# Sandboxes overview

Canonical: https://savrn.com/cloud/docs/sandboxes-overview

SAVRN Cloud · Coming soon. Public documentation and a browser simulation are available; connected services are not yet available.

A sandbox needs an explicit contract for resources, files, tools and network access as well as a result. SAVRN Cloud's preview illustrates those records, while this guide distinguishes controlled tasks from the separately qualified capability to execute customer-submitted code.

**SAVRN Cloud · Coming soon · Public preview · Browser-local simulation · No live compute or payments**

## Inspect the execution record

Open [Sandboxes](https://savrn.com/cloud/console/#/sandboxes) and examine the sample resources and supported actions. A sandbox record demonstrates task lifetime, resource settings, outputs and termination in local state. It does not start a virtual machine, container or isolated operating system.

Use the provided demonstration inputs. No arbitrary code should be treated as safely executed merely because it appears inside a sandbox screen. The first intended production workers run SAVRN-controlled tasks; customer-submitted code is a separately qualified capability.

## Read the boundary

A useful execution contract identifies CPU, memory, duration, concurrency, image source, permitted files, credentials and network access. It also defines how artifacts survive termination and how usage is recorded. Compare these requirements with the local record and [Operations](https://savrn.com/cloud/console/#/operations) to identify missing production evidence.

## Before connected services launch

A container alone is not proof of tenant isolation. Test filesystem boundaries, secret exposure, egress restrictions, management-network access, resource exhaustion and cleanup. Ensure cancellation and expiry survive worker failure. Validate image provenance and record immutable versions. GPU support, snapshots and arbitrary images each need their own acceptance evidence. Publish the specific supported boundary rather than using “sandbox” as a blanket security claim. See [first sandbox run](https://savrn.com/cloud/docs/sandboxes-first-run) for a minimal operational walkthrough.