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.
python-3.12
Every sandbox started from this template gets exactly the same bytes, because the template holds a digest, not a tag.
python:3.12 to sha256:4f1c…a9e2Sep 2312 sandboxes from this template this weekone digestpython:3.12Sep 9sha256:4f1c…a9e2unchangedsbx_9a14same digest- 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.
Sandscale resolves the tag to a digest when you create the template.
Every sandbox from the template boots the same image.
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.
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.
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 →Start every run
from a known image
Start free with 100 vCPU-hours a month. Upgrade when your agents need more.