Databricks Sandbox

https://docs.databricks.com/aws/en/compute/serverless/sandbox

Databricks Sandbox runs untrusted code in isolated environments controlled through a REST API, SDK, or CLI. Developers use it to run agent harnesses, execute user-written or AI-generated code, and run background workers.

Pricing model Free during Beta; anticipated hourly running-compute charges plus persistent storage and data transfer
Pricing The headline compute price as the provider states it. Sorting ranks prices stated per vCPU over time, converted to hourly. Other pricing models sort after, unranked. No charge during Beta; pricing is subject to change.
Free while idle Whether a stopped, paused, or sleeping sandbox costs nothing. ✓
Elastic Resources flex with what the sandbox actually uses, and the bill follows: yes when the provider bills on active or observed use, no when capacity is reserved or allocated and billed while it runs. ✕
Memory snapshots Whether RAM state survives a pause and resume, not just disk. –
Wake on request Whether a stopped sandbox wakes automatically on inbound traffic. –
Start / resume Typical time from create or resume to running. Sorting ranks stated times, converted to seconds; claims with no figure sort after, unranked. –
Max runtime The longest a sandbox may run. –
Isolation The isolation technology between sandboxes. microVM isolation
GPUs Whether GPU instances are available for sandboxes. –
Docker Whether Docker containers can run inside the sandbox. –
SDKs Python, Go, Java, JavaScript

✓ yes · ✕ no · – no cited public fact.

Under the anticipated paid model, home-directory storage would remain billable while stopped, until the sandbox is deleted.

Sources

Last verified 2026-10-27. Corrections land through the update log.