Templates
Install ready-made software on a running server without SSH, from the command line.
Templates are software made and reviewed by Layerbeat — coding agents (Claude Code, Codex, Cursor CLI, OpenCode, Pi, omp, herdr, luvus), Docker, Caddy, HTTPS for your app, Supabase — that Layerbeat installs on your running Linux server for you. No SSH, and your settings reach the server as data, never as commands.
Find one
layerbeat template ls # the catalog, no sign-in needed
layerbeat template show supabase # what it installs, its settings, ports and READMEDeploy
layerbeat template deploy claude-code --server agent-01 --wait
layerbeat template deploy https-proxy --server agent-01 \
--input domain=app.example.com --input upstream=127.0.0.1:3000 \
--accept-ports --wait--input NAME=VALUEfills a setting (repeatable);template showlists them.- A template that opens ports to the internet needs your agreement:
--ports 80,443, or--accept-portsfor exactly the ports it lists (they are printed before anything happens). Layerbeat opens only ports that aren't open yet, and closes them again when you remove the template. - Templates it needs are deployed first: HTTPS for an app brings Caddy; Supabase brings Docker and Caddy.
Follow and manage
layerbeat template deployments # what is deployed where
layerbeat template status claude-code --server agent-01
layerbeat template check claude-code --server agent-01 # run its health check now
layerbeat template update dep_... # the latest version, or retry a failed run
layerbeat template rm supabase --server agent-01 # data is kept…
layerbeat template rm supabase --server agent-01 --delete-data # …unless you askA deployment can be named by its dep_... ID, or by the template with --server.
| Status | Meaning |
|---|---|
deploying | Being installed |
ready | Done. A service (Caddy, Docker, HTTPS for an app, Supabase) is running; a tool (the coding agents) is installed, ready for you to run |
failed | The script reported a problem; see the output with template status, then retry with template update |
unknown | The result couldn't be confirmed. Run template check, then template update to retry. Layerbeat never re-runs a script on its own |
removing, removed | Being removed, or gone |
See exactly what runs
layerbeat template script https-proxy --input domain=app.example.com
layerbeat template script dep_...This prints the full script the server receives: Layerbeat's short header, which passes your settings as data and reports the result, then the template's reviewed install script.
Editing a template's script before deploying (template deploy --script FILE) is not available yet; Layerbeat runs the reviewed scripts only.