Templates

When to use a template#

• You spin up the same workspace shape often. Save it once, save 90 seconds every time.
• You want every candidate in a hiring loop to start from the same machine, with no drift between runs.
• You want to onboard a new engineer with one click instead of a README full of setup steps.

Create a template#

1. Tune a real workspace
   Spin up a workspace, get the machines + stacks exactly the way you want, and verify it boots cleanly from a cold start.
2. Open Save as template
   Open the kebab menu on the workspace card and pick Save as template. The option is visible on every non-archived workspace.
3. Name and describe
   Give the template a clear name (e.g. node-postgres-redis) and a one-line description so others know when to use it.
4. Save
   The template appears in the template gallery on step 1 of the Create New Workspace wizard.

Edit a template#

Templates are immutable snapshots - editing one would retroactively change every workspace someone might create from it. Instead: spin up a workspace from the existing template, adjust the machines or stacks, and use Save as template to capture the new shape under a new name (e.g. node-postgres-redis-v2).

Share a template across the team#

Templates are scoped to an account. Every member of the account sees every template in the gallery on step 1 of the Create New Workspace wizard. There is no per-template ACL inside an account - a template is either visible to everyone or it does not exist.