Three inboxes, read by the team

Pick the inbox that fits your question and write to us like you’d write to a colleague.

Pick the inbox
that fits

Email is the way in for now: there’s no contact form and no chatbot. Writing to the right inbox gets your email to the people who can act on it.

Sales and Enterprise

Plans, Team and Enterprise, your own cloud, lab hosts, and early access before sign-up opens.

sales@sandscale.dev
Tell us what your agents do, roughly how many run at once, and where you need them to run.
Support

Your account, billing, and anything a sandbox, workspace or build host did that you didn’t expect.

support@sandscale.dev
Send the box id (sbx_…), the template, what you ran, and what happened instead.
Security

Vulnerabilities in Sandscale, including anything that weakens the isolation between boxes.

security@sandscale.dev
Steps to reproduce and what you could reach. Please don’t test against other people’s boxes.

Want the API and CLI
before launch?

They open to everyone at launch. Until then, five answers make a good early access request, and are enough for us to pick the right plan and box sizes with you.

01What your agents do

For example, coding agents in CI with one box per run.

02What runs them, and how many at once

Claude Code, Codex, your own framework; a rough count is fine.

03Where they should run, and any hardware

The US, Europe or your own AWS account; any devices in the loop.

Or skip the email
and look at the plans

Start free with 100 vCPU-hours a month.

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