Same image, every start

A template is an image pinned by its digest. Every sandbox started from it gets exactly the same bytes, today and next month.

Templates › python-3.12New sandbox · Repin

python-3.12

Every sandbox started from this template gets exactly the same bytes, because the template holds a digest, not a tag.

Activity
lee pinned python:3.12 to sha256:4f1c…a9e2Sep 2
Agents started 312 sandboxes from this template this weekone digest
Upstream pushed a new build under python:3.12Sep 9
Sandscale kept the template on sha256:4f1c…a9e2unchanged
Claude Code started sbx_9a14same digest
lee tested the new build in a sandbox before repinningSep 10
Image
python:3.12
Digest
sha256:4f1c…a9e2
Toolchain
Python 3.12
Packages
pip
Working dir
/workspace
Network
Off by default
This week
312 sandboxes
Pinned by
lee, Sep 2

Every run should start from the same place. A template holds an image digest, not a tag, so the thousandth run next month boots the same bytes as the first run today.

FIG 0.1Pinned once

Sandscale resolves the tag to a digest when you create the template.

FIG 0.2Same bytes every start

Every sandbox from the template boots the same image.

FIG 0.3You choose when it changes

Take a new upstream build by pointing the template at it again.

A tag can move.
A digest can’t.

The same week of agent runs, started two ways. The tag was repointed twice, so the runs on the left got three different images. The template held its digest. Digests are shortened examples.

Started from the tag › python:3.12
DaySandboxImage
Monsbx_31a0sha256:4f1c…a9e2
Wedsbx_33b1sha256:9d07…3c11
Frisbx_35c4sha256:e8a2…7f40
Started from the template › python-3.12
DaySandboxImage
Monsbx_52c0sha256:4f1c…a9e2
Wedsbx_54d3sha256:4f1c…a9e2
Frisbx_56e9sha256:4f1c…a9e2

Four to
start from

Each one carries a language toolchain and its package manager, a /workspace directory, no network by default, and nothing your agent didn’t ask for. The list may change before general availability.

TemplatesDigests shown are examples
TemplateToolchainPackagesDigestStarted this week
python-3.12Python 3.12pipsha256:4f1c…a9e2312
node-22Node.js 22npmsha256:9b2e…11c0208
go-1.25Go 1.25go modulessha256:71d4…5e3a96
rust-1.82Rust 1.82cargosha256:c08a…f71b41

Your image,
pinned the same way

Point a template at your own container image, with your system packages, internal tools and the versions your build expects. Already set a sandbox up by hand? Snapshot it and start new sandboxes from the snapshot instead.

Read the docs →
Create from your own image
01$ sandscale templates create ci --from registry.acme.dev/ci:latest
02resolving registry.acme.dev/ci:latest …
03pinned to sha256:2a7f…09bd
04$ sandscale up --template ci
05sbx_9a20 running ci sha256:2a7f…09bd
A week later
01upstream pushed registry.acme.dev/ci:latest
02new digest sha256:e41c…77aa
03$ sandscale up --template ci
04sbx_9a31 running ci sha256:2a7f…09bd
05template unchanged until you repin it

Start every run
from a known image

Start free with 100 vCPU-hours a month. Upgrade when your agents need more.

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