Daytona

“# Persistence Daytona sandboxes are persistent by default. Stopping a sandbox does not destroy it: the sandbox keeps its identity, its filesystem, and its configuration, and can be started again at any point with all files, installed packages, and repositories intact. A sandbox is only deleted when you delete it, mark it as [ephemeral](https://www.daytona.io/docs/en/sandboxes.md#ephemeral-sandboxes), or set an [auto-delete interval](https://www.daytona.io/docs/en/sandboxes.md#auto-delete-interval). Per”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“shots.md#create-snapshot-from-sandbox)</u> to capture filesystem state, then create a new sandbox from that snapshot. Forking creates a duplicate of a Linux VM sandbox's filesystem and memory state in a new sandbox. The forked sandbox is fully independent: it can be started, stopped, and deleted without affecting the original. Daytona tracks the parent-child relationship in a fork tree, so you can trace a fork's lineage back to the sandbox it was created from. You can fork a fork to build branches. The parent sandbox cannot be deleted while it has active fork children. A fork of a [KVM sandbox](#nested-virtualization) inherits the `kvm` setting. Forking a”

Source daytona.io

“ is preserved through <u>[**pause / resume**](https://www.daytona.io/docs/en/sandboxes.md#pause--resume-sandboxes)</u>: pausing freezes the VM with memory intact, resuming continues all processes from the point they were frozen. Use <u>[**hot snapshots**](https://www.daytona.io/docs/en/snapshots.md#create-snapshot-from-sandbox)</u> or <u>[**forks**](https://www.daytona.io/docs/en/sandboxes.md#fork-sandboxes)</u> to capture memory. | | GPU | Ephemeral by design: deleted on stop, and memory is not preserved. Use <u>[**volumes**](https://www.daytona.io/docs/en/volumes.”

Source daytona.io

“ | | Stopped | ✗ | ✗ | ✓ | Billed for reserved disk only. <u>[**Ephemeral sandboxes**](https://www.daytona.io/docs/en/sandboxes.md#ephemeral-sandboxes) </u> and <u>[**GPU sandboxes**](https://www.daytona.io/docs/en/sandboxes.md#gpu-sandboxes)</u> are automatically deleted when stopped, so stopped billing does not apply to them. | | Paused | ✗ | ✗ | ✓ | Billed for reserved disk only. The preserved memory state is not billed. Supported ”

Source daytona.io

“lt. Daytona also provides [VM sandboxes](#vm-sandboxes) with a dedicated **Linux VM** or **Windows** operating system, [GPU sandboxes](#gpu-sandboxes) with **NVIDIA** and **AMD GPU** acceleration for model inference, fine-tuning, and GPU-accelerated compute, and [macOS sandboxes](#macos-sandboxes) running on dedicated Apple silicon hardware. <DocLinkCardGrid> <DocLinkCard title="Container" href="#create-sandboxes" icon="package" description="Default Linux container runtime for running processes and executing code." features={['<90ms', 'Dynamic builds', '”

Source daytona.io

“s managed by Daytona and available to all organizations: | **Region** | **Target** | | ------------- | ---------- | | United States | **`us`** | | Europe | **`eu`** | ```python from daytona import Daytona, DaytonaConfig # Configure Daytona to use the US region config = DaytonaConfig( target="us" ) # Initialize the Daytona client with the specified configuration daytona = Daytona(config) # Create a sandbox in the US region sandbox = daytona.create() ``` ```typescript import { Daytona } from '@daytona/sdk' // Configure Daytona to use the US region const daytona = n”

Source daytona.io

“ew sandboxes can start from the same snapshot. Daytona provides default snapshots for creating sandboxes. You can also create snapshots from images, capture the state of existing sandboxes, or create warm pools for a snapshot: - [**Create snapshots from an image**](#create-snapshots): define the base operating system, language runtimes, packages, and project-level setup in an image or Dockerfile, and Daytona builds it into a snapshot you can use to create sandboxes - [**Create snapshots from a sandbox**](#create-snapshot-from-sandbox): captures and persists a sandbox's current ”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“# Computer Use Computer Use enables programmatic control of desktop environments within sandboxes. It provides mouse, keyboard, screenshot, screen recording, and display operations for automating GUI interactions and testing desktop applications. Computer Use and [VNC](https://www.daytona.io/docs/en/vnc-access.md) work together to enable both manual and automated desktop interactions. VNC provides the visual interface for users to manually interact with the ”

Source daytona.io

“access to a full composable computer where they can install packages, run servers, compile code, and manage processes. Sandboxes run as **Linux containers** by default. Daytona also provides [VM sandboxes](#vm-sandboxes) with a dedicated **Linux VM** or **Windows** operating system, [GPU sandboxes](#gpu-sandboxes) with **NVIDIA** and **AMD GPU** acceleration for model inference, fine-tuning, and GPU-accelerated compute, and [macOS sandboxes](#macos-sandboxes) running on dedicated Apple silicon hardware. <DocLinkCardGrid> <DocLinkCard title="Container" href="#create-sandboxes" icon="package" d”

Source daytona.io

“view URLs require a token unless the sandbox is public preview = sandbox.get_preview_link(3000) print(preview.url) # https://3000-{sandboxId}.{proxy-domain} print(preview.token) # sent via the x-daytona-preview-token header ``` ```typescript import { Daytona } from '@daytona/sdk' const daytona = new Daytona() const sandbox = await daytona.create() // Preview URLs require a token unless the sandbox is public const preview = await sandbox.getPreviewLink(3000) console.log(preview.url) // https://3000-{sandboxId}.{proxy-domain} console.log(preview.token) // sent via the x-daytona-preview-token ”

Source daytona.io

“d-host) to forward your value unchanged. ## WebSocket support The preview proxy fully supports WebSocket connections. WebSocket upgrade requests (`Upgrade: websocket`) are automatically detected and proxied. WebSocket connections skip the preview warning page. ## Reserved ports The following ports are reserved for internal services and always require authentication, even on public sandboxes: | Port | Service | | ----------- | ----------------------------------------- | | **`22222`** | [**Web** terminal](https://www.daytona.io/docs/en/web-termin”

Source daytona.io

“Customer can run a custom preview proxy under their domain; not evidenced as platform-managed CNAME/TLS binding. Custom proxy implementation required.”

Source daytona.io

“# Preview Daytona provides preview URLs for accessing services running in your sandboxes. Any process listening for HTTP traffic on ports `1` - `65535` can be previewed through a generated URL. Daytona supports two types of preview URLs, each with a different authentication mechanism: - [Standard preview URL](#standard-preview-url) uses the sandbox ID in the URL and requires a separate token for authentication. That token is sandbox-wide and cannot be ”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“ and above; restricted on Tier 1 and 2 | <u>[**Network limits**](https://www.daytona.io/docs/en/network-limits.md)</u>: block all, CIDR allow list, domain allow list, or <u>[**outbound proxy**](https://www.daytona.io/docs/en/network-limits.md#outbound-proxy)</u> | | Internet to sandbox | Authenticated preview URLs and SSH access | <u>[**Preview tokens and signed URLs**](https://www.daytona.io/docs/en/preview.md)</u> and <u>[**SSH tokens**](https://www.daytona.io/docs/en/ssh-access.md)</u>; the **`public`** flag opts previews out of authentication | | Sandbox to sandbox | No shared network ”

Source daytona.io

“network. [Linked sandboxes](https://www.daytona.io/docs/en/sandboxes.md#linked-sandboxes) are the deliberate exception: children are scheduled onto the same runner as their parent and joined into a link network where each sandbox is reachable by name, while remaining isolated from every sandbox outside the group. ```python from daytona import CreateSandboxFromSnapshotParams, Daytona daytona = Daytona() parent = daytona.create() # Only linked sandboxes share a network; everything else is isolated child = daytona.create(CreateSandboxFromSnapshotParams( linked_sandbox=parent.id, ephemeral=True, )) # Sandboxes on the link network are reachabl”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“curl 'https://app.daytona.io/api/api-keys' \ --header 'X-Daytona-Organization-ID: YOUR_ORGANIZATION_ID' \ --header 'Authorization: Bearer YOUR_JWT_TOKEN' ``` ## Get current API key Get details of the API key used to authenticate the current request. ```bash curl 'https://app.daytona.io/api/api-keys/current' \ --header 'X-Daytona-Organization-ID: YOUR_ORGANIZATION_ID' \ --header 'Authorization: Bearer YOUR_API_KEY' ``` ## Get API key Get a single API key by name. ```bash curl 'https://app.daytona.io/api/api-keys/my-api-key' \ --header 'X-Daytona-Organization-ID: YOU”

Source daytona.io

“{ "openapi": "3.0.0", "info": { "contact": { "email": "[email protected]", "name": "Daytona Platforms Inc.", "url": "https://www.daytona.io" }, "description": "Daytona AI platform API Docs", "license": { "name": "Apache-2.0", "url": "https://www.apache.org/licenses/LICENSE-2.0" }, "title": "Daytona", "version": "1.0" }, "servers"”

Source daytona.io

“# CLI Daytona provides command-line access to core features for interacting with Daytona Sandboxes, including managing their lifecycle, snapshots, and more. The CLI reference lists all commands supported by the `daytona` command-line tool, complete with a description of their behavior, and any supported flags. You can access this documentation on a per-command basis by appending the `--help`/`-h` flag when invoking `daytona`. ## Installation Install the Da”

Source daytona.io

“rom daytona import Daytona daytona = Daytona() sandbox = daytona.create() ``` ```typescript import { Daytona } from '@daytona/sdk' const daytona = new Daytona() const sandbox = await daytona.create() ``` ```ruby require 'daytona' daytona = Daytona::Daytona.new sandbox = daytona.create ``` ```go package main import ( "context" "github.com/daytona/clients/sdk-go/pkg/daytona" ) func main() { client, _ := daytona.NewClient() ctx := context.Background() _, _ = client.Create(ctx, nil) } ``` ```java import io.daytona.sdk.Daytona; import io.daytona.sdk.Sandbox; pub”

Source daytona.io

“# SSH Access Daytona provides SSH access to your sandboxes using token-based authentication. This allows you to connect from local terminals, IDEs, and development tools without installing additional software. ## Access from Dashboard Create an SSH access token directly from the [Daytona Dashboard ↗](https://app.daytona.io/dashboard/sandboxes). 1. Go to [Sandboxes ↗](https://app.daytona.io/dashboard/sandboxes) 2. Locate the sandbox you want to cre”

Source daytona.io

“ ```bash curl 'https://proxy.app.daytona.io/toolbox/{sandboxId}/files/folder?path=&mode=' \ --request POST ``` ### Upload files Daytona provides methods to upload a single or multiple files in sandboxes. #### Upload a single file Upload a single file by providing the content to upload and the path to the file to upload it to. ```python # Upload from memory (small files) content = b"Hello, World!" sandbox.fs.upload_file(content, "remote_file.txt") # Upload from a local file path (streams large files) sandbox.fs.upload_file("local_file.txt", "remote_file.txt") ``` ”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“Snapshots from private registries documents pulling external private images; it does not establish a general hosted private image registry. Daytona stores snapshots.”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“Go, and Ruby SDKs. ## Installation Daytona provides multiple options to install the agent skill. ### Skills ```bash npx skills add https://github.com/daytona/skills --skill daytona ``` ### Claude Code (Plugin) ```bash claude plugin marketplace add daytona/skills claude plugin install daytona@daytona --scope user ``` Scope options: `user` (all projects), `project` (shared via git), `local` (gitignored). ### Manual Clone the Daytona skills repository: ```bash git clone https://github.com/daytona/skills.git ``` Copy the `daytona` subdirectory into your agent's `skills` directory: | **Agent** | **Skill directory** ”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“# Daytona MCP Server Daytona Model Context Protocol (MCP) server enables AI agents to interact with [Daytona Sandboxes](https://www.daytona.io/docs/en/sandboxes.md) programmatically. This guide covers how to set up and use the MCP server with various AI agents. ## Install Daytona CLI Install the Daytona CLI to manage the MCP server. ```bash brew install daytonaio/cli/daytona ``` ```bash powershell -Command "irm https://get.daytona.io/windows | iex" ```”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“ sandbox. Instead of an environment variable holding the actual API key, the sandbox holds an opaque placeholder token. An outbound proxy replaces the placeholder with the real value before the request reaches its destination, and only when the request goes to a host you have allowed. This lets you give a sandbox access to a credential such as an LLM API key or a database password while keeping the plaintext out of the sandbox environment, file system, process arguments, and logs. Code running in the sandbox can use the credential to reach an approved host, but cannot read the value, and cannot send it to any other host as long as the secret has a [host allowlist](#”

Source daytona.io

“This creates a sandbox named `claude-sandbox`, visible in your [Dashboard](https://app.daytona.io/dashboard/sandboxes). The default Daytona snapshot includes Claude Code, so the command above is all you need. :::tip Need more power? Pass `--snapshot daytona-large` or `--snapshot daytona-medium` flag to increase your sandbox resources. See [default snapshots](https://www.daytona.io/docs/en/snapshots.md#default-snapshots) for resource details. ::: ### Connect to the Sandbox SSH into your sandbox: ```bash daytona ssh claude-sandbox ``` You now have an interactive terminal session inside the sandbox. ### Run C”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“app.daytona.io/dashboard) 2. Navigate to **Sandboxes** section 3. Open the **Sandbox Details** sheet for any sandbox 4. Use the **Logs**, **Traces**, and **Metrics** tabs to inspect the collected telemetry data ```python # Historical resource metrics (CPU, memory, disk) samples = sandbox.get_metrics() for s in samples: print(f"{s.timestamp}: CPU {s.cpu_used_pct}%") ``` ```typescript // Historical resource metrics (CPU, memory, disk) const samples = await sandbox.getMetrics() for (const s of samples) { console.log(`${s.timestamp.toISOString()} CPU: ${s.cpuUsedPct}%`) } ``` ```ruby # Historical resource”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“y provider step by step, with instructions and screenshots for each screen you configure on the identity provider side. Connections can use SAML or OIDC. Daytona lists the connections you configure on the SSO page. Managing SSO requires the **`manage:sso`** permission. Organization owners and members with the **SSO Admin** assignment can open the SSO page. See [roles](https://www.daytona.io/docs/en/organizations.md#roles). :::note SSO is available on the Enterprise plan for collaborative organizations. Personal organizations cannot configure SSO. ::: ## Configure SSO Connect an identity provi”

Source daytona.io

“ate to external services without hardcoding credentials into your source, snapshots, or sandbox environment variables. Secrets are organization-scoped, encrypted credentials that Daytona injects into a sandbox's outbound HTTPS traffic without ever placing the plaintext inside the sandbox. Instead of an environment variable holding the actual API key, the sandbox holds an opaque placeholder token. An outbound proxy replaces the placeholder with the real value before the request reaches its destination, and only when the request goes to a host you have allowed. This lets you give a sandbox access to a credential such”

Source daytona.io

“# Organizations Daytona provides organizations as a way to group resources and enable collaboration. Users can work individually in their personal organization or together in a collaborative organization. Go to [Daytona Dashboard ↗](https://app.daytona.io/dashboard) to manage your organizations, or use the [API](https://www.daytona.io/docs/en/tools/api.md#daytona/tag/organizations) to manage them programmatically. ## Personal vs Collaborative Every Daytona”

Source daytona.io

“ication. That token is sandbox-wide and cannot be revoked — use it for your own programmatic access, not for sharing - [Signed preview URL](#signed-preview-url) embeds the authentication token directly in the URL, requiring no headers. The token is bound to a single port, expires, and can be revoked — use it when sharing access with someone else ## Authentication If a sandbox has its `public` property set to `true`, preview links are publicly accessible without authentication. Otherwise, authentication is required. The authentication mechanism depends on the preview U”

Source daytona.io

“# Bring Your Own Compute (BYOC) Bring Your Own Compute enables you to run sandbox workloads on your own infrastructure while using Daytona's control plane to manage them. Daytona provides two [built-in regions](https://www.daytona.io/docs/en/regions.md) (**US** and **EU**) for shared compute resources and handling provisioning, maintenance, monitoring, and scaling on your behalf. You can define one or more [custom regions](#custom-regions) and attach your own runner nodes. Custom regions can also include a region-specific sandbox proxy service and snapshot man”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“No advertised first-party capability found across fresh docs index, landing, pricing and relevant capability docs; this is a bounded absence observation, not a vendor assertion.”

Source daytona.io

“Primary current hosted core closed June 2026. Archived historical AGPL code is sibling only; do not score primary hosted pass.”

Source raw.githubusercontent.com