DocumentationAccount

Your account

One place for your cloud.

Your resources, usage and agent access—together.

Run your work

Isolated Linux environments for your agents and code.

Sandbox

Understand your spend

Track settled usage and keep costs in view.

Usage & billing

Control agent access

Manage separate credentials and revoke access.

API keys

Start with Sandbox

Sandbox is the first Runtime Cloud product.

Open account →

One account owns every Runtime Cloud resource, its agent connections and its prepaid credit. One key, one API, one SDK and one CLI reach every product, with the same resource shape, errors, idempotency, pages and labels. The dashboard shows what you can use today; an SDK method is not a promise that another product is available.

Products

Product What it is Status
Sandboxes Linux microVMs: commands, processes, terminals, files, pause and wake Available
Code interpreter A notebook-style Python or JavaScript session inside a sandbox Available
Network rules Per-sandbox internet, allow and deny lists, and host:port access Available
Images Custom sandbox images from a recipe, a public image or a Dockerfile Available
Volumes Persistent disks attached to sandboxes Available
Snapshots Saved sandboxes, disk and memory, to start and fork from Paused for a fix
Previews An HTTPS address for a port in a sandbox Available
Desktop A Linux desktop in a sandbox, driven by clicks and keys Available

Snapshots and forks are paused while we fix an issue: fork, snapshot and a create naming snapshot answer fork_unavailable. To install dependencies once and start many sandboxes from them, build a custom image and create each sandbox from it.

Start with getting started, then check the sandbox environment and security against your workload. New products join the same namespaces as they launch: runtime.<product> in the SDKs, runtime <product> in the CLI, /v1/<products> in the API and runtime_<products>_* in MCP.

Overview, usage and keys

The overview brings together running resources, monthly spend, available credit and daily spend. API keys have a separate management section. New accounts begin with a focused connection flow until their first sandbox has started.

Spend is settled service usage, not a count of payments or reserved credit. Charges use integer microdollars: one million equals one US dollar. Daily and monthly summaries use UTC. Check the resource's immutable quote and the pricing guide to understand what it is metering. npx withruntime usage and GET /v1/usage give the same figures.

An agent connection has its own identity and revocable credential. Current owner-issued keys cover all Cloud products, including products enabled later, and last until revoked. Browser sign-out does not revoke them. See security and access before connecting an agent.

Labels and names

Sandboxes, images, volumes and snapshots take a name and up to 32 labels, and their lists filter by them: npx withruntime sandbox ls --label team=search, GET /v1/sandboxes?label=team:search. Use them for tenants, jobs and cost attribution.

Was this page right?