Straight answers about Sandscale

What it runs, how it’s isolated, what it costs and where it runs. If your question isn’t here, email us.

The product

What is Sandscale?

Isolated compute for AI agents. Sandscale runs sandboxes, workspaces, build hosts and lab hosts, on our cloud or your own, so the code your agents write runs away from your systems.

What's the difference between a sandbox and a workspace?

A sandbox is a Firecracker microVM for a run: start it, execute commands with live output, move files in and out, snapshot, pause and resume it, and throw it away.

A workspace is a persistent cloud computer: its disk stays, you get terminals in the browser and SSH, snapshots and templates, and it can start and stop on a schedule and sleep when idle.

What is a build host?

A clean machine you lease from a pool for a set time. You sync your source tree, run over SSH with a certificate that expires with the lease, get short-lived secrets from Vault for that lease, keep artifacts and caches, and the machine is wiped when you release it. Leases run up to 4 hours on Pro and 12 hours on Team.

What is a lab host?

Your own Linux or macOS machine running the Sandscale lab host agent. It lists the USB devices attached to it, like security keys, TPMs, debug probes and boards, and lets a run claim them exclusively. Device policy and approvals decide who can claim what, the connection uses mTLS with a heartbeat, and devices are released when the run ends. Lab hosts are on Team and Enterprise.

Can lab hosts run Windows?

Not yet. Lab hosts run on Linux and macOS today.

Which agents can I use?

Coding agents like Claude Code, Codex and Gemini CLI run inside a workspace, and agents can use sandboxes over MCP. We provide the machine, not the model: you bring the agent and its model access.

Which templates are there?

Templates include python-3.12, node-22, go-1.25 and rust-1.82, each pinned by digest so a run starts from exactly the same image every time. The list may change before general availability.

Isolation and security

How is a sandbox isolated?

Each sandbox is its own Firecracker microVM with its own kernel, not a container sharing the host's kernel. It has no network by default.

Can a sandbox reach the internet?

Not by default. Sandboxes start with the network off. On Pro and up you choose what an agent may reach with an egress allowlist; Free stays off.

How do I get into a box or reach a port?

Over SSH with a short-lived certificate. Ports are reached through an authenticated tunnel only: there are no public URLs.

How are secrets handled?

Secrets live in Vault, out of prompts, repositories and logs. Build hosts get short-lived secrets for each lease. Vault is on Pro and above.

Is there an audit log?

Yes. Every action is recorded in a hash-chained audit log. A basic audit log comes with every plan; exporting it as evidence comes with Team and Enterprise.

Do you have DLP, SSO and SCIM?

SSO with SAML or OpenID Connect (Entra ID, Okta, Google Workspace and others), roles and groups come with Team. SCIM, verified domains, custom roles, and DLP on prompts and tool calls, come with Enterprise. Passkeys and multi-factor sign-in work on every plan.

Is Sandscale SOC 2 or ISO 27001 certified?

We don’t claim any certification. Team and Enterprise can export the audit log as evidence for your own assessments.

Can I use my own encryption keys?

Yes, on Enterprise.

Speed and size

How fast does a sandbox start?

In seconds. Warm pools keep sandboxes from each template booted, so your agent is handed one that is already running.

What do pause and resume keep?

Memory and files, on every plan. A resumed sandbox carries on where it stopped. Snapshots, which save a sandbox to start new ones from, come with Pro and up.

How big can a box be?

Free: up to 2 vCPU. Pro: up to 8 vCPU. Team: up to 16 vCPU. Enterprise: up to 64 vCPU on request.

Plans and billing

Is there a free plan?

Yes. Free is $0 with 100 vCPU-hours a month and 2 sandboxes at once, with the network off. It needs a verified email address.

What does Pro include?

$20 a month billed annually, or $25 billed monthly. 750 vCPU-hours a month, 20 at once, up to 8 vCPU, network access with an allowlist, workspaces, build host leases up to 4 hours, Vault and 50 GB of object storage. It needs a payment method.

What does Team include?

$40 per member a month billed annually, or $48 billed monthly, from 2 members. 1,000 vCPU-hours per member, pooled, 100 at once, up to 16 vCPU, build host leases up to 12 hours, lab hosts, SSO, roles and groups, approvals and policies, projects and audit log export.

What about more than 200 people?

Large organisations use Enterprise: SCIM, your own keys, your own cloud, dedicated capacity, up to 64 vCPU on request and support terms in your agreement. Email sales.

What if I need more hours?

On paid plans you can turn on usage beyond your included hours, or keep it off. We will publish the rate before sign-up opens.

What is a vCPU-hour?

One vCPU for one hour. A 2 vCPU box running for 30 minutes uses 1 vCPU-hour.

Regions and clouds

Where does hosted compute run?

In the US (N. Virginia) and Europe (Frankfurt). One account works in both: pick the region for each sandbox or workspace, with one dashboard, one bill and one balance of hours. See regions.

Can I run on my own cloud?

Yes, on Enterprise. AWS is available; Azure and Google Cloud are coming soon.

Getting started

Can I use the API and CLI today?

Not yet: Sandscale isn’t open to the public. At launch the console is at cloud.sandscale.dev, the API at api.sandscale.dev, and the sandscale CLI installs from sandscale.dev/install, Homebrew or npm. Ask for early access.

How do I get help?

Free has the docs and the community. Paid plans get email support at support@sandscale.dev; Enterprise support follows your agreement.

How do I report a vulnerability?

Still have
a question?

Email support@sandscale.dev and a person on the team will answer.

A Firecracker microVM for every runNo network by defaultPause and resume with state keptVault keeps secrets out of promptsSSO, roles and audit logBring your own cloudWorks over MCP and the CLI