Give your code a computer it can actually use

Managed sandboxes for real execution

Run code with real terminals, files, services, and browsers, driven from the app or automated through the CLI, API, and MCP. Use Borealis-managed capacity or qualifying private host pools, then stop, snapshot, and resume without losing work.

  • Start, stop, resume, and inspect sandboxes
  • Persistent snapshots and exact workspace transfer
  • Managed capacity with plan-controlled private host pools
  • Metered vCPU and memory only while sandboxes run
Start FreeSign In

Sandbox

sandbox-01

Running

Compute

4 vCPU · 8 GiB

Checkpoint

2 min ago

terminal
$ pnpm test ✓ 48 tests passed $ _

Sandboxes you can run, pause, and automate

Real terminals and services while the work runs, snapshots when it pauses, and an API, CLI, and MCP server to drive all of it.

Dedicated Environments

Give each workload a dedicated sandbox with explicit CPU, memory, networking, and lifecycle boundaries.

Persistent Snapshots

Checkpoint a sandbox, stop it when idle, and resume later without rebuilding the working environment.

Managed or Private Capacity

Run on Borealis-managed hosts or enrol private host pools when your plan and security requirements call for them.

Terminals, Logs, and Ports

Execute commands, stream logs, expose services, and inspect running sandboxes through one consistent control plane.

Usage-Based Billing

Track allocated vCPU and memory while sandboxes run. Stopped and suspended sandboxes do not incur compute charges.

API, CLI, and MCP

Create and control sandboxes from the web app, automate them with the versioned API and CLI, or let an AI agent drive them through the MCP server.

From image to working environment

Create, run, preserve, and automate a sandbox in five clear steps.

Borealis

Define the Sandbox

image: node:22
cpu: 4
memory: 8Gi
ports: [3000]