Daytona
71,297Secure AI sandbox workspaces with sub-second start and stateful dev environments.
Upstream archived. The repository of Daytona is read-only: it gets no further changes. Upstream is archived (checked on GitHub 2026-11-21; last push 2026-07-24). The repository README says: "This repository is no longer maintained. As of June 2026, Daytona's core development has moved to a private codebase." The last open release is v0.190.0 (AGPL-3.0); the default branch no longer has a LICENSE file. Status set to deprecated; no open successor is named.
Activity band details
Activity band A to F: a bin of a score that adds GitHub stars (log scale), a push to the upstream repository in the 12 months before `as_of`, the number of declared integration surfaces and, where the catalogue records them, citing papers and benchmark evaluations. It measures popularity and activity. It is not a level of evidence: no band means a paper cites the tool or that it was measured. Recency is judged as of 2026-11-22.
Computed band: F
(raw score 4.94).
Shown band: F
.
Facets:
documented_in=0evaluated_on=0integration_surfaces=1paper_citations=0recent_push=2stars=1.94
capped from C to F by maturity_status='deprecated'
Source of truth: pipeline/maturity/score.py
Description
Open-core sandbox platform providing secure, stateful workspaces for AI agents. Supervision primitives: sub-second sandbox creation, per-workspace filesystem and network isolation, snapshot/fork for branching trajectories, and a declarative devcontainer-style workspace config. Positioned as infrastructure for fully_autonomous coding agents that need reproducible, disposable execution environments.
Why it's included
Occupies recovery × post_generation × fully_autonomous. Distinctive primitive is workspace snapshot/fork, which enables branching agent trajectories and rollback — a supervision capability beyond pure per-call sandbox isolation.
Security notes
Open-core (AGPL core + hosted control plane). Self-hosted deployments require hardening of the orchestration layer and careful review of runtime-class settings for tenant isolation. Hosted tier inherits typical SaaS tenancy and data-residency questions — review posture before running sensitive code.
Addresses failure modes
These tags are the catalog's claim about what Daytona is built to catch or prevent. A tag is not a test result. SAICA-Bench has not measured Daytona, so none of these tags is tested here.
- Supply-chain attack — Slopsquatting, typosquatting, compromised MCP servers.
- Security vulnerability — Insecure patterns, injection flaws, weak cryptography, secret leakage.
- Scope creep — Actions outside declared task boundary.