Quick verdict
These are the two TypeScript agent frameworks product teams ask about together once they notice Vercel shipped Eve:
- Vercel Eve is a filesystem-first agent framework ("Next.js for agents"):
instructions.md+ Markdown skills, TypeScript tools, sandboxes, channels, schedules, and durable sessions on Vercel Workflows. Best for Next.js / Vercel teams that want one agent directory that deploys with AI Gateway, Sandbox, Connect, and multi-channel delivery. Honest limit: preview/beta APIs can move; the deepest value shows when you accept Vercel platform gravity (Functions, Workflows, Sandbox meters). Self-host paths exist, but the happy path is Vercel. - Mastra is a batteries-included TypeScript agent framework: agents, graph workflows with suspend/resume, memory, RAG, evals, MCP, Studio, deployers for Vercel/Cloudflare/Netlify or a standalone Hono server. Best for teams that want the agent runtime in code they own and can run on any Node-compatible host. Honest limit: more framework surface; serverless storage and background memory still need deliberate config (LibSQL-on-Workers traps, Observational Memory costs).
Cipher's cutover rule: pick Eve when the agent should feel like a Vercel primitive (directory authoring + platform durability + channels). Pick Mastra when the agent is a product service you must keep cloud-portable with workflows, memory, and evals in one TypeScript package. They are not the same layer as the Vercel AI SDK — see Eve vs AI SDK and Mastra vs AI SDK.
Last updated: August 2026. Eve is in public preview/beta — re-check vercel.com/eve, Eve concepts, and Mastra before you freeze a stack decision.
Framework matrix
| Vercel Eve | Mastra | |
|---|---|---|
| Authoring model | Agent = directory (instructions.md, skills/, tools/*.ts) |
Agent = TypeScript modules (agents, workflows, tools in code) |
| Durability | Sessions on Vercel Workflows (event log + replay) | Native workflows + suspend/resume; platform durability still yours (or Inngest/etc.) |
| Sandbox | First-class isolated sandbox (Vercel Sandbox on Vercel) | You choose where untrusted code runs |
| Channels | Built-in channel files (Slack, Discord, Teams, web, cron…) | HTTP / app integration; channels are your product surface |
| Memory & RAG | Session context + skills; assemble deeper RAG as tools/connections | Built-in memory + RAG primitives |
| Evals | Framework eval suites + Agent Runs observability on Vercel | Built-in scorers / Studio-oriented eval loop |
| Cloud gravity | Strongest on Vercel (Gateway, Workflows, Sandbox, Connect) | Provider-agnostic Node deploy; optional Vercel deployer |
| License / maturity | Open framework (Apache-2.0 lineage); preview/beta | Apache-2.0 core; production use widespread in TS shops |
Where Eve wins
Eve wins on authoring speed for Vercel-native teams. An instructions.md file is a runnable agent; skills load on demand so you do not stuff every playbook into the system prompt; tools are files with no registration ceremony. Durability is not a side project — sessions park and resume on Workflows, including human-in-the-loop approval gates.
The other Eve edge is the platform bundle: AI Gateway model strings, sandboxed compute for bash/file tools, Connect for GitHub/Stripe/Linear-style auth, and multi-channel delivery from one codebase. If your product already lives on Vercel, gluing those yourself is how projects lose a quarter.
Cost honesty: Eve is not a flat "agent SKU." Usage maps to Functions, Workflows, Sandbox, AI Gateway, and model tokens (Eve pricing docs). Budget turns, stream writes, and sandbox minutes the same way you budget any production agent.
Where Mastra wins
Mastra wins when the agent is the product backend and you refuse cloud lock-in as the default. Typed workflows (.then(), .branch(), .parallel()), memory, RAG, MCP, and evals ship as one TypeScript story you can run on Cloudflare Workers, a container, or a Hono server — not only Vercel Functions.
Teams that already standardized on Mastra for orchestration should not rip it out because Eve launched. Eve is a strong alternative entry point for greenfield Vercel agents; Mastra remains the clearer batteries framework when you need portable agent infrastructure with Studio-style DX.
Production traps unchanged from our other Mastra posts: avoid LibSQL file URLs on Vercel/Workers; configure memory compression so background tokens do not surprise finance.
The cutover in practice
| Signal | Prefer Eve | Prefer Mastra |
|---|---|---|
| App already on Vercel + Next.js | Default | Fine if you need portable agent service |
| Want Markdown skills + directory DX | Default | Possible, not the native authoring model |
| Need multi-channel (Slack/Teams/cron) day one | Default | Build channels yourself |
| Must deploy agent to AWS/Cloudflare without Vercel meters | Self-host path; more work | Default |
| Deep built-in memory + RAG + evals package | Assemble more | Default |
| AU/SG residency / VPC story is AWS-first | Usually wrong gravity — see Strands | Possible, still not AWS-native |
Cipher preference for AU/SG product teams on Vercel: prototype the agent on Eve if channels + Workflows durability are the hard part; choose Mastra if the hard part is a portable agent platform with memory/evals you will operate for years. AWS-bound internal agents still often land on Strands + AgentCore — Mastra vs Strands.
FAQ
Is Eve just a rebrand of the Vercel AI SDK? No. The AI SDK is an application toolkit for streaming and model calls. Eve is an agent framework with directory authoring, durable sessions, sandboxes, and channels. Stack them; do not treat them as substitutes — full comparison.
Can I self-host Eve? Eve positions itself as open and self-hostable (swap backends; Postgres-backed durability paths are documented on eve.dev). Production reality: most teams will still feel Vercel's gravity. Verify the self-host guide against your compliance boundary before promising it to a board.
Which is more "production ready" in August 2026? Mastra has longer production runway in TypeScript shops. Eve's durability story is strong because it sits on Workflows, but the framework itself is preview/beta — design for API change.
Who helps Australian and Singapore teams choose and ship either? Cipher Projects designs production agent stacks — framework selection, eval harnesses, and deployment on infrastructure you own — without forcing a demo that dies in staging.
Conclusion
Eve vs Mastra is an authoring-and-gravity decision. Eve makes agents feel like Vercel: Markdown + tools in a directory, durable by default, channels included. Mastra makes agents feel like a TypeScript product platform you can take anywhere Node runs. Pick the gravity you are willing to inherit, then wire evals and ownership before the first customer-facing session.
Related: Eve alternatives · Eve vs LangGraph · durable workflow frameworks · four-way framework comparison