SANDBOXES

Run Code in a
Real Machine

Run Code in a
Real Machine

Isolated compute for code, tools, and long-running tasks. Snapshot, fork, and resume in seconds.

Isolated compute for code, tools, and long-running tasks. Snapshot, fork, and resume in seconds.

Install
npm install @solarisdk/sandbox
import { SandboxClient } from "@solarisdk/sandbox"
 
const sandboxes = new SandboxClient({
apiKey: process.env.SOLARI_API_KEY!,
baseUrl: "https://api.getsolari.com",
})
 
const sbx = await sandboxes.create({
template: "base",
})
 
const res = await sbx.commands.run(
"echo",
{
args: ["hello", "world"],
}
)
 
console.log(
res.exitCode,
res.stdout
)
 
await sbx.kill()
One protocol, many clients. Every SDK uses the same REST + control-WebSocket contract, so sandboxes can be created in one language and controlled from another.

Benchmarks

See how Solari stacks up

Full Sandbox Lifecycle
Solari
8.2s
E2B
10.8s
Modal
11.9s
Daytona
13.6s
CodeSandbox
24.8s

Measured on the open-source Nibzard benchmark, Solari delivers the fastest end-to-end sandbox lifecycle.

Measured on the open-source Nibzard benchmark, Solari delivers the fastest end-to-end sandbox lifecycle.

8.2s

Full FFT lifecycle

Fastest sandbox in the field

8.2s

Full FFT lifecycle

Fastest sandbox in the field

1.3x

Faster than the next best

8.2s vs E2B 10.8s

Top 2

On every phase

The only provider never slower than second

Top 2

On every phase

The only provider never slower than second

Solari
E2B
Modal
Daytona
CodeSandbox
Create
869ms
541ms
2,070ms
2,202ms
1,321ms
Run code
7,019ms
9,868ms
6,607ms
8,531ms
17,237ms
Clean up
269ms
401ms
3,235ms
141ms
6,234ms
Total
8,158ms
10,810ms
11,912ms
13,589ms
24,792ms
Metric: the open-source nibzard test_fft_performance lifecycle, same harness for every provider. Competitor figures are the benchmark's own published results. Solari run on Solari infrastructure at 1 vCPU / 8 GB (the FFT allocates about 4 GB, so every provider runs it sized to fit); the FFT is single threaded, so this reflects single-core speed. Solari's client is a region away from its gateway, so create and clean up are measured conservatively.

BUILT FOR AGENTS

Fast. Scalable. Stateful. Built for AI agents

Lightning-Fast Infrastructure

Start executing in milliseconds

Launch a ready sandbox in under 90 ms, with no machine boot delay before the first command.

Isolated Runtime Protection

Protect your infrastructure

Run model-generated code inside a dedicated microVM with its own kernel and hardware-backed isolation.

Massive Parallel Execution

Scale agent workflows instantly

Fork one prepared environment into independent workers for parallel tasks, retries, and evaluations.

Capabilities

Everything your agent needs

Stateful execution

Let agents run for hours, pause when idle, and resume exactly where they left off without losing context or rebuilding the environment.

sandbox-session
AGENT_19HT50
Training pipeline
RUNNING
AGENT_21H41C
Data processing
RUNNING
agent-runtime
$ python train.py
[10:21:14] Starting agent...
[10:21:15] Processing batch 42/100
[10:21:16] Checkpoint saved
RUNNINGProcessing task
PAUSEDState saved
RESUMINGContinuing task
sandbox-session
AGENT_19HT50
Training pipeline
RUNNING
AGENT_21H41C
Data processing
RUNNING
agent-runtime
$ python train.py
[10:21:14] Starting agent...
[10:21:15] Processing batch 42/100
[10:21:16] Checkpoint saved
RUNNINGProcessing task
PAUSEDState saved
RESUMINGContinuing task

Rich outputs

Return structured JSON, charts, images, files, logs, and execution metadata, not just plain text.

Persistent filesystem

Clone repositories, process documents, generate artifacts, and move large files through a persistent filesystem.

Scale on demand

Scale from 1 to 16 vCPUs without rebuilding the environment or losing state.

Bring your own image

Start every sandbox with your exact runtime, dependencies, tools, and system configuration already installed.

WORKLOAD ISOLATION

Keep untrusted code isolated from your infrastructure

SolariMICROVM
E2BMICROVM
ModalGVISOR
DaytonaSYSBOX
Isolation technology
Cloud Hypervisor microVM
Firecracker microVM
gVisor sandbox
Sysbox container
Dedicated kernel per session
Yes
Yes
Userspace kernel
No — shared kernel
Untrusted code boundary
Hardware virtualization (KVM)
Hardware virtualization (KVM)
Syscall filtering
Shared host kernel
Isolation model per each vendor's published architecture. microVM (Solari, E2B) is the strongest tier; gVisor filters syscalls in userspace; Sysbox hardens a container but shares the host kernel.

Run model-generated and untrusted code without putting the rest of your infrastructure at risk. Each Solari sandbox gets its own microVM and dedicated kernel, creating a clear boundary between workloads.

FAQ

Before you deploy. Everything you need to know

What is Solari?

What's the difference between a browser, a sandbox, and a VM?

Can Solari run in our VPC?

Can agents pause work and resume it later?

What languages and frameworks does Solari support?

How do agents stay undetected in Solari browsers?

How does Solari run AI-generated code safely?

Can I bring my own environment?

FAQ

Before you deploy. Everything you need to know

What is Solari?

What's the difference between a browser, a sandbox, and a VM?

Can Solari run in our VPC?

Can agents pause work and resume it later?

What languages and frameworks does Solari support?

How do agents stay undetected in Solari browsers?

How does Solari run AI-generated code safely?

Can I bring my own environment?

FAQ

Before you deploy. Everything you need to know

What is Solari?

What's the difference between a browser, a sandbox, and a VM?

Can Solari run in our VPC?

Can agents pause work and resume it later?

What languages and frameworks does Solari support?

How do agents stay undetected in Solari browsers?

How does Solari run AI-generated code safely?

Can I bring my own environment?

The Fastest Agent
Infrastructure

Get started today on Solari