Daytona Sandbox

license

AGPL-3.0(OSI, copyleft)

source

public

managed-tier

app.daytona.io hosted cloud + hybrid (proprietary)

core features withheld

yes — core development moved to a private codebase in June 2026 - daytonaio/daytona now holds only a README and logos, and the daytona org publishes SDKs and clients but no server or runtime

Daytona's AGPL-3.0 license and public source describe the project at its last tagged release, v0.190.0; since then, core development has moved to a private codebase, and the default branch holds only a README and two logo files, with no server or runtime published anywhere in the daytona org. Judged against what currently ships, the source would read as partial rather than open core.

• https://api.github.com/orgs/daytona/repos?per_page=100 recorded 2026-10-13

  The org the README redirects to publishes SDKs and clients (daytona/sdk, daytona/clients - "Official SDKs, API clients, and CLI/MCP tools"), legacy provider plugins and samples. No server, control plane or sandbox runtime repository.

• https://api.github.com/repos/daytonaio/daytona/git/trees/main?recursive=1 recorded 2026-10-13

  Full untruncated recursive tree of the default branch: 5 entries in total - README.md, assets/, assets/images/ and two logo PNGs. No source, no LICENSE file. The repo is not archived and was last pushed 2026-07-24.

• https://github.com/daytonaio/daytona recorded 2026-06-04

  AGPL-3.0 license; secure runtime for AI-generated code; managed cloud at app.daytona.io

• https://raw.githubusercontent.com/daytonaio/daytona/main/README.md recorded 2026-10-13

  "This repository is no longer maintained. As of June 2026, Daytona’s core development has moved to a private codebase. This repository will receive no further updates, fixes, or releases. It remains public and free to use, fork, and build on under the LICENSE (linked at tag v0.190.0), as is and without support or warranty."

• https://raw.githubusercontent.com/daytonaio/daytona/v0.190.0/LICENSE recorded 2026-10-13

  The GNU Affero General Public License v3, verbatim. This is the tag the unmaintained README points at, and it is the only place the AGPL-3.0 grant now lives - the default branch carries no LICENSE file at all, and GitHub's repo metadata reports a null license for daytonaio/daytona as a result. So the recorded AGPL-3.0 is a fact about v0.190.0, not about anything Daytona currently ships.

Adoption is read from monthly PyPI downloads of the daytona package, confirmed as the product's own SDK. The count is close enough to where a larger number would read differently that ordinary month-to-month variance could change it, so confidence stays moderate rather than high.

• https://pypi.org/pypi/daytona/json recorded 2026-08-14

  Package metadata - name daytona, summary "Python SDK for Daytona", author "Daytona Platforms Inc.", author_email support@daytona.io, license Apache-2.0, version 0.204.0. Confirms the banded package is the product's own SDK.

• https://pypistats.org/api/packages/daytona/recent recorded 2026-10-07

  8,365,992 downloads in the trailing 30 days for daytona (pypistats last_month)

• https://pypistats.org/packages/daytona recorded 2026-06-04

  ~8,313,410 downloads last month

Each Daytona sandbox gets a dedicated kernel, filesystem and network stack, and independent benchmarks confirm well-under-a-second cold starts for the default container class. Daytona names no microVM or gVisor-style isolation, so isolation is limited to OCI and Docker compatibility, and fork, pause and resume apply only to a separate, opt-in VM tier.

• https://daytona.io/docs/ recorded 2026-09-29

  Docs index stating "spinning up in under 90ms from code to execution and running any code in Python, TypeScript, and JavaScript. Built on OCI/Docker compatibility".

• https://daytona.io/docs/en/sandboxes recorded 2026-09-29

  Sandboxes page stating "Each sandbox runs in isolation, giving it a dedicated kernel, filesystem, network stack, and allocated vCPU, RAM, and disk." and "GPU sandboxes are ephemeral and support up to"; its runtime table lists "<90ms" for the default Linux container, and "Fork", "Pause/resume" and "Memory snapshots" for the Linux VM and Windows runtimes.

• https://github.com/daytonaio/daytona recorded 2026-06-04

  The repo behind the isolation and spin-up claims is a README stub carrying neither, which is why the docs are cited for them instead.

• https://www.computesdk.com/benchmarks/sandboxes/ recorded 2026-07-09

  ComputeSDK TTI leaderboard (independent, 100 iters/day, 2026-07-09 run): median time-to-interactive ~140ms sequential / ~710ms burst @100 concurrent; 4th-fastest of 19 providers

• https://www.computesdk.com/benchmarks/sandboxes/burst-tti recorded 2026-09-29

  ComputeSDK burst benchmark page describing "Compare sandbox startup times for E2B, Modal, Vercel, Blaxel, Daytona, Hopx, Namespace, Cloudflare, and more in a 100-sandbox burst." with a Daytona row reporting "0.34s" median.