Daytona sells sandboxes for AI-generated code: a Linux container by default, or a Linux VM, Windows, GPU or macOS sandbox when the workload needs one. The unit is created and driven through five SDKs, a CLI, a REST API and an MCP server.

The classes are not interchangeable. Pause, resume, fork and memory snapshots exist only on the VM classes; archive exists only on containers; GPU sandboxes run in containers and vanish on stop.

It began as an open-source development-environment company. That repository is archived, and the managed platform is closed source.

At a glance

Who it is forTeams building an agent product who want a fast container by default and a full VM when Docker, Windows or a real kernel is needed.
IsolationLinux containers by default: dedicated namespaces, enforced resource limits and root inside, sharing the runner's kernel. Linux VM and Windows sandboxes have their own kernel. Docker-in-Docker is documented; nested virtualisation is Linux-VM only and must be enabled for the organisation. GPU sandboxes are containers with exclusive GPU allocation.
SizesDefault 1 vCPU / 1 GB / 3 GiB; the organisation ceiling is 4 vCPU / 8 GB / 10 GiB of disk. Named presets include daytona-medium 2/4/8 and daytona-large 4/8/10; Windows presets go to 4/16/50. GPU sandboxes attach up to 8 GPUs, each adding up to 16 vCPU / 192 GB / 512 GB. Two shared regions, us and eu.

Fits well, fits badly

Our reading of the sourced material on this page, not a provider claim.

Fits well

  • A Docker or Windows workload: the VM and Windows classes have their own kernel, and Docker-in-Docker is documented.
  • A fast container for untrusted code, priced per reserved vCPU and second, with $200 of free compute and no card.
  • A GPU sandbox alongside the CPU ones: up to 8 GPUs per sandbox, though on shared capacity and preemptible.
  • Browser or desktop agents: a VNC desktop and a computer-use API are first-class.

Fits badly

  • A workload that needs more than 10 GiB of disk on a Linux sandbox; the 50 GiB presets are Windows only.
  • An agent that runs long jobs with no inbound traffic: a container stops after 15 idle minutes even mid-build.
  • Full internet on a small account: Tier 1 and 2 are network-restricted and cannot be overridden per sandbox.
  • A strict per-tenant boundary: any organisation member or API key can exec in any running sandbox.

How it bills

ModelPer-second billing on reserved resources, with no plan fee. Tiers are prepaid top-ups that set an organisation-wide pool.
MetervCPU $0.0504/hour, memory $0.0162/GiB-hour and disk $0.000108/GiB-hour after the first 5 GiB. Windows adds $0.0858/vCPU-hour, which reads either as a replacement rate or a surcharge.
While stoppedStopped and paused sandboxes bill reserved disk only; memory is not billed. Archived and deleted sandboxes bill nothing.
Plan feeNo plan fee. Tier 1 needs only a verified email; Tier 2 is a $25 top-up, Tier 3 $500, and Tier 4 $2,000 every 30 days.
Minimum$200 of free compute with no card, but it cannot be spent on GPU sandboxes.

How Daytona lets you try before paying is on Trials and free tiers.

Where it stands out

  • A container by default and a real VM, Windows or GPU sandbox when the workload needs one.
  • Reserved-resource billing per second with no plan fee and $200 of free compute.
  • Free S3-backed volumes, 100 per organisation, that do not count against storage.
  • Five SDKs, a REST API, a CLI, a first-party MCP server and a browser Playground.
  • A VNC desktop and a computer-use API for browser agents.

Using it without writing code

DashboardYes: a dashboard with a browser Playground for creating sandboxes and running SDK operations, plus Terminal and VNC tabs.
Without codePartly. The Playground creates a sandbox and generates SDK snippets; operating one from the browser works, but building one is still a form of code.
SignupGoogle or GitHub login, no card, $200 of free compute. Tier 1 needs only a verified email; GPU sandboxes cannot use the free credit.
Docs and supportAgent-readable docs with llms.txt and a 3.3 MB llms-full.txt, five SDKs, a CLI and a first-party MCP server. Support is email, Slack, chat, video and forums with no response-time commitment.

The company

From the profile's company section: the legal entity, who funds it, and what a buyer can check before signing.

Legal entity

Daytona Platforms Inc., at a New York address. Delaware incorporation is unconfirmed by the company; its terms name Delaware law.

“These Terms of Service ("Terms") are a binding contract between you ("you" or "Customer") and Daytona Platforms Inc.” daytona.io docs-confirmed

Founded and leadership

2023, by Ivan Burazin (CEO), Vedran Jukić (CTO) and Goran Draganić (Chief Architect).

“Daytona was founded in 2023 and evolved from our deep experience with developer workflows and infrastructure challenges.” daytona.io docs-confirmed

Funding

$91M total after a $60M Series B at a $1B valuation in October 2026, led by FirstMark Growth.

“a $60M Series B at a $1B valuation, led by FirstMark Growth, bringing our total funding to $91M” daytona.io docs-confirmed

Headcount

Twelve people are named on the about page; no total is published.

not-published

Status and SLA

Status page components showed 99.768% at the lowest. The SLA promises 99.95%, but credits go only to Tier 4 and above.

