PAGES
← all tools
◆ AI Coding Agents

Daytona

Warm pool management and spot GPUs commercial

Daytona is a development environment platform that enables standardized, reproducible coding spaces for teams and AI agents.

source ↗ rss ↗ What is a cyber toolchain?

Summary

Daytona is a commercial sandbox infrastructure platform that provisions and manages isolated execution environments for AI-generated code, run as a hosted API and SDK rather than something installed and operated locally. It gives developers building AI coding agents a way to spin up, fork, and tear down sandboxes programmatically, with controls like per-sandbox CPUCPUThe main general-purpose processor in a computer. It runs application instructions and coordinates work with memory and other hardware. and memory limits, TTLTTLTime to live, a limit on how long data remains valid or how far a packet can travel. Caches use a time limit; IP packets use a hop limit. and auto-pause settings for lifecycle management, and WebSocketWebSocketA protocol that upgrades an HTTP connection into a persistent, full-duplex channel, letting a server push data to a client without repeated polling. Cyber tools use it for real-time event streaming and live command output. event subscriptions for tracking sandbox state in real time. Organization-level metrics and membership management point to teams operating fleets of sandboxes rather than single developers experimenting alone. Security-conscious defaults run through recent work too, including enforced TLS verification and restricted CLI config permissions. With 33 releases in the window tracked, including steady SDK, API, and CLI updates, the project shows active, ongoing development.

Daytona is a development environment platform that enables standardized, reproducible coding spaces for teams and AI agents.

How Daytona helps

Which of my sandboxes are burning CPU or memory right now?

surfaces live resource and usage metrics per running sandbox, so overconsumption shows up before it becomes a billing or performance surprise

How long will an idle sandbox sit around before it gets cleaned up?

applies the TTL and auto-pause interval configured on creation, so idle environments pause or expire automatically instead of running indefinitely

Can I move files into or out of a sandbox without handing out credentials?

generates pre-signed upload and download URLs for direct file transfer, scoped to that transfer without exposing account credentials

How do I know when a sandbox's state actually changes, without polling for it?

pushes state changes over a WebSocket subscription, so a fleet's transitions are visible as they happen rather than being inferred by querying repeatedly

Who on my team has access to which organization, and can I revoke it?

manages organization membership directly, listing and removing members without touching individual sandbox permissions

Which sandboxes are still exposed to expire outside the range I expect?

filters the sandbox list by a range on scheduled auto-destroy time, making it possible to spot sandboxes with lifecycle settings that don't match policy

all 23 features, with the evidence for each →

Languages

Not documented

Features

23 capabilities across 7 areas · 8 backed by code, an API document or a real run

Built from Daytona's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

What Daytona offers you

  • REST API6
  • Client SDKs3
  • Command-line interface2
  • Python scripting support1
  • Scripting language support1
Sandbox Lifecycle and Resource Management 3 capabilities This is the core of Daytona: creating and running sandboxes with control over how long they live, how much compute they consume, and when they pause or expire. Users interact with sandboxes through both the SDK and CLI to manage the full lifecycle from creation to deletion.
Sandbox lifecycle management verified Create, configure, pause, fork, and delete sandboxes, controlling auto-pause intervals, expiry, and proxy settings from the SDK or CLI. 33 releases · 24 other sources · first seen Aug 2026

Also counts toward: Command-line interface, Client SDKs

release 33 total

  • Exposes daytona.createSandbox(ctx, { autoStopInterval }) and daytona.runCode(ctx, { sandboxId, code, language }) APIs inside Convex actions for creating isolated sandboxes and running code (e.g.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ language: 'python') without holding an action open past Convex's limits. announced · Sep 2026 · source · release history
  • Adds outboundProxyUrl parameter to the sandbox create API call for routing sandbox traffic through an outbound proxy. updated · seen Sep 2026 · source · release history
  • POST /sandbox: request body changed 1.0 · Sep 2026 · source · release history
  • Adds server-side argument validation for fork and create-snapshot requests, returning HTTP 400 on invalid input. updated · seen Sep 2026 · source · release history
  • Adds autoDestroyAt range filter to the sandbox list SDK call, allowing callers to query sandboxes by their scheduled destruction time. updated · seen Aug 2026 · source · release history
  • Adds otelEndpointOverride to sandbox creation for overriding the OpenTelemetry endpoint per sandbox. Warm pool management and spot GPUs · seen Aug 2026 · source · release history

example

  • Route all outbound sandbox traffic through a corporate proxy at sandbox creation time. curl -X POST https://api.daytona.io/v1/sandboxes \ -H 'Authorization: Bearer <token>' \ -H 'Content-Type: application/json' \ -d '{"outboundProxyUrl": "http://proxy.corp.example.com:3128"}' updated · seen Sep 2026 · source
  • Create a sandbox that routes all outbound traffic through a corporate proxy — useful in air-gapped or regulated environments. sandbox.create({ ..., outboundProxyUrl: 'http://proxy.corp.example.com:3128' }) Snapshot operations by name and outbound proxy · seen Aug 2026 · source

api 22 total

  • GET /sandbox/{sandboxIdOrName} · source
  • DELETE /sandbox/{sandboxIdOrName} · source
  • GET /sandbox · source
  • POST /sandbox/{sandboxIdOrName}/pause · source
  • POST /sandbox/{sandboxIdOrName}/archive · source
  • GET /sandbox/paginated · source
Snapshot management verified Capture sandbox state as a snapshot and restore or activate it later, with the ability to filter snapshots by their source sandbox. 21 releases · 15 other sources · first seen Aug 2026

Also counts toward: Command-line interface, Client SDKs

