Skip to main content
Prime Sandboxes are disposable, hardware-isolated microVMs for AI agents, benchmarking, agentic RL, and quick experiments. Each one boots an OCI/Docker image as its root filesystem, so it runs anything a real VM can: Docker, systemd, background services, kernel-dependent workloads. Thousands can start concurrently in seconds. Sandbox Dashboard

​
Features

Create & manage

Resources, start commands, lifetime and idle timeouts, labels, bulk delete

Run commands & SSH

One-off commands, long-running background jobs, interactive SSH

Files

Upload, download, and read files

Env vars & secrets

Inject config and encrypted credentials that never appear in API responses

Network isolation

Allow or deny outbound traffic by domain or CIDR, live-updatable

Header secret injection

Add secrets to HTTPS request headers outside the sandbox

Private networks

Let sandboxes reach each other at <sandbox-id>.sandbox.internal, with per-port rules

Public ports

Serve an HTTP app running in a sandbox at a public HTTPS URL

Checkpoints & forking

Save a sandbox’s filesystem, restore it later, or fork it

Pause & resume

Stop compute and resume with memory and processes intact

Volumes

Persistent named storage you attach to a sandbox and publish to share

Custom images

Build images in the cloud or copy them from public registries

Tunnels

Expose a local or in-sandbox service at a public HTTPS URL

Python SDK

Sync and async clients, fleets, typed errors

GPUs (coming soon)

GPU sandboxes need an explicit grant; --gpu-count above 0 errors until then

​
Quickstart

Log in first with prime login, using an API key with sandbox permissions.
Python snippets on the feature pages assume this client; see the Python SDK for the async client. Runnable demos live in prime/examples.

​
Pricing

Sandboxes are billed while running. For our new launch, these rates are valid through December 22, 2026:
  • CPU: $0.02 per vCPU per hour
  • Memory: $0.0125 per GiB per hour
  • Disk: $0.0002 per GiB per hour
Example: 1 vCPU, 2 GiB RAM, 5 GiB disk → $0.046/hour. A paused sandbox is billed for its disk only. VM images and filesystem checkpoints are billed for storage separately:
  • Storage: $0.10 per GiB per month, billed hourly while the image or checkpoint exists
  • Upload: a one-time charge equal to one day of storage, applied when an image build completes or a checkpoint becomes DURABLE
Track usage and billing in the Prime Billing dashboard.

​
Limits

​
Per-sandbox

CPU is allocated in whole vCPUs; fractional values are truncated, and anything below 1 becomes 1. Set the timeout to any negative value for no lifetime deadline. A finite timeout must be at least as long as the idle timeout.

​
Per-account

Account limits apply across all running sandboxes. If you need higher limits, contact support.