Daytona
Daytona is open-source, secure, and elastic infrastructure for running AI-generated code. Daytona sandboxes spin up in under 90 milliseconds and provide isolated Linux, Windows, and macOS environments where autonomous agents and developer workflows can execute untrusted code, perform file system and Git operations, run language servers, drive virtual desktops, and persist state via snapshots and volumes. The platform exposes a control-plane REST API (sandboxes, snapshots, volumes, organizations, runners, webhooks) and an in-sandbox Toolbox API (file system, Git, LSP, process execution, PTY, computer use, interpreter), with official SDKs for TypeScript, Python, Ruby, Go, and Java, plus a Go CLI and Homebrew/Windows installers.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Daytona the way a machine reads it — 124 machine-readable artifacts across 28 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Daytona scores 74.1/100 (exemplar), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Daytona
Each block below is one kind of artifact we hold for Daytona. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 28
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Daytona admin API
The admin API from Daytona — 15 operation(s) for admin.
Daytona api-keys API
The api-keys API from Daytona — 4 operation(s) for api-keys.
Daytona audit API
The audit API from Daytona — 1 operation(s) for audit.
Daytona computer-use API
The computer-use API from Daytona — 32 operation(s) for computer-use.
Daytona config API
The config API from Daytona — 1 operation(s) for config.
Daytona docker-registry API
The docker-registry API from Daytona — 3 operation(s) for docker-registry.
Daytona file-system API
The file-system API from Daytona — 12 operation(s) for file-system.
Daytona git API
The git API from Daytona — 9 operation(s) for git.
Daytona Health API
The Health API from Daytona — 2 operation(s) for health.
Daytona info API
The info API from Daytona — 3 operation(s) for info.
Daytona interpreter API
The interpreter API from Daytona — 3 operation(s) for interpreter.
Daytona jobs API
The jobs API from Daytona — 4 operation(s) for jobs.
Daytona lsp API
The lsp API from Daytona — 7 operation(s) for lsp.
Daytona object-storage API
The object-storage API from Daytona — 1 operation(s) for object-storage.
Daytona organizations API
The organizations API from Daytona — 30 operation(s) for organizations.
Daytona port API
The port API from Daytona — 2 operation(s) for port.
Daytona preview API
The preview API from Daytona — 4 operation(s) for preview.
Daytona process API
The process API from Daytona — 14 operation(s) for process.
Daytona regions API
The regions API from Daytona — 1 operation(s) for regions.
Daytona runners API
The runners API from Daytona — 9 operation(s) for runners.
Daytona sandbox API
The sandbox API from Daytona — 37 operation(s) for sandbox.
Daytona server API
The server API from Daytona — 1 operation(s) for server.
Daytona snapshots API
The snapshots API from Daytona — 6 operation(s) for snapshots.
Daytona toolbox API
The toolbox API from Daytona — 61 operation(s) for toolbox.
Daytona users API
The users API from Daytona — 5 operation(s) for users.
Daytona volumes API
The volumes API from Daytona — 3 operation(s) for volumes.
Daytona webhooks API
The webhooks API from Daytona — 3 operation(s) for webhooks.
Daytona workspace API
The workspace API from Daytona — 12 operation(s) for workspace.
Scroll within the panel for all 28 ·
Postman Collections 12
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Daytona Admin API
POSTMANDaytona Api Keys API
POSTMANDaytona Health API
POSTMANDaytona Organizations API
POSTMANDaytona Preview API
POSTMANDaytona Sandbox API
POSTMANDaytona Sandbox Toolbox API
POSTMANDaytona Snapshots API
POSTMANDaytona Toolbox API
POSTMANDaytona Users API
POSTMANDaytona Volumes API
POSTMANDaytona Webhooks API
POSTMANScroll within the panel for all 12 ·
Open Collections 11
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Daytona Admin API
OPEN COLLECTIONDaytona Api Keys API
OPEN COLLECTIONDaytona Health API
OPEN COLLECTIONDaytona Organizations API
OPEN COLLECTIONDaytona Sandbox API
OPEN COLLECTIONDaytona Sandbox Toolbox API
OPEN COLLECTIONDaytona Snapshots API
OPEN COLLECTIONDaytona Toolbox API
OPEN COLLECTIONDaytona Users API
OPEN COLLECTIONDaytona Volumes API
OPEN COLLECTIONDaytona Webhooks API
OPEN COLLECTIONScroll within the panel for all 11 ·
Arazzo Workflows 8
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Daytona Build and Activate a Snapshot
Register a snapshot from a container image, poll until it builds, and activate it if it lands inactive.
ARAZZODaytona Capture a Sandbox as a Snapshot
Snapshot a live sandbox into a reusable image and wait for the sandbox to return to running.
ARAZZODaytona Fork a Sandbox
Fork an existing sandbox into a new independent copy and wait until the fork is running.
ARAZZODaytona From Container Image to Running Sandbox
Build a snapshot from an image, wait for it to build, then launch and run a sandbox from it.
ARAZZODaytona Provision a Sandbox
Create a sandbox from a snapshot, poll until it reaches the started state, then read its details.
ARAZZODaytona Provision a Volume and Attach It to a New Sandbox
Create a persistent volume, wait until it is ready, then launch a sandbox with the volume mounted.
ARAZZODaytona Restore an Archived Sandbox
Start an archived or stopped sandbox and wait until it is running again.
ARAZZODaytona Stop and Archive a Sandbox
Stop a running sandbox, wait until it is fully stopped, then archive it to cold storage.
ARAZZOScroll within the panel for all 8 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Daytona Io Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Daytona Io Finops
FINOPSFeatures 10
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Sub-90ms cold start
Sandboxes boot in under 90 milliseconds, enabling per-request isolation for agents at scale.
Massive parallelism
Spin up thousands of concurrent sandboxes for parallel agent runs, evaluation harnesses, and batch code execution.
Snapshots and volumes
Persist file system, process, and environment state via snapshots, and share data across sandboxes via volumes.
Computer Use desktops
Programmatically drive Linux, Windows, and macOS GUI desktops via a built-in computer-use API for agent control.
Multi-language runtimes
Native support for Python, TypeScript, Ruby, Go, and Java with built-in package management.
Built-in LSP and Git
Language Server Protocol bridging and Git operations are first-class agent tools, not bolted-on shell calls.
Open-source core
The Daytona platform is AGPL-3.0 open source and self-hostable on Kubernetes via official Helm charts.
Customer-managed compute
Run the Daytona control plane against your own compute pools for data-residency and cost control.
SSH and VS Code Browser
Humans can drop into any sandbox via SSH, web terminal, VNC, or VS Code Browser for debugging.
Webhooks and OpenTelemetry
Subscribe to sandbox lifecycle events and emit OpenTelemetry traces for observability.
Scroll within the panel for all 10 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Daytona Io Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Daytona API Rules
SPECTRALDaytona API Rules
SPECTRALJSON Schema 7
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ApiKeyResponse
JSON SCHEMAOrganization
JSON SCHEMASandbox
JSON SCHEMASnapshotDto
JSON SCHEMAUser
JSON SCHEMAVolumeDto
JSON SCHEMAWebhookEvent
JSON SCHEMAScroll within the panel for all 7 ·
JSON Structure 7
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Daytona Api Key Structure
JSON STRUCTUREDaytona Organization Structure
JSON STRUCTUREDaytona Sandbox Structure
JSON STRUCTUREDaytona Snapshot Structure
JSON STRUCTUREDaytona User Structure
JSON STRUCTUREDaytona Volume Structure
JSON STRUCTUREDaytona Webhook Structure
JSON STRUCTUREScroll within the panel for all 7 ·
Examples 7
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 7 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 7
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
AI coding agents
Give every agent its own isolated computer to run, test, and iterate on generated code safely.
Code interpreter for LLM apps
Back chatbot code-execution features (Python interpreter, data analysis, plotting) with disposable sandboxes.
Computer-use agents
Drive headless and headed Linux/Windows/macOS desktops for browser automation and GUI-driven workflows.
Evaluation harnesses
Run SWE-bench-style benchmarks and agent evaluations in massively parallel sandboxes with reproducible state.
CI for AI-generated code
Execute untrusted PRs from autonomous agents in isolated environments without risking host infrastructure.
Hosted developer environments
Provide cloud dev environments for engineers with persistent volumes, snapshots, and SSH/VS Code access.
Sandboxed data analysis
Run user-uploaded notebooks and scripts safely with built-in Python and TypeScript interpreters.
Scroll within the panel for all 7 ·
Integrations 13
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
LangChain
Daytona is integrated as a code execution tool in the LangChain ecosystem.
Anthropic Claude Managed Agents
Daytona is supported as a sandbox host for Anthropic Claude Managed Agents.
Google ADK
Daytona plugin for Google's Agent Development Kit enables ADK agents to run code in Daytona sandboxes.
Inngest AgentKit
Coding agent reference powered by Daytona using Inngest AgentKit.
VibeKit
Run Codex, Gemini CLI, and Claude Code in Daytona sandboxes via VibeKit.
Stripe Projects
Daytona sandboxes are available through Stripe Projects.
OpenHands
OpenHands open-source agent runtime uses Daytona for sandboxed code execution.
SWE-ReX
Sandboxed code execution backend for SWE-agent powered in part by Daytona.
Kubernetes
Self-host the Daytona control plane on Kubernetes via official Helm charts.
Terraform
Provision Daytona infrastructure using official Terraform modules.
MCP
Daytona exposes an MCP server so MCP-compatible agents and IDEs can invoke sandbox tools natively.
VS Code
Connect to a running sandbox from VS Code via the VS Code Browser, SSH, or official extension.
JetBrains
Connect to a running sandbox from JetBrains IDEs via the official JetBrains plugin.
Scroll within the panel for all 13 ·
Solutions 4
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Daytona Cloud
Fully managed sandbox infrastructure at app.daytona.io with pay-as-you-go pricing and $200 free credit.
Customer-Managed Compute
Run Daytona's managed control plane against your own VPC/Kubernetes compute for residency and cost control.
Self-Hosted Open Source
Deploy the full Daytona platform on your own Kubernetes via Helm for fully air-gapped deployments.
Startups Program
Up to $50k in free Daytona compute credits for qualifying startups building agent infrastructure.
Resources
Every other property we hold for Daytona — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 6
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 11
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 11 ·
Build 10
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 10 ·
Access & Security 6
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 5
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/daytona-io · machine-readable index on apis.io