release 21 total

  • Adds sourceSandboxId filter parameter to the snapshot list operation for targeted snapshot queries. updated · seen Sep 2026 · source · release history
  • Supports snapshot delete and activate by ID or name, expanding snapshot management beyond ID-only operations. updated · seen Sep 2026 · source · release history
  • POST /snapshots: request body changed 1.0 · Sep 2026 · source · release history
  • Promotes sandbox fork and create-snapshot to stable API, retiring the experimental aliases. updated · seen Sep 2026 · source · release history
  • Promotes sandbox fork and create-snapshot to stable API, replacing the previous experimental aliases. updated · seen Aug 2026 · source · release history
  • Promotes fork and create-snapshot from experimental to stable API, retiring the experimental aliases. updated · seen Aug 2026 · source · release history

example

  • List only snapshots derived from a specific source sandbox to audit lineage. curl -X GET 'https://api.daytona.io/v1/snapshots?sourceSandboxId=<sandboxId>' \ -H 'Authorization: Bearer <token>' updated · seen Sep 2026 · source
  • Activate a snapshot by human-readable name instead of opaque ID, useful in scripted pipelines. curl -X POST https://api.daytona.io/v1/snapshots/my-snapshot-name/activate \ -H 'Authorization: Bearer <token>' updated · seen Sep 2026 · source

api 13 total

  • DELETE /snapshots/{id} · source
  • POST /snapshots/{id}/deactivate · source
  • POST /snapshots · source
  • GET /runners/me/snapshots · source
  • POST /sandbox/{sandboxIdOrName}/snapshot · source
  • PATCH /admin/snapshots/{id}/general · source
Sandbox resource control verified Set CPU and memory limits on individual sandboxes to control how much compute each one is allowed to use. 3 releases · 3 other sources · first seen Aug 2026

release

  • Adds spot GPU support for sandboxes. Warm pool management and spot GPUs · seen Aug 2026 · source · release history
  • POST /sandbox/{sandboxIdOrName}/resize: response schema changed 1.0 · Aug 2026 · source · release history
  • Adds per-sandbox resource limits enabling granular CPU/memory control per sandbox. SDK Simplification & Per-Sandbox Resource Limits · seen Jul 2026 · source · release history

api

  • GET /organizations/{organizationId}/available-sandbox-classes · source
  • GET /sandbox/{sandboxId}/region-quota · source
  • POST /sandbox/{sandboxIdOrName}/resize · source
Sandbox Observability and Monitoring 1 capability Daytona surfaces what is happening inside and across sandboxes in real time, covering both live state changes and resource consumption. This gives operators and developers visibility at the individual sandbox level and across an entire organization.
Sandbox observability verified Subscribe to real-time sandbox state changes over WebSocket and view resource usage metrics at both the sandbox and organization level. 8 releases · 9 other sources · first seen Aug 2026

Also counts toward: Client SDKs

release 8 total

  • GET /sandbox: param maxGpu (query) added; param minGpu (query) added 1.0 · Sep 2026 · source · release history
  • Experimental API aliases for fork and create-snapshot are deprecated; callers must migrate to the stable endpoints. updated · seen Sep 2026 · source · release history
  • The experimental API aliases for sandbox fork and create-snapshot are deprecated — callers using the experimental endpoints must migrate to the stable API equivalents. updated · seen Aug 2026 · source · release history
  • Experimental API aliases for fork and create-snapshot are deprecated; callers using the experimental endpoints must migrate to the stable API. updated · seen Aug 2026 · source · release history
  • New endpoint GET /audit/scenarios 1.0 · Aug 2026 · source · release history
  • Adds WebSocket sandbox event subscription support to the Daytona SDKs, enabling real-time event-driven monitoring of sandbox state changes. Websocket sandbox event subscriptions in SDKs · seen Jul 2026 · source · release history

api 9 total

  • GET /sandbox/{sandboxId}/telemetry/traces/{traceId} · source
  • GET /sandbox/{sandboxId}/telemetry/metrics · source
  • GET /sandbox/{sandboxId}/telemetry/traces · source
  • GET /sandbox/{sandboxId}/telemetry/logs · source
  • GET /organizations/{organizationId}/usage · source
  • POST /sandbox/{sandboxId}/last-activity · source
Sandbox Data and Code Access 2 capabilities Daytona provides mechanisms to move files into and out of sandboxes and to bring code repositories directly into the sandbox environment. These capabilities support workflows where sandboxes need to be populated with code or artifacts at creation or runtime.
Sandbox file transfer verified Generate pre-signed URLs so files can be uploaded to or downloaded from a sandbox without requiring credentials at transfer time. 8 releases · 7 other sources · first seen Sep 2026

release 8 total

  • GET /object-storage/push-access: param regionId (query) added 1.0 · Oct 2026 · source · release history
  • New endpoint GET /organizations/{organizationId}/gpu-capacity⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ 1.0 · Sep 2026 · source · release history
  • GET /organizations/{organizationId}/available-sandbox-classes: response schema changed 1.0 · Sep 2026 · source · release history
  • Adds pre-signed download and upload URLs for sandbox files via the SDK, enabling direct S3-compatible file transfer without proxying through the API. updated · seen Aug 2026 · source · release history
  • Adds pre-signed download and upload URL generation for sandbox files, allowing direct S3-compatible file transfers without proxying through the API. Pre-signed file URLs and typed SDK errors · seen Aug 2026 · source · release history
  • Adds pre-signed download and upload URLs for sandbox file transfers via the SDK. updated · seen Aug 2026 · source · release history

api 7 total

  • GET /sandbox/{sandboxId}/signing-key · source
  • GET /sandbox/{sandboxIdOrName}/build-logs-url · source
  • POST /sandbox/{sandboxIdOrName}/ports/{port}/signed-preview-url/{token}/expire · source
  • GET /sandbox/{sandboxIdOrName}/ports/{port}/signed-preview-url · source
  • GET /preview/{sandboxId}/signing-key · source
  • GET /object-storage/push-access · source
