570+ templates in the catalog.

Pick a database, a wiki, an analytics tool or a media server from the catalog and deploy it as a Compose app on your own hardware. Secrets are generated, volumes are named, and a domain gets a certificate.

New templates ship with every release, and any app you run can be saved as a template of your own.

The Levelrail template picker: a search box, a category list with counts and a grid of service cards with Deploy now buttons. The Levelrail template picker: a search box, a category list with counts and a grid of service cards with Deploy now buttons.
  • Ghost
  • Grafana
  • n8n
  • Immich
  • Gitea
  • Vaultwarden
  • Jellyfin
  • Nextcloud
  • Prometheus
  • MinIO
  • Keycloak
  • WordPress

Find a template and install it on a VPS.

Images, ports, volumes and memory, exactly as the catalog lists them.

574 templates

Category pages: AI, Analytics, Applications, Automation, Backups, Communication, Dashboard, Database Tools, Databases, Developer Tools, Finance, Games, Infrastructure, IoT, Mail, Media, Monitoring, Networking, Productivity, Security, Starter Kits, Storage.

arm64 listed is a registry manifest fact, not proof it runs. Verified means the pinned image tag reached healthy in a smoke run. Templates without that mark are plain catalog templates.

in the catalog
574
574 catalog entries, 565 active, 346 proven on a real engine, 228 previews. Each has its own page: what it deploys, what it needs and how to install it on a VPS.
categories
22
From AI and databases to media, finance and IoT.
starter kits
7
Multi-service stacks: web plus database, worker plus queue, reverse proxy plus backends.

More than a Compose file.

Each template is set up to deploy cleanly: secrets, domains and settings are handled so you do not copy values between files.

  • Secrets generated for you

    Passwords and keys are generated at deploy time, stored as secrets, and shared between an app and its database.

    Magic variables
  • A domain and a certificate

    Give a service a domain at deploy time and it is routed with HTTPS, no proxy config to write.

    Domains and ingress
  • An install form, not a YAML hunt

    Templates with an install manifest ask for just the settings that matter: defaults filled in, required values called out.

    How templates are defined
  • Seven starter kits

    Small multi-service templates that show common wiring, so you can copy a pattern for your own stack.

    Starter kits
  • Ready for local AI

    Templates for local models can reserve an NVIDIA GPU on a node that has one, with the runtime installed.

    AI models and GPUs
  • Save your own as a template

    Turn an app you already run into a template, so a second copy is one click away.

    Save an app as a template
  • Try it, then keep it

    One-click deploys start as a trial you can stop and delete, or keep with a single click.

    Keep a trial deployment
  • CLI and API too

    List, inspect and deploy templates from the command line or the API, in scripts and CI.

    CLI and API reference
$ levelrail-cli templates deploy uptime-kuma --name my-status-page

Wiki.js, with its own Postgres.

Productivity, two services

A wiki with Markdown, page permissions and search. The template starts the app and a Postgres next to it, generates the database password, and puts the wiki on your domain.

db
postgres:16-alpine, volume pgdata
wiki
ghcr.io/requarks/wiki:2, port 3000
memory
about 512 MiB recommended
Wiki.js template page
wiki Running wiki.acme.dev, HTTPS
  • wiki ghcr.io/requarks/wiki:2healthy
  • db postgres:16-alpinehealthy
Wiki.js running as a Levelrail app: an engineering handbook page with a contents list, a table and a code block.
A real Wiki.js, deployed from the template and serving its own pages. Any service in the catalog runs the same way.
  • Ghost
  • Grafana
  • n8n
  • Immich
  • Gitea
  • Vaultwarden
  • Jellyfin
  • Nextcloud
  • + 566 more
levelrail-cli, installing Wiki.js
levelrail-cli templates get wikijsSERVICE  IMAGE                     PORTdb       postgres:16-alpine        nonewiki     ghcr.io/requarks/wiki:2   3000levelrail-cli templates install wikijs --name wiki --domain wiki=wiki.acme.devdatabase password generated, stored as a secretwiki is running, HTTPS follows once DNS points at this server

Terminal output is abbreviated. The domain is an example.

It is a Compose app, so it behaves like one.

  1. 01

    A Compose file, nothing hidden

    Each template is a curated Docker Compose body. Deploying one sends it through the same path as any Compose app, so you can read it, edit it first, or save it and deploy it yourself. One app, one service per Compose service, each reconciled on its own.

  2. 02

    Secrets are made for you

    Passwords and keys are generated at deploy time and stored as secrets. The app and its database get the same value, and the generated value is never written into the stored Compose file.

  3. 03

    Volumes hold the data

    State lives in the named volumes the file declares, such as the Postgres volume behind Wiki.js. Images are pinned to a tag, and the previous image stays pinned so a bad upgrade can roll back.

  4. 04

    A domain and a certificate

    Map a service to a domain at install. Ingress issues the HTTPS certificate once DNS points at your server.

How the catalog is checked.

All 574 catalog entries pass structural tests in CI: the Compose file parses, validates against the platform rules and expands into services. 346 are proven on a real engine; the other 228 are previews without that pass yet.

As with any self-hosted app, take a backup before moving an image tag. The status table lists what each template has been through.

Your server, 570+ templates deep.

One command on a Linux server, then browse templates from the dashboard or the CLI.

curl -fsSL https://levelrail.com/install.sh | sudo sh