Built so a bad run stays in its box
Its own kernel for every run, secrets on a timer, prompts checked before they leave, and a record of every action you can verify.
Security overview
Sign-ins, directory changes, secrets, prompts and policy decisions from the last hour, all in one hash-chained log.
Okta over SAML09:02jo@acme.dev from the directory, sessions ended09:14curl -s https://get.example.sh | sh in sbx_9a14blockedDB_TEST_URL ended with lease_7f2c10:32github.create_pull_request10:411,284,113 entries11:00- Sign-in
- Okta, SAML
- Directory
- SCIM, in sync
- Members
- 48 in 4 roles
- Kill switch
- Ready, stops every agent
- Vault
- 12 secrets, 3 leased
- Audit chain
- Verified
- Hosted in
- US East and EU
- Plan
- Enterprise
Agents run code nobody has read yet. Sandscale gives every run its own microVM, keeps secrets out of it, checks what the agent sends, and writes every action to a log you can verify.
A Firecracker microVM per run, not a container on a shared host.
Vault leases end with the job. Keys never sit in prompts, repos or logs.
Each audit entry is chained to the one before it, so an edit shows.
Its own kernel.
No way out it wasn’t given.
Each sandbox is a Firecracker microVM that boots its own kernel. It shares nothing with your machines or with other customers’ runs, and its network is off until your allowlist opens it.
See sandboxes →Secrets go in on a timer.
Leaks don’t go out.
Keys and tokens live in Vault and reach a run in memory, for as long as the run lasts. DLP on prompts and tool calls (Enterprise) scans prompts and MCP tool calls before they go anywhere, so a credential pasted into a prompt never reaches the model.
Your directory
decides who gets in
SAML or OpenID Connect single sign-on with Entra ID, Okta, Google Workspace or any standard provider, on Team. On Enterprise, SCIM adds and removes members as your directory changes, with verified domains and custom roles. Passkeys and multi-factor sign-in work on every plan.
See integrations →Proof for your assessor,
data where you put it
Every entry for a period, its hash chain checked, packed into one file you hand to your assessor. It is evidence toward SOC 2, ISO 27001 and the EU AI Act; certification stays with you and your assessor.
- Period
- July 1 to September 30
- Entries
- 1,284,113
- Hash chain
- Checked, no gaps
- Covers
- sign-ins, runs, policy, secrets, approvals
- File
- sandscale-evidence-2026-q3.zip
- Evidence toward
- SOC 2, ISO 27001, EU AI Act
- Hosted
- US East (N. Virginia) or EU (Frankfurt)
- Your own cloud
- AWS on Enterprise. Azure and Google Cloud coming soon
- Encryption keys
- Yours, on Enterprise
- Audit retention
- By plan
What each plan
includes
Isolation and a basic audit log are the same on every plan. Team adds the controls a company needs; Enterprise adds SCIM, DLP, your own keys, your own cloud and dedicated capacity.
See pricing →Found something?
Tell us first.
If you think you’ve found a security issue in Sandscale, email us before you share it anywhere else. Our disclosure page says what to include and how we handle reports. Bring your security questionnaire too; we’ll go through it with you, control by control.
Vulnerability disclosure →Bring your security
questionnaire
We’ll go through it with you, control by control.