Daytona
Stateful sandboxes for AI-generated code — Linux containers, Linux and Windows VMs, macOS and GPU sandboxes — with snapshots, volumes and preview URLs. The strongest choice for stateful coding-agent workspaces and breadth of sandbox types; note the shift away from open source.
Overview
Daytona pivoted from development environments to agent infrastructure and has become one of the most popular sandbox platforms. Sandboxes are stateful by default — they stop when idle and resume with files intact — which suits coding agents that return to the same workspace. It offers Linux containers, Linux and Windows VMs, macOS and GPU sandboxes from one API.
Daytona’s SDK coverage (Python, TypeScript, Ruby, Go and Java) is the broadest among hosted providers, and BYOC lets you run sandboxes on your own runner nodes. In June 2026 Daytona moved core development to a private codebase and archived its public AGPL repository, so it should now be treated as a proprietary platform.
Notable
- Raised a $24M Series A in February 2026, led by FirstMark Capital.
- Archived its open-source repository in June 2026; development continues privately.
- Lists LangChain, SambaNova, Writer and n8n among customers.
Daytona specifications
| Attribute | Details |
|---|---|
| Isolation | Isolated Linux containers (dedicated namespaces, resource limits) by default; VM sandboxes (Linux, Windows) run a full VM with their own kernel; GPU sandboxes are containers with exclusive GPU allocation |
| Deployment | Hosted platform · BYOC available |
| Open source | No (Former public repo archived (AGPL-3.0)) |
| SDKs and interfaces | Python, TypeScript, Ruby, Go, Java |
| Cold start (vendor claim) | Sub-90 ms sandbox creation (vendor claim) |
| Max session length | No hard maximum: auto-stop after 15 min idle by default (can be disabled), auto-archive after 7 days stopped, optional wall-clock TTL |
| Persistence | Stateful sandboxes, snapshots, shared volumes, archive/recover and stop/start with state. Pause/resume, fork and hot snapshots on VM sandboxes |
| GPU | Yes — up to 8 GPUs per sandbox (e.g. H100 from $2.27/hour, B200 $3.59/hour, preemptible list rates) |
| Networking | Tiered egress: per-sandbox CIDR and domain allowlists or block-all, changeable at runtime; preview URLs for any port with token or signed URLs; SSH, VNC and web terminal |
| Pricing | Per second: $0.0504 per vCPU-hour + $0.0162 per GiB-hour; storage $0.000108/GiB-hour after 5 GiB free; Windows $0.0858/vCPU-hour |
| Free tier | $200 free compute for new users; startup program up to $50k |
| Compliance | States HIPAA, SOC 2 and GDPR compliance (Trust Center) |
| Regions | US East, US West, EU Central, EU West, India; custom regions via BYOC |
Facts from Daytona’s public documentation, verified November 8, 2026. Performance numbers are vendor claims.
Strengths and trade-offs
Strengths
- You need long-lived, stateful workspaces that survive between sessions
- You want SDKs beyond Python and TypeScript (Ruby, Go, Java)
- You need GPUs, Windows or macOS sandboxes from the same provider
- You want BYOC on your own compute
Trade-offs
- No longer actively open source — the public repo is archived
- Default Linux sandboxes use container isolation; VM isolation requires VM sandboxes
- Fork and pause/resume limited to VM sandboxes
Best for: Long-lived, stateful agent workspaces that need many SDK languages, GPUs, or Windows and macOS sandboxes.
Where Daytona ranks
How Daytona compares
| Sandbox | Isolation | Open source | Self-host / BYOC | Cold start (vendor) | Max session | Snapshots / pause | GPU | SDKs |
|---|---|---|---|---|---|---|---|---|
| Daytona | Containers or VMs | No | Not documented / Yes | <90 ms | Unlimited | Yes / Yes | Yes | Python, TypeScript, Ruby, Go, Java |
| E2B | Firecracker microVM | Yes | Yes / Yes | Not documented | 1 h / 24 h (Pro) | Yes / Yes | No | Python, JavaScript/TypeScript |
| Fly.io Sprites | MicroVM | No | No / No | 0.1–2 s wake | Unlimited | Yes / Yes | No | JavaScript/TypeScript, Go, Python, Elixir |
| Modal Sandboxes | gVisor or VM | No | No / Not documented | <1 s | Up to 24 h | Yes / Yes | Yes | Python, JavaScript/TypeScript, Go |
| Vercel Sandbox | Firecracker microVM | No | No / No | Milliseconds (claim) | 24 h (Pro) | Yes / Yes | Not documented | JavaScript/TypeScript, Python |
| Together Code Sandbox | MicroVM | No | No / Not documented | 0.5 s (snapshot) | Until terminated | Yes / Yes | Not documented | Python, TypeScript |
| Northflank Sandboxes | Cloud Hypervisor microVM | No | No / Yes | <1 s | Unlimited | Not documented / Yes | Yes | JavaScript/TypeScript, Python |
Head-to-head: E2B vs Daytona · Daytona vs Modal Sandboxes · Daytona vs Vercel Sandbox · Daytona vs Cloudflare Sandbox SDK · Daytona vs Fly.io Sprites · Freestyle vs Daytona
Frequently asked questions
What is Daytona?
How does Daytona isolate code?
Is Daytona open source?
How much does Daytona cost?
What are the best Daytona alternatives?
Sources
Cite this page
Agent Sandboxes. (2026). Daytona. agentsandboxes.org. Last reviewed November 8, 2026. https://agentsandboxes.org/sandboxes/daytona/
Found an error or a missing sandbox? Submit a correction — every entry links to the sources it relies on.