orgo.ai/v1 document — copy it, publish and build it, then launch a computer from its ref. The first four use the short sugar form; the last uses the canonical form.
Publishing and building templates requires a Scale plan. Curated templates are launchable on every paid plan.
Minimal
The smallest valid template — a blank Linux desktop. Everything exceptapi_version and the name/version is optional.
my-template.yaml
Static site (nginx)
A single HTTP service on port 8000, served by nginx, with Chrome set to auto-open the page when the desktop starts. The headline is driven by a compile-time variable, so changing it is a one-line edit.static-site.yaml
Browser desktop
Chrome launches automatically on boot. Chrome is already in the base image, so there’s no install step — just anautostart entry.
browser-desktop.yaml
Background worker with triggers
A long-running service that logs a tick every 10 seconds, kept alive by a process health check, plus two triggers: a cron heartbeat and a CPU watchdog that notifies on sustained load.heartbeat-worker.yaml
Agent with a user-supplied key
The canonical form, with a secret the launching user supplies from their vault. The CLI is installed at build time; theon_resume hook starts it with the launcher’s own key after /root/.env is injected at create. This is the pattern the curated system/claude-code template uses.
claude-code.yaml
Publish, build, launch
The flow is the same for any of the above:Quickstart
The full walkthrough, end to end.
Schema reference
Every field explained.
Secrets
The full secret-injection model.
Publish API
Ship a template over HTTP.