Daytona-compatible API

Sandboxer has a second API that speaks Daytona's. Code that uses the Daytona TypeScript or Python SDK for sandboxes, commands, files and previews runs on Sandboxer when you change two environment variables. See what's covered below. Your sandboxes are Sandboxer microVMs, billed and limited exactly like the ones you create with sbx or the Sandboxer API.

Moving a project over step by step? The Daytona migration guide walks through it. This page is the reference.

Switch#

1. Create an API key in the dashboard, or with sbx api-key create daytona --preset ci (create, run, files, previews, and delete what it created).
2. Set two variables where your code runs:

export DAYTONA_API_URL=https://sandboxer.com/daytona/api
export DAYTONA_API_KEY=sbx_live_…   # a Sandboxer API key

3. Run your code unchanged:

import { Daytona } from "@daytonaio/sdk";

const daytona = new Daytona(); // reads DAYTONA_API_URL and DAYTONA_API_KEY
const sandbox = await daytona.create();
const r = await sandbox.process.executeCommand("echo hello");
console.log(r.result); // hello
const link = await sandbox.getPreviewLink(3000); // https://…-3000.box.sandboxer.com, plus a token
await sandbox.stop();
await sandbox.delete();

from daytona import Daytona

daytona = Daytona()  # reads DAYTONA_API_URL and DAYTONA_API_KEY
sandbox = daytona.create()
print(sandbox.process.exec("echo hello").result)  # hello
sandbox.fs.upload_file(b"hi", "/tmp/hi.txt")
sandbox.stop()
sandbox.delete()

We test the official TypeScript and Python SDKs (@daytonaio/sdk and daytona 0.225.0) against this API end to end: create, run a command, write and read a file, open a preview URL with its token, stop and delete. The Go, Ruby and Java SDKs call the same API, but we haven't tested them.

What's covered#

Not covered yet#

These return an error with the code not_supported, never a silent no-op. A field counts as used when it's set to anything but its default. Real-time events are refused when the connection opens, and the SDKs fall back to polling.

• Custom images, Daytona snapshots and declarative builds. Every sandbox starts from Sandboxer's Ubuntu image. For your own base, use named snapshots through sbx or the Sandboxer API.
• Volumes, GPUs, spot instances.
• Daytona's pause and fork. Here, a plain stop already keeps memory.
• Network controls: networkBlockAll, allow-lists, outbound proxy.
• Git, LSP, computer use, PTY and the code interpreter in the toolbox.
• Following command logs live (follow). Fetch them instead.
• Sorting the list, and filtering it by state or snapshot.

How it differs#

• Every sandbox is a microVM. Each sandbox is a Linux VM with its own kernel, root, systemd, Docker and /dev/kvm. There are no container sandboxes. kvm is always on.
• Stop keeps memory. A stop snapshots memory and disk, and a start resumes with running processes intact. A stopped sandbox is archived at once, so autoArchiveInterval is accepted but has no effect.
• Auto-stop works as in Daytona. autoStopInterval (minutes, default 15) stops the sandbox that many minutes after it starts or after its last toolbox call, whichever is later. A command keeps it up until the command's timeout plus a minute, so a command with no timeout holds it for about 11 minutes. A stopped sandbox isn't billed for compute. 0 means it never stops by itself, so stop or delete it when you're done. On the free trial the interval must be 8 hours or less, and 0 is refused with trial_auto_stop_required. On any plan it's at most 30 days. Sandboxer's own idle pause is off for sandboxes created through this API.
• Previews are per port. Each port has its own token, not one per sandbox.
• Errors use Daytona's shape (statusCode, message, error) with Sandboxer's machine code in code, so the SDKs raise their usual exceptions.
• The same account. Billing, limits, API key scopes and organizations are shared with the rest of Sandboxer. A sandbox created through either API shows up in both, in the dashboard and in sbx ls.

Endpoints: the control API is at https://sandboxer.com/daytona/api and the toolbox at https://sandboxer.com/daytona/toolbox. The SDKs find the toolbox themselves.