Comparisons / Eve vs Google ADK
Eve vs Google ADK: Which Agent Framework to Use?
Eve vs Google ADK, head to head
Eve and Google ADK both let you build an agent, but they sit in different parts of the stack and they assume different things about who's writing the code.
Eve is Vercel's open-source TypeScript agent framework, launched June 17 2026.
Google's Agent Development Kit (ADK) is an open-source framework for building multi-agent systems.
Underneath, both wrap the same thing: a model call, a tool dispatch, a loop. The decision is about which abstraction your team wants to think in day to day, and which ecosystem you're willing to inherit along with it. There's an honest, framework-free version of the same pattern in about 60 lines of Python in the lesson at the bottom of this page — useful as a baseline regardless of which framework wins.
Pick Eve if
Pick Eve if eve earns its keep when you want durable execution, sandboxed code exec, and multi-model routing without wiring three separate services. If you're already on Vercel, it composes; if not, the runtime pieces are the value and they don't travel. For a single-loop tool-using agent, plain TypeScript ships faster. The tradeoffs in its intro should match how your team already thinks about agents; Google ADK will feel like translation if they don't.
Pick Google ADK if
Pick Google ADK if aDK earns its complexity when you need multi-agent orchestration on Google Cloud with Vertex AI deployment. If you're using Gemini and need production-grade agent infrastructure, it's well-designed. For single-agent use cases or non-Google stacks, plain Python keeps things simpler. The tradeoffs in its intro should match how your team already thinks about agents; Eve will feel like translation if they don't.
By the numbers
By the numbers
Eve
3.5k
180
TypeScript
Apache-2.0
2026-06-17
Vercel
Vercel (public)
Runs on Vercel Sandbox + AI Gateway; deploys anywhere Node runs
Yes
Google ADK
18.7k
3.2k
Python
Apache-2.0
2025-04-01
Google/Alphabet
Vertex AI
Yes
GitHub stats as of April 2026. Stars indicate community interest, not necessarily quality or fit for your use case.
| Concept | Eve | Google ADK |
|---|---|---|
| Agent | A directory with `agent.ts` + `instructions.md` + subfolders — the framework wires them together | `LlmAgent` class with model, instructions, and `sub_agents` list |
| Tools | Each file in `tools/` exports one tool; schema comes from a Zod export | `FunctionTool`, built-in tools (Search, Code Exec), third-party integrations |
| Durability | Vercel Workflow SDK checkpoints every step so a crashed agent resumes where it left off | — |
| Sub-agents | Each `subagents/*.ts` becomes a callable sub-agent the parent can hand off to | — |
| Sandboxed exec | Vercel Sandbox runs untrusted code in isolated micro-VMs, one API call away | — |
| Schedules | `schedules/*.ts` exports a cron expression + handler; Vercel runs it | — |
| Agent Loop | — | `Runner.run()` with automatic tool dispatch and sub-agent delegation |
| Multi-Agent | — | Hierarchical agent tree with root agent delegating to specialized sub-agents |
| Workflows | — | `SequentialAgent`, `ParallelAgent`, `LoopAgent` workflow primitives |
| Session | — | Session and State service with typed channels and persistence |
Or build your own in 60 lines
Both Eve and Google ADK implement the same 8 patterns. An agent is a function. Tools are a dict. The loop is a while loop. The whole thing composes in ~60 lines of Python.
No framework. No dependencies. No opinions. Just the code.
Build it from scratch →