Git integration shipped Clone a Git repository directly into a sandbox so code is immediately available inside the environment. 2 releases · 1 other source · first seen Sep 2026

release

  • Each agent request receives its own isolated sandbox created on demand from a snapshot you define, with the repository set as the workspace origin and a Cursor-minted short-lived GitHub token used for checkout — no long-lived credentials stored in the snapshot. announced · Sep 2026 · source · release history
  • Adds Git clone support. Docs Search, Git Clone & API 400s · seen Jul 2026 · source · release history

example

  • Catch specific git transport failures in automation to distinguish a network error from a rejected push. catch (err) { if (err.code === 'GIT_TRANSPORT_FAILED') { /* retry */ } if (err.code === 'GIT_REMOTE_REJECTED') { /* alert */ } } Snapshot operations by name and outbound proxy · seen Aug 2026 · source
Developer Integration and SDK 4 capabilities Daytona exposes a programmatic interface designed to keep integration effort low, with typed errors, configurable timeouts, and a simplified SDK surface. These capabilities are aimed at developers embedding sandbox functionality into larger systems or pipelines.
SDK error handling shipped Receive structured, typed error codes and HTTP 400 responses from the SDK and API to make error handling straightforward in code. 17 releases

release 17 total

  • Introduces typed git transport error codes GIT_TRANSPORT_FAILED and GIT_REMOTE_REJECTED in the SDK for programmatic handling of git remote failures. updated · seen Sep 2026 · source · release history
  • Propagates daemon error codes consistently across all SDKs for uniform error handling. updated · seen Sep 2026 · source · release history
  • Moves argument validation server-side, returning HTTP 400 responses for invalid inputs. updated · seen Sep 2026 · source · release history
  • Adds consistent daemon error code propagation across all SDKs. updated · seen Sep 2026 · source · release history
  • Propagates missing daemon error codes to all SDKs for consistent error handling across clients. updated · seen Aug 2026 · source · release history
  • Propagates daemon error codes consistently across all SDKs. updated · seen Aug 2026 · source · release history
SDK surface verified Use a simplified SDK interface to interact with the platform programmatically without needing to handle low-level API details directly. 4 releases · 2 other sources

Also counts toward: REST API

release

  • Exposes sandboxClass, warmPoolId, gpuType, desiredState, daemonVersion, and otelEndpointOverride fields directly on the Sandbox object in the SDK Sandbox class and warm pool fields on Sandbox · seen Aug 2026 · source · release history
  • Makes FileInfo.modifiedAt optional in the Python toolbox API client for compatibility with older runners. updated · seen Aug 2026 · source · release history
  • Adds warm pool management APIs across SDKs. Warm pool management and spot GPUs · seen Aug 2026 · source · release history
  • Simplifies the SDK surface to reduce integration complexity. SDK Simplification & Per-Sandbox Resource Limits · seen Jul 2026 · source · release history

api

SDK HTTP timeout configuration shipped Set client-side HTTP timeouts in the SDK so long-running sandbox operations do not cause the client to hang indefinitely. 5 releases

release

  • Adds DaytonaConfig.requestTimeoutMs to the TypeScript SDK for configurable client-side HTTP timeouts. Org members command and client-side HTTP timeout · seen Aug 2026 · source · release history
  • Makes the HTTP timeout configurable in the Go SDK to honor long execution timeouts. updated · seen Aug 2026 · source · release history
  • Go SDK HTTP timeout is now configurable, enabling reliable long-running executions that previously timed out. updated · seen Aug 2026 · source · release history
  • Go SDK now supports a configurable HTTP timeout to handle long-running executions reliably. updated · seen Aug 2026 · source · release history
  • Introduces client-side HTTP timeout configuration. Org members command and client-side HTTP timeout · seen Jul 2026 · source · release history
Documentation search shipped Search the product documentation from within Daytona without leaving the working environment. 1 release

release

  • Adds documentation search capability. Docs Search, Git Clone & API 400s · seen Jul 2026 · source · release history
Organization and Access Management 1 capability Daytona supports multi-user and multi-team use through organization-level configuration, membership controls, and invitation management. Administrators can set defaults such as region and experimental settings at the organization level.
Organization management verified Create and configure organizations, manage who belongs to them, send invitations, and set organization-wide defaults such as region. 28 releases · 31 other sources · first seen Aug 2026

Also counts toward: REST API

release 28 total

  • New endpoint PATCH /organizations/{organizationId}/default-queue-timeout⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ 1.0 · Sep 2026 · source · release history
  • Adds an organization members command to the CLI and SDK for listing org members. updated · seen Sep 2026 · source · release history
  • Adds an organization members CLI command for listing org members from the terminal. updated · seen Aug 2026 · source · release history
  • Adds organization members command to the CLI for listing members of an organization. updated · seen Aug 2026 · source · release history
  • Adds organization members command to the CLI for listing org members. updated · seen Aug 2026 · source · release history
  • Organizations (49 endpoints) — create, read, update, delete 1.0 · Aug 2026 · source · release history

api 31 total

  • PUT /organizations/{organizationId}/experimental-config · source
  • GET /organizations/{organizationId} · source
  • POST /organizations/{organizationId}/invitations · source
  • PATCH /organizations/{organizationId}/default-region · source
  • POST /organizations/invitations/{invitationId}/decline · source
  • POST /organizations · source
Security Hardening 2 capabilities Daytona applies a set of hardening measures to its client-side components and network connections to reduce exposure from misconfiguration or interception. These controls operate at the TLS, file permission, and connection layers.
CLI config file hardening shipped Write CLI configuration files with permissions restricted to the owning user so other accounts on the same system cannot read them. 6 releases