“Daytona will use commercially reasonable efforts to make the Services available 99.95% of the time in any given calendar month” daytona.io docs-confirmed

Certification

SOC 2 Type 2 is a management bridge letter, not an attestation report. ISO 27001 is marked in progress while the badge is displayed.

“This letter is a representation of Daytona management” trust.daytona.io docs-confirmed

Price changes

No notice period: fees may change by posting the change on the service.

“We reserve the right to modify fees and may do so by posting such modification on the Services or informing you through other reasonable methods.” daytona.io docs-confirmed

Caveats and contradictions

Shown as the research found them. A contradiction means the provider's own pages disagree; an open question means the answer is not published.

  1. 01

    Every sandbox is said to have a dedicated kernel, then said to be a container Contradiction

    The sandboxes page claims a dedicated kernel for every sandbox and two paragraphs later says sandboxes run as Linux containers by default. The isolation page is explicit that containers get namespaces and only VM classes get their own kernel.

    “Each sandbox runs in isolation, giving it a dedicated kernel, filesystem, network stack, and allocated vCPU, RAM, and disk.”
    Daytonadocs-confirmed
    “Sandboxes run as Linux containers by default.”
    Daytonadocs-confirmed
  2. 02

    Startup is quoted as sub-90 ms and as sub-200 ms Contradiction

    The homepage claims sub-90 ms from code to execution; the careers page says sub-200 ms. Neither is a measured figure for a cold sandbox.

    “Sub 90ms sandbox creation from code to execution.”
    Daytonadocs-confirmed
    “isolated environments with sub 200ms startup times”
    Daytonadocs-confirmed
  3. 03

    The 10 GiB disk cap and the 50 GiB Windows presets cannot both be the maximum Open question

    The sandboxes page states a 10 GB per-sandbox disk maximum and, on the same page, lists Windows presets with 30 and 50 GB. Treating 10 GiB as the real Linux cap is the profile's judgement call: a 50 GiB Linux sandbox needs a raised limit with no published price or approval path beyond support.

  4. 04

    Startup credits are $50k or $100k Contradiction

    The pricing page offers up to $50k in credits; the startups page offers up to $100k. Both are live.

    “up to $50k in credits for free”
    Daytonapricing-page
    “Get up to $100k in Daytona credits”
    Daytonadocs-confirmed
  5. 05

    Audit logs are an Enterprise feature on one page and a permission on another Contradiction

    The pricing page lists SSO and audit logs under Enterprise; the audit-log page gates them by role instead, and says compliance export is coming soon.

    “SSO, audit logs”
    Daytonapricing-page
    “available to administrators with full access and members with audit log permissions”
    Daytonadocs-confirmed
  6. 06

    Roles do not protect running sandboxes Open question

    Any member of an organisation, and any API key valid for it, can exec in every running sandbox whatever their role. A write:sandboxes key can also mount any secret in the organisation.

  7. 07

    The standard preview token is a sandbox-wide credential Open question

    It is not restricted to the port requested, opens the web terminal and the toolbox, and cannot be revoked. Signed URLs are the shareable form: 60 seconds by default, 24 hours maximum.

  8. 08

    The open-source repository is archived Open question

    The public repo says development moved to a private codebase in June 2026. The managed service is closed source, so the archived code is not what you are buying.

  9. 09

    Two documentation trees describe different products Open question

    The default docs are v0.226; /docs/en/v2/ documents an alpha with different API hosts and a different macOS model, including Daytona-managed Mac reservations.

Sources

The three shared workloads

List-price illustrations, not quotes

A · 1,000 short tasks

$27.74 a month

daytona-medium (2 vCPU / 4 GiB / 8 GiB disk), deleted after each task

  • Compute166.67 h × (2 × $0.0504 + 4 × $0.0162)$27.60
  • Disk8 GiB × 166.67 h × $0.000108$0.14
  • The shape exists exactly as daytona-medium, so no substitution is needed.
  • The $200 free credit covers this workload, leaving about $172.
  • Tier 1's restricted network may block package installs the allowlist does not cover.

B · One always-on box

$443.69, after substituting Windows

windows-large (4 vCPU / 16 GiB / 50 GiB), 730 h

  • Compute730 × (4 × $0.0858 + 16 × $0.0162)$439.75
  • Disk50 GiB × 730 h × $0.000108$3.94
  • If the Windows rate is a surcharge on top of the Linux rate rather than a replacement, the month is $590.86.
  • 50 GiB also exceeds Tier 1's 30 GiB storage pool, so Tier 2 is the minimum.

This workload cannot be bought as specified: 50 GiB exceeds the 10 GiB per-sandbox disk cap. The nearest published shape is a Windows VM, which is the profile's judgement call, not a Linux option.

C · Three hours a day

$15.53 a month

daytona-medium (2 vCPU / 4 GiB / 8 GiB), 90 running hours, stopped otherwise

  • Compute90 × (2 × $0.0504 + 4 × $0.0162)$14.90
  • Disk8 GiB × 720 h × $0.000108$0.62
  • The 20 GiB brief is not available on this class; 8 GiB is the published 2 vCPU shape.
  • Disk bills in both running and stopped hours. Containers cannot pause, so stop is disk-only.