Templates
Official maintained base environments, how they are versioned, and the patch cadence and provenance recorded for each build.
What templates are
A template is a named base environment a session starts from. There are two kinds:
- Official templates are maintained by inis.run. You get them in every project, you cannot delete them, and each one is rebuilt on a schedule to pick up upstream security patches.
- Your templates are saved from your own sessions. Configure a session, save it, and stamp new sessions from it.
Create a session from a template by name:
inis run --template python -- python3 script.pyThe official set
The official set is grouped into two lines:
- Language runtimes track an upstream release —
python,node,go, and the defaultbase(Python and TypeScript ready). These follow the upstream image and are rebuilt weekly. - Use-case images are composed environments for a task built from a maintained recipe — for example
data-science(pandas, numpy, scikit-learn, Jupyter) orheadless-browser(Playwright with Chromium). These are rebuilt at least monthly.
The set grows over time, so the live list is the source of truth — not this page. See what is available, with the version and built date of each:
inis templates lsNAME KIND VERSION BUILT DESCRIPTION
base official 2026.07.09 2026-07-09 Default environment — Python and TypeScript ready.
python official 2026.07.10 2026-07-10 Python 3.12 with pip, venv, and the common data libraries.
node official 2026.07.10 2026-07-10 Node.js 22 LTS with npm and pnpm.
data-science official 2026.07.02 2026-07-02 Python + pandas, numpy, scikit-learn, and Jupyter.The same list, with full provenance, is on the Templates page in the console.
Versioning
Every rebuild of an official template is published as a new immutable version — for example python@2026.07.10. A (name, version) pair, once published, never changes. Two ways to reference one:
- The bare name (
python) resolves to the currently promoted version. When a rebuild is promoted, the name points at the new version; every already-published version stays exactly as it was. - An exact pin —
python@2026.07.10— always resolves to that one published version and never moves.
# Follows the promoted version — always the latest patched build:
inis run --template python -- ...
# Pins an exact version — byte-identical every time, never moves:
inis run --template python@2026.07.10 -- ...Use the bare name when you want the latest patched build. Pin a version when you need a byte-identical baseline across a run — a reproducible evaluation, or a result you need to reproduce later.
We deprecate rather than delete. When a version is retired it stops being offered for new sessions, but any version you have pinned or built on stays resolvable, so a pin never breaks under you.
Patch cadence
Official templates are rebuilt on a fixed cadence — language runtimes weekly, use-case images at least monthly — to pull in upstream security patches. The built date is shown next to every official template in inis templates ls and in the console. A stale built date is a visible signal that a rebuild is overdue, not something you have to take on trust.
Provenance
For each official template, the console records what a build is made of and what it resolves to:
| Field | What it is |
|---|---|
| Version | The immutable published version the bare name currently resolves to. |
| Base image | The upstream image the build was made from, with its content digest — pinning exactly what went in. |
| Built | When this version's bundle was built, and its rebuild cadence. |
| Bundle hash | The content hash of the published bundle, recomputed server-side at publish time and refused if it doesn't match the bytes uploaded. |