release

  • Experimental API aliases for sandbox fork and create-snapshot are deprecated — callers using the experimental endpoints must migrate to the stable equivalents. updated · seen Sep 2026 · source · release history
  • Experimental API aliases for fork and create-snapshot are deprecated and replaced by the stable API endpoints — callers using the experimental aliases must migrate to the stable equivalents. updated · seen Aug 2026 · source · release history
  • CLI config file is created with 0600 permissions, restricting access to the owning user. updated · seen Aug 2026 · source · release history
  • Creates CLI config files with 0600 permissions for tighter access control. updated · seen Aug 2026 · source · release history
  • CLI config file is now created with 0600 permissions, restricting access to the owning user only. updated · seen Aug 2026 · source · release history
  • CLI config file is now created with 0600 permissions, restricting access to the owner only. updated · seen Aug 2026 · source · release history
TLS enforcement shipped Enforce TLS verification on SDK and WebSocket connections to the API so that communication cannot be intercepted by an untrusted party. 5 releases · first seen Oct 2026

release

  • New endpoint POST /jobs/{jobId}/registry-mtls/{registryId}⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ 1.0 · Oct 2026 · source · release history
  • TLS verification is now enforced in the Ruby Socket.IO client. updated · seen Aug 2026 · source · release history
  • Enforces TLS verification in the Ruby Socket.IO client for hardened client security. updated · seen Aug 2026 · source · release history
  • Enforces TLS verification across the client security layer in 0.200.0. updated · seen Aug 2026 · source · release history
  • Enforces TLS verification in the Ruby Socket.IO client. updated · seen Aug 2026 · source · release history
Other 10 capabilities
Identity provider configuration verified Manage SAML or OIDC identity providers for an organization, including creating, listing, retrieving, updating, and testing connections. 9 releases · 11 other sources · first seen Aug 2026

release 9 total

  • New endpoint GET /organizations/{organizationId}/identity-providers/workos-sso-connections⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ 1.0 · Sep 2026 · source · release history
  • Removed endpoint POST /users/mfa/sms/enroll 1.0 · Sep 2026 · source · release history
  • New endpoint POST /organizations/{organizationId}/identity-providers 1.0 · Aug 2026 · source · release history
  • New endpoint GET /organizations/{organizationId}/identity-providers/{id} 1.0 · Aug 2026 · source · release history
  • New endpoint GET /organizations/{organizationId}/identity-providers 1.0 · Aug 2026 · source · release history
  • New endpoint GET /users/me/pending-sso-links 1.0 · Aug 2026 · source · release history

api 11 total

  • POST /organizations/{organizationId}/sso-enabled · source
  • POST /organizations/{organizationId}/identity-providers · source
  • DELETE /users/me/pending-sso-links/{id} · source
  • GET /organizations/{organizationId}/identity-providers/{id} · source
  • DELETE /organizations/{organizationId}/identity-providers/{id} · source
  • PATCH /organizations/{organizationId}/identity-providers/{id} · source
Convex integration shipped A Convex component that connects Daytona sandboxes to Convex backend actions, enabling sandbox creation, long-running background command execution with streamed logs, and live-queryable execution history for frontends. 3 releases · 3 other sources · first seen Sep 2026

Also counts toward: Python scripting support, Scripting language support

release

  • Provides runBackground for long-running command execution — returns an execution ID immediately and streams logs into a Convex row via a chain of scheduled functions, removing the 10-minute action ceiling. announced · Sep 2026 · source · release history
  • Surfaces daytona.listExecutions as a subscribable live query so frontends can render real-time execution history and log streaming without polling or websocket plumbing. announced · Sep 2026 · source · release history
  • Requires DAYTONA_API_KEY environment variable set via npx convex env set DAYTONA_API_KEY <key> to authenticate the component with Daytona. announced · Sep 2026 · source · release history

