E2B vs forkd
E2B is much bigger: 14.6k stars against 3.3k. Over the days we have tracked them E2B moved +10.5% and forkd +22.3%, so forkd is growing faster right now.
E2B leads on model freedom. forkd does not take any axis by a clear margin.
Stars and commit dates come from our own daily tracking. The six axes are read off each project's documentation by our review pipeline, so they describe what a project says about itself, not what we measured in its code.
Where they stand today
Provides secure, isolated cloud sandboxes for running AI-generated code with SDKs for JavaScript and Python, allowing real-world tool access in a managed environment.
- Stars
- 14.6k
- Tracked growth
- +10.5%
- Maturity
- ●●●●●
- Last commit
- 12h ago
- Language
- Python
- License
- Apache-2.0
- Cost to run
- E2B cloud (API key); self-hostable
Provides near-fork(2) microVM spawn and live BRANCHing via snapshot copy-on-write, enabling KVM-isolated agent fan-out with millisecond-scale latency.
- Stars
- 3.3k
- Tracked growth
- +22.3%
- Maturity
- ●●●●●
- Last commit
- 1h ago
- Language
- Rust
- License
- Apache-2.0
- Cost to run
- Free, self-hosted
Six axes, head to head
Each axis runs 0 to 5. The label under a score is what that project's own docs claim, not a category average.
| Axis | E2B | forkd |
|---|---|---|
Context depth How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository. | ●●●●● Command-only | ●●●●● Diff only |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● None | ●●●●● None |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Minimal config | ●●●●● CLI / REST options |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Self-hostable | ●●●●● Fully local |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● Bring-your-own-key | ●●●●● No model support |
Setup ease What it takes to get a first useful run out of it. | ●●●●● API key + SDK | ●●●●● Kernel + root req |
Which one to pick
Pick E2B if…
Secure sandboxing — choose E2B when you need to execute AI-generated code safely in isolated sandboxes with an option to self-host your infrastructure.
- Model freedom: Bring-your-own-key (5/5 against 1/5)
Pick forkd if…
Ultra-fast fan-out — pick forkd when you need hundreds of warmed, KVM-isolated microVM sandboxes and the ability to snapshot/branch a running agent mid-thought.
What people want from each one
e2b-dev/E2B
deeplethe/forkd
Hacker News: Forkd: Fork() for AI Agent MicroVMs drew 2 points and 0 comments.
Questions people ask
Is E2B better than forkd?
E2B leads on model freedom. forkd does not take any axis by a clear margin. E2B is worth picking when secure sandboxing — choose E2B when you need to execute AI-generated code safely in isolated sandboxes with an option to self-host your infrastructure.
Which of E2B and forkd keeps my code private?
E2B: Self-hostable (4/5). forkd: Fully local (5/5).
What does each one cost to run?
E2B: E2B cloud (API key); self-hostable. forkd: Free, self-hosted.
Full profiles: e2b-dev/E2B and deeplethe/forkd. Everything else in Runtimes & sandboxes.