A template is a snapshot of a Linux filesystem (base image, build steps, and optionally a long-running process) that sandboxes boot from. Templates let you pre-install dependencies once and launch identically configured sandboxes in seconds. Every sandbox is created from a template. If you don’t specify one, Superserve defaults toDocumentation Index
Fetch the complete documentation index at: https://docs.superserve.ai/llms.txt
Use this file to discover all available pages before exploring further.
superserve/base.
System templates
Curated by Superserve, available to every team. Identified by thesuperserve/ name prefix.
| Name | Base | Notes |
|---|---|---|
superserve/base | Ubuntu 24.04 | Python 3.12, Node.js 22, git, curl, build-essential. Default when fromTemplate is omitted. |
superserve/python-3.11 | Python 3.11 | Python-focused image with common scientific libraries. |
superserve/node-22 | Node.js 22 | Node-focused image with bun + npm. |
Team templates
Team-owned templates let you bake in team-specific dependencies (e.g.my-python-env with scientific libs pre-installed). They’re created via Template.create() and referenced by name.
Team template names cannot start with superserve/; that prefix is reserved. Names are unique per team among non-deleted templates and are released for reuse the moment a template is deleted.
Names vs UUIDs
When booting a sandbox,Sandbox.create({ fromTemplate }) accepts either the template’s name (my-python-env) or its UUID. Names are more readable; UUIDs are stable across rename/delete.