example

  • Build a code-interpreter Convex action that spins up an isolated sandbox, runs Python code, and exposes live execution history to the frontend via daytona.listExecutions. const daytona = new Daytona(components.daytona); export const codeInterpreter = action({ args: { code: v.string() }, handler: async (ctx, args) => { const { sandboxId } = await… announced · Sep 2026 · source
  • Register the Daytona component in your Convex app configuration so its reactive tables and APIs are available to your backend. import daytona from "@daytona/convex/convex.config.js"; app.use(daytona); announced · Sep 2026 · source
  • Install the Convex component and set your Daytona API key so Convex actions can create and manage sandboxes. npm install @daytona/convex npx convex env set DAYTONA_API_KEY dtn_... announced · Sep 2026 · source
API key management shipped Retrieve current API keys and create new ones for authentication. 5 releases · first seen Aug 2026

Also counts toward: REST API

release

Organization role management shipped Create, list, and update custom roles for organization members. 3 releases · first seen Aug 2026

Also counts toward: REST API

release

  • POST /sandbox/{sandboxIdOrName}/backup: response schema changed 1.0 · Aug 2026 · source · release history
  • PUT /organizations/{organizationId}/roles/{roleId}: request body changed; response schema changed 1.0 · Aug 2026 · source · release history
  • GET /organizations/{organizationId}/roles: response schema changed 1.0 · Aug 2026 · source · release history
Region and organization quota management shipped View, create, and update resource quotas for sandboxes within specific regions and organizations. 3 releases · first seen Aug 2026

Also counts toward: REST API

release

  • GET /admin/organizations/{organizationId}/quota/{regionId}/{sandboxClass}: response schema changed 1.0 · Aug 2026 · source · release history
  • POST /admin/organizations/{organizationId}/quota/{regionId}: request body changed; response schema changed 1.0 · Aug 2026 · source · release history
  • PATCH /organizations/{organizationId}/quota/{regionId}: request body changed 1.0 · Aug 2026 · source · release history
GPU capacity visibility shipped Provides endpoints to check available GPU capacity for organizations. 2 releases · first seen Sep 2026

release

  • GET /organizations/{organizationId}/gpu-capacity: response schema changed 1.0 · Oct 2026 · source · release history
  • New endpoint GET /organizations/{organizationId}/gpu-capacity⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ 1.0 · Sep 2026 · source · release history
Runner management shipped Delete execution runners, including forcing deletion in error states. 2 releases · first seen Aug 2026

Also counts toward: REST API

release

Sandbox recovery shipped Recover stopped or failed sandboxes to a running state without re-provisioning from scratch. 2 releases · first seen Aug 2026

release

  • POST /admin/sandbox/{sandboxId}/recover: response schema changed 1.0 · Aug 2026 · source · release history
  • POST /sandbox/{sandboxIdOrName}/recover: response schema changed 1.0 · Aug 2026 · source · release history
Cursor Self-Hosted Machines integration shipped Allows Cursor Cloud Agent workers to execute inside Daytona sandboxes using Linux containers or VMs instead of Cursor-hosted machines. 1 release · first seen Sep 2026

release

  • Adds support for Cursor Self-Hosted Machines integration, allowing Cursor Cloud Agent workers to execute inside Daytona sandboxes (Linux containers, Linux VMs via daytona-vm-medium snapshot, or Windows VMs via windows-medium snapshot) instead of Cursor-hosted machines. announced · Sep 2026 · source · release history
Sandbox class support shipped Supports defining sandbox pools with Linux containers, Linux VMs, and Windows VMs using specific snapshots or Dockerfiles. 1 release · first seen Sep 2026

release

  • Supports three sandbox classes per pool: Linux containers built from an included Dockerfile, Linux VMs from the daytona-vm-medium snapshot, and Windows VMs from the windows-medium snapshot, with pools defined per-snapshot. announced · Sep 2026 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Release-note detail over time

See how much detail Daytona puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

21 entries

  1. August 202615
  17. July 20266
    Show

    21 entries

    1. Warm pool management and spot GPUs seen Aug 18, 2026 · issue 049

      Daytona 0.205.0 adds warm pool management APIs, spot GPUGPUA graphics processing unit, a processor that performs many calculations in parallel. AI workloads use GPUs to speed up model training and inference. support, and OpenTelemetryOpenTelemetryAn open standard and set of tools for collecting traces, metrics and logs from applications. It lets services export observability data without tying instrumentation to one monitoring vendor. endpoint override for sandboxes.

      • Adds otelEndpointOverride to sandbox creation, enabling per-sandbox OpenTelemetry endpoint configuration.
      • Adds spot GPU support for sandboxes.
      • Adds warm pool management APIs across SDKs.

      3 details in Everything

    2. updated seen Aug 18, 2026 · issue 049

      Daytona promotes sandbox fork and snapshot creation to stable API, with improved client-side error signaling in the TypeScript SDK.

      • Promotes fork and create-snapshot operations from experimental to stable API, retiring the experimental aliases.
      • Distinguishes client-side argument validation errors from server-side 400 responses in the TypeScript SDK for clearer error handling.

      2 details in Everything

    3. updated seen Aug 17, 2026 · issue 048
      • Adds autoDestroyAt range filter to the sandbox list endpoint, enabling lifecycle-aware queries that scope results by scheduled destruction time.
      • Adds structured error responses with typed error codes to the SDK, giving programmatic access to failure reasons instead of raw HTTP status parsing.
    4. updated seen Aug 16, 2026 · issue 047
      • CLI config file is created with 0600 permissions, restricting access to the owning user.
      • TLS verification is now enforced in the Ruby Socket.IO client.
    5. updated seen Aug 15, 2026 · issue 046

      Daytona 0.201.0 adds pre-signed file transfer URLs, typed SDK error codes, and a sandbox list date-range filter.

      • Introduces pre-signed sandbox file download and upload URLs, allowing direct S3-compatibleS3-compatibleAn object-storage API that mirrors Amazon S3's HTTP interface, so any client or cyber tool written for AWS S3 works unchanged against any compliant storage backend. file transfers without proxying through the API.

      1 detail in Everything

    6. 1.0 Aug 14, 2026 · issue 045

      API surface changed: +12 endpoints, 63 modified

      API change

      API surface changed: +12 endpoints, 63 modified

      • + DELETE /organizations/{organizationId}/identity-providers/{id}
      • + DELETE /users/me/pending-sso-links/{id}
      • + GET /audit/scenarios
      • + GET /organizations/{organizationId}/identity-providers
      • + GET /organizations/{organizationId}/identity-providers/{id}
      • + GET /runners/me/snapshots
      • + GET /users/me/pending-sso-links
      • + PATCH /organizations/{organizationId}/identity-providers/{id}
      • + POST /organizations/{organizationId}/identity-providers
      • + POST /organizations/{organizationId}/identity-providers/test-connection
      • + POST /organizations/{organizationId}/sso-enabled
      • + POST /users/me/pending-sso-links/{id}/confirm
      • ~ DELETE /admin/runners/{id}: param force (query) added
      • ~ DELETE /runners/{id}: param force (query) added
      • ~ DELETE /sandbox/{sandboxIdOrName}: response schema changed
      • ~ DELETE /sandbox/{sandboxIdOrName}/ssh-access: response schema changed
      • ~ GET /admin/organizations/{organizationId}/quota/{regionId}/{sandboxClass}: response schema changed
      • ~ GET /admin/users/{id}: response schema changed
      • ~ GET /api-keys: response schema changed
      • ~ GET /api-keys/current: response schema changed
      • ~ GET /api-keys/{name}: response schema changed
      • ~ GET /config: response schema changed
      • ~ GET /organizations: response schema changed
      • ~ GET /organizations/invitations: response schema changed
      • ~ GET /organizations/{organizationId}: response schema changed
      • ~ GET /organizations/{organizationId}/invitations: response schema changed
      • ~ GET /organizations/{organizationId}/roles: response schema changed
      • ~ GET /organizations/{organizationId}/users: response schema changed
      • ~ GET /sandbox: response schema changed
      • ~ GET /sandbox/for-runner: response schema changed
      • ~ GET /sandbox/paginated: response schema changed
      • ~ GET /sandbox/{sandboxIdOrName}: response schema changed
      • ~ GET /sandbox/{sandboxIdOrName}/ancestors: response schema changed
      • ~ GET /sandbox/{sandboxIdOrName}/forks: response schema changed
      • ~ GET /sandbox/{sandboxIdOrName}/parent: response schema changed
      • ~ GET /sandbox/{sandboxId}/organization: response schema changed
      • ~ GET /sandbox/{sandboxId}/region-quota: response schema changed
      • ~ GET /snapshots: param sourceSandboxId (query) added; response schema changed
      • ~ GET /snapshots/{id}: response schema changed
      • ~ GET /users/me: response schema changed
      • ~ PATCH /admin/organizations/{organizationId}/quota/{regionId}: request body changed
      • ~ PATCH /admin/snapshots/{id}/general: response schema changed
      • ~ PATCH /organizations/{organizationId}/quota/{regionId}: request body changed
      • ~ POST /admin/organizations: response schema changed
      • ~ POST /admin/organizations/{organizationId}/quota/{regionId}: request body changed; response schema changed
      • ~ POST /admin/sandbox/{sandboxId}/recover: response schema changed
      • ~ POST /admin/users: request body changed
      • ~ POST /api-keys: request body changed; response schema changed
      • ~ POST /organizations: response schema changed
      • ~ POST /organizations/invitations/{invitationId}/accept: response schema changed
      • ~ POST /organizations/{organizationId}/invitations: response schema changed
      • ~ POST /organizations/{organizationId}/roles: request body changed; response schema changed
      • ~ POST /organizations/{organizationId}/users/{userId}/access: response schema changed
      • ~ POST /sandbox: request body changed; response schema changed
      • ~ POST /sandbox/{sandboxIdOrName}/archive: response schema changed
      • ~ POST /sandbox/{sandboxIdOrName}/autoarchive/{interval}: response schema changed
      • ~ POST /sandbox/{sandboxIdOrName}/autodelete/{interval}: response schema changed
      • ~ POST /sandbox/{sandboxIdOrName}/autopause/{interval}: response schema changed
      • ~ POST /sandbox/{sandboxIdOrName}/autostop/{interval}: response schema changed
      • ~ POST /sandbox/{sandboxIdOrName}/backup: response schema changed
      • ~ POST /sandbox/{sandboxIdOrName}/fork: response schema changed
      • ~ POST /sandbox/{sandboxIdOrName}/network-settings: response schema changed
      • ~ POST /sandbox/{sandboxIdOrName}/pause: response schema changed
      • ~ POST /sandbox/{sandboxIdOrName}/public/{isPublic}: response schema changed
      • ~ POST /sandbox/{sandboxIdOrName}/recover: response schema changed
      • ~ POST /sandbox/{sandboxIdOrName}/resize: response schema changed
      • ~ POST /sandbox/{sandboxIdOrName}/snapshot: response schema changed
      • ~ POST /sandbox/{sandboxIdOrName}/start: response schema changed
      • ~ POST /sandbox/{sandboxIdOrName}/stop: response schema changed
      • ~ POST /sandbox/{sandboxIdOrName}/ttl/{ttlMinutes}: response schema changed
      • ~ POST /snapshots: response schema changed
      • ~ POST /snapshots/{id}/activate: response schema changed
      • ~ PUT /organizations/{organizationId}/invitations/{invitationId}: response schema changed
      • ~ PUT /organizations/{organizationId}/roles/{roleId}: request body changed; response schema changed
      • ~ PUT /sandbox/{sandboxIdOrName}/secrets: response schema changed
      • New endpoint DELETE /organizations/{organizationId}/identity-providers/{id}
      • New endpoint DELETE /users/me/pending-sso-links/{id}
      • New endpoint GET /audit/scenarios
      • New endpoint GET /organizations/{organizationId}/identity-providers
      • New endpoint GET /organizations/{organizationId}/identity-providers/{id}
      +70 more show less
      • New endpoint GET /runners/me/snapshots
      • New endpoint GET /users/me/pending-sso-links
      • New endpoint PATCH /organizations/{organizationId}/identity-providers/{id}
      • New endpoint POST /organizations/{organizationId}/identity-providers
      • New endpoint POST /organizations/{organizationId}/identity-providers/test-connection
      • New endpoint POST /organizations/{organizationId}/sso-enabled
      • New endpoint POST /users/me/pending-sso-links/{id}/confirm
      • DELETE /admin/runners/{id}: param force (query) added
      • DELETE /runners/{id}: param force (query) added
      • DELETE /sandbox/{sandboxIdOrName}: response schema changed
      • DELETE /sandbox/{sandboxIdOrName}/ssh-access: response schema changed
      • GET /admin/organizations/{organizationId}/quota/{regionId}/{sandboxClass}: response schema changed
      • GET /admin/users/{id}: response schema changed
      • GET /api-keys: response schema changed
      • GET /api-keys/current: response schema changed
      • GET /api-keys/{name}: response schema changed
      • GET /config: response schema changed
      • GET /organizations: response schema changed
      • GET /organizations/invitations: response schema changed
      • GET /organizations/{organizationId}: response schema changed
      • GET /organizations/{organizationId}/invitations: response schema changed
      • GET /organizations/{organizationId}/roles: response schema changed
      • GET /organizations/{organizationId}/users: response schema changed
      • GET /sandbox: response schema changed
      • GET /sandbox/for-runner: response schema changed
      • GET /sandbox/paginated: response schema changed
      • GET /sandbox/{sandboxIdOrName}: response schema changed
      • GET /sandbox/{sandboxIdOrName}/ancestors: response schema changed
      • GET /sandbox/{sandboxIdOrName}/forks: response schema changed
      • GET /sandbox/{sandboxIdOrName}/parent: response schema changed
      • GET /sandbox/{sandboxId}/organization: response schema changed
      • GET /sandbox/{sandboxId}/region-quota: response schema changed
      • GET /snapshots: param sourceSandboxId (query) added; response schema changed
      • GET /snapshots/{id}: response schema changed
      • GET /users/me: response schema changed
      • PATCH /admin/organizations/{organizationId}/quota/{regionId}: request body changed
      • PATCH /admin/snapshots/{id}/general: response schema changed
      • PATCH /organizations/{organizationId}/quota/{regionId}: request body changed
      • POST /admin/organizations: response schema changed
      • POST /admin/organizations/{organizationId}/quota/{regionId}: request body changed; response schema changed
      • POST /admin/sandbox/{sandboxId}/recover: response schema changed
      • POST /admin/users: request body changed
      • POST /api-keys: request body changed; response schema changed
      • POST /organizations: response schema changed
      • POST /organizations/invitations/{invitationId}/accept: response schema changed
      • POST /organizations/{organizationId}/invitations: response schema changed
      • POST /organizations/{organizationId}/roles: request body changed; response schema changed
      • POST /organizations/{organizationId}/users/{userId}/access: response schema changed
      • POST /sandbox: request body changed; response schema changed
      • POST /sandbox/{sandboxIdOrName}/archive: response schema changed
      • POST /sandbox/{sandboxIdOrName}/autoarchive/{interval}: response schema changed
      • POST /sandbox/{sandboxIdOrName}/autodelete/{interval}: response schema changed
      • POST /sandbox/{sandboxIdOrName}/autopause/{interval}: response schema changed
      • POST /sandbox/{sandboxIdOrName}/autostop/{interval}: response schema changed
      • POST /sandbox/{sandboxIdOrName}/backup: response schema changed
      • POST /sandbox/{sandboxIdOrName}/fork: response schema changed
      • POST /sandbox/{sandboxIdOrName}/network-settings: response schema changed
      • POST /sandbox/{sandboxIdOrName}/pause: response schema changed
      • POST /sandbox/{sandboxIdOrName}/public/{isPublic}: response schema changed
      • POST /sandbox/{sandboxIdOrName}/recover: response schema changed
      • POST /sandbox/{sandboxIdOrName}/resize: response schema changed
      • POST /sandbox/{sandboxIdOrName}/snapshot: response schema changed
      • POST /sandbox/{sandboxIdOrName}/start: response schema changed
      • POST /sandbox/{sandboxIdOrName}/stop: response schema changed
      • POST /sandbox/{sandboxIdOrName}/ttl/{ttlMinutes}: response schema changed
      • POST /snapshots: response schema changed
      • POST /snapshots/{id}/activate: response schema changed
      • PUT /organizations/{organizationId}/invitations/{invitationId}: response schema changed
      • PUT /organizations/{organizationId}/roles/{roleId}: request body changed; response schema changed
      • PUT /sandbox/{sandboxIdOrName}/secrets: response schema changed

      75 details in Everything

    7. updated seen Aug 14, 2026 · issue 045

      Daytona 0.200.0 enforces TLS verification and adds a configurable HTTP timeout to the Go SDK.

      • Makes the HTTP timeout configurable in the Go SDK to honor long execution timeouts.
      • Creates CLI config files with 0600 permissions for tighter access control.

      2 details in Everything

    8. updated seen Aug 13, 2026 · issue 044

      Daytona 0.201.0 adds pre-signed file upload/download URLs, typed SDK error codes, and autoDestroyAt range filtering for sandbox listing.

      • Adds autoDestroyAt range filter to the sandbox list API, enabling lifecycle-aware sandbox queries.
      • Adds pre-signed sandbox file download and upload URLs for direct, credential-free file transfers to/from sandboxes.
      • Adds structured error responses with typed error codes to the SDK, making programmatic error handling against the API practical.

      3 details in Everything

    9. Snapshot operations by name and outbound proxy seen Aug 12, 2026 · issue 043

      Daytona 0.204.0 adds snapshot ops by name, outbound proxy on sandbox create, and typed git transport errors.

      • Adds support for snapshot delete and activate by ID or name across the SDK and CLI.
      • Adds sourceSandboxId filter parameter to the snapshot list SDK call.
      • Adds outboundProxyUrl parameter to the sandbox create SDK call for outbound proxy configuration.
      • Introduces GIT_TRANSPORT_FAILED and GIT_REMOTE_REJECTED typed error codes across all SDKs.

      4 details in Everything

    10. updated seen Aug 12, 2026 · issue 043

      Daytona 0.200.0 enforces TLS verification, tightens config file permissions, and adds configurable Go SDK HTTP timeouts.

      • Go SDK HTTP timeout is now configurable, enabling reliable long-running executions that previously timed out.
      • Enforces TLS verification in the Ruby Socket.IO client for hardened client security.
      • CLI config file is now created with 0600 permissions, restricting access to the owning user only.

      3 details in Everything

    11. updated seen Aug 11, 2026 · issue 042
      └──▷ BREAKING ON UPGRADE
      • !The minimum supported Python version is raised to 3.10; sandboxes or integrations running on older Python versions will break on upgrade.
    12. updated seen Aug 10, 2026 · issue 041

      Daytona 0.199.0 adds time-to-livetime-to-liveTime to live, a limit on how long data remains valid or how far a packet can travel. Caches use a time limit; IP packets use a hop limit. control over sandbox lifetimes and raises the Python floor to 3.10.

      └──▷ BREAKING ON UPGRADE
      • !Minimum supported Python version raised to 3.10; setups running Python below 3.10 will break on upgrade.
    13. updated seen Aug 9, 2026 · issue 040

      Daytona 0.200.0 enforces TLS verification, tightens config file permissions, and adds configurable HTTP timeouts to the Go SDK.

      • Go SDK now supports a configurable HTTP timeout to handle long-running executions reliably.
      • Enforces TLS verification in the Ruby Socket.IO client.
      • CLI config file is now created with 0600 permissions, restricting access to the owner only.
      • Enforces TLS verification across the client security layer in 0.200.0.

      4 details in Everything

    14. updated seen Aug 8, 2026 · issue 039

      Daytona 0.199.0 adds sandbox time-to-livetime-to-liveTime to live, a limit on how long data remains valid or how far a packet can travel. Caches use a time limit; IP packets use a hop limit. (TTLTTLTime to live, a limit on how long data remains valid or how far a packet can travel. Caches use a time limit; IP packets use a hop limit.) control via SDK and CLI.

      └──▷ BREAKING ON UPGRADE
      • !Python SDK now requires Python >=3.10; installations running older Python versions will break on upgrade.
    15. 1.0 seen Aug 4, 2026 · issue 035

      API surface changed: 5 deprecated

      API change

      API surface changed: 5 deprecated

      • ⚠ GET /sandbox/paginated
      • ⚠ GET /sandbox/{sandboxIdOrName}/build-logs
      • ⚠ GET /secret
      • ⚠ GET /snapshots/{id}/build-logs
      • ⚠ POST /sandbox/{sandboxIdOrName}/backup
      └──▷ BREAKING ON UPGRADE
      • !Deprecated endpoint GET /sandbox/paginated (still works)
      • !Deprecated endpoint GET /sandbox/{sandboxIdOrName}/build-logs (still works)
      • !Deprecated endpoint GET /secret (still works)
      • !Deprecated endpoint GET /snapshots/{id}/build-logs (still works)
      • !Deprecated endpoint POST /sandbox/{sandboxIdOrName}/backup (still works)
    16. Org members command and client-side HTTP timeout seen Jul 31, 2026 · issue 031

      Daytona adds an org members command and client-side HTTP timeout support.

      • Adds an org members command for managing organization membership.
      • Introduces client-side HTTP timeout configuration.

      2 details in Everything

    17. Sandbox metrics and auto-pause interval support seen Jul 25, 2026 · issue 025

      Daytona adds sandbox metrics visibility and configurable auto-pause intervals for sandboxes.

      • Adds sandbox metrics to surface resource and usage data for running sandboxes.
      • Supports configurable auto-pause intervals, letting users control how long a sandbox idles before pausing.

      2 details in Everything

    18. Websocket sandbox event subscriptions in SDKs seen Jul 25, 2026 · issue 025

      Daytona SDKs gain WebSocketWebSocketA protocol that upgrades an HTTP connection into a persistent, full-duplex channel, letting a server push data to a client without repeated polling. Cyber tools use it for real-time event streaming and live command output.-based sandbox event subscriptions for real-time sandbox lifecycle updates.

      • Adds WebSocket sandbox event subscription support to the Daytona SDKs, enabling real-time event-driven monitoring of sandbox state changes.

      1 detail in Everything

    19. Docs Search, Git Clone & API 400s seen Jul 23, 2026 · issue 023

      Daytona adds docs search, Git clone support, and improved API 400 error handling.

      • Adds documentation search capability.
      • Adds Git clone support.
      • Adds API 400 error responses for improved developer feedback.

      3 details in Everything

    20. SDK Simplification & Per-Sandbox Resource Limits seen Jul 23, 2026 · issue 023

      Daytona introduces SDK simplification and per-sandbox resource limits for finer workload control.

      • Simplifies the SDK surface to reduce integration complexity.
      • Adds per-sandbox resource limits enabling granular CPUCPUThe main general-purpose processor in a computer. It runs application instructions and coordinates work with memory and other hardware./memory control per sandbox.

      2 details in Everything

    21. Sandbox Forking SDK & Org Metrics seen Jul 23, 2026 · issue 023

      Daytona adds sandbox forking via SDK and organization-level metrics.

      • Adds sandbox forking capability accessible through the SDK.
      • Introduces organization-level metrics for monitoring sandbox usage.

      2 details in Everything

    Articles

    1 article · updated Nov 4, 2026

    Where Daytona turns up in what others publish: how-tos, attack reports that name it, and incident write-ups. A row says why it is here and quotes where the article names it; the link goes to the publisher.

    Tutorials & guides 1

    • Discord Image Generation Bot with Daytona DEV Community
      This project demonstrates how to build a Discord bot that generates images from text prompts using the Prodia API , while utilizing Daytona for an optimized and scalable development environment.
      2 more quotes
      With Daytona's devcontainers, the bot ensures a standardized, fast, and efficient setup process.
      Install Daytona First, make sure you have Daytona installed.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    compare.md

      Free the public facts, no sign-in Any paid plan all other sections Researcher & Business pricing history and category rank

      my-toolchain — 0 tools

        Betas, release candidates and previews. Turn it off to see final releases only. It also applies to changes you ask for over MCP when you're signed in.
        browse all tools → score card for your toolchain →
        cyber-toolchain / feedback

        Send us feedback