Eve vs Flue: Vercel-first vs deploy-anywhere
Compare Eve and Flue on deployment gravity: Vercel-first vs deploy-anywhere. Then see where Evex fits as the registry for reusable Eve agents.
The decision is deployment gravity
Eve and Flue are both TypeScript agent frameworks. The useful cut is where you expect the agent to run day to day.
Eve's first-class deploy path is Vercel: eve deploy, with Vercel running the web service, workflows, sandboxes, and schedules. On Vercel, the default sandbox backend is Vercel Sandbox (Deploy to Vercel).
Flue markets write-once, deploy-anywhere. Its getting started path covers Node.js, Cloudflare, and GitHub Actions or other CI, with flue run for local and CI runs and a Vite plus Hono path when you host the agent (Flue getting started).
Choose on that gravity first. Feature lists matter less than whether your team's host is already decided.
Eve in one paragraph
Eve builds an agent by walking the filesystem under agent/. Start with Node.js 24 or newer and npx eve@latest init. The default scaffold routes models through the Vercel AI Gateway. From there the natural production path is the Vercel deploy flow above (Eve getting started).
Flue in one paragraph
Flue is an open agent framework from the creators of Astro, powered by Pi. You write agents with a React-like hooks API, run them with flue run, and target Node or Cloudflare in config. The site and docs frame it as a programmable harness you can run locally or deploy across those hosts (Flue, Flue getting started, withastro/flue).
Where Evex fits
Eve is the TypeScript agent framework you author under agent/. Evex is the catalog where you browse reusable Eve agents and install them as source into that project.
Browse the catalog on /agents. From the Eve app root, install with:
npx shadcn@latest add @evex/<slug>
The CLI writes under agent/ (and related files). You own those files. There is no hosted Evex runtime (Installation).
For editor-driven browse and install, configure the shadcn MCP server and resolve @evex/<slug> from chat (MCP). Product docs live at /docs. For scaffold vs catalog vs standalone install paths, see /learn/install-eve-agent.
If you chose Flue for deploy-anywhere, that choice stands. @evex installs still require an Eve project: Installation documents agents installing into an eve app, not into a Flue app. Use Eve when you want the Evex catalog path.
Decision table
Eve
Use when
Your default host is Vercel, and you want filesystem agents under agent/ with eve init / eve deploy.
Avoid when
You need Node, Cloudflare, or CI as equal first-class targets without a Vercel-first gravity.
Flue
Use when
You want an open harness/framework you can run locally and deploy across Node, Cloudflare, or CI.
Avoid when
Your team is already committed to Eve on Vercel and wants registry installs from Evex.
Evex install
Use when
You already have (or will create) an Eve app and want reusable agent source via npx shadcn@latest add @evex/<slug>.
Avoid when
You only have a Flue project and expected @evex to install there. Evex installs into an eve project.
FAQ
What is the difference between Eve and Evex?
Eve is the TypeScript agent framework (filesystem under agent/, Vercel-first deploy). Evex is the catalog of reusable Eve agents you inspect and install as source with npx shadcn@latest add @evex/<slug>.
Can I install Evex agents into a Flue project?
No. Evex Installation says agents install into an eve project and write the agent/ layout Eve loads. If you want @evex/<slug>, create or open an Eve app first. Flue remains the right framework when deploy-anywhere is the priority.
When should I pick Flue?
Pick Flue when write-once and deploy across Node, Cloudflare, or CI matters more than a Vercel-first path, and you want the hooks-style Flue agent model.
When should I pick Eve?
Pick Eve when Vercel is your default production host and you want filesystem-authored agents with the Eve init and deploy flow. After the Eve app exists, use Evex to install catalog agents.