# Levelrail

> Levelrail is a self-hosted deployment platform. It turns one or more Linux servers into a private cloud: push to a git repository or an image tag and it builds, deploys and keeps the app running with TLS, logs, metrics and rollback. The control plane and the node agent are each a single Go binary, Docker is the only container runtime, and the license is Apache 2.0. It is pre-release: a single node is the well-tested path and multi-node is in beta.

## Key facts
- Agents dial out to the control plane over mutual TLS; nothing connects in, so no inbound ports or SSH keys are needed on managed servers.
- A level-triggered reconciler compares desired and observed state on every pass and records a status condition with a reason.
- State is SQLite in WAL mode; ingress, TLS and HTTP load balancing use an embedded Caddy; metrics and logs stay on the node that produced them.
- Idle footprint on a development build: 68 MB of memory with no apps, 91 MB with 500 suspended apps, 1.6% CPU at 500 suspended apps.
- 358 one-click service templates; 48 of the top 50 passed a live smoke run on 2026-10-19, the rest pass structural checks only.

## Pages
- [Home](https://levelrail.com/): What Levelrail is, the three tiers (edge, control plane, nodes), the dashboard, the template gallery and the install command.
- [Deploys and rollback](https://levelrail.com/deploys/): Readiness-gated cutover, digest-pinned images, one-command rollback, previews, schedules and pipelines.
- [Observability](https://levelrail.com/observability/): Per-app metrics, searchable logs, automatic crashloop context and alerts, kept on each node and queried on demand.
- [Networking: seven layers, three of them run by Levelrail](https://levelrail.com/networking/): Levelrail runs layer 7 (ingress, TLS, HTTP balancing, request firewall), layer 3 (WireGuard mesh, private networks, mesh DNS) and part of layer 4. The rest stays with your host and your app.
- [Architecture](https://levelrail.com/architecture/): The level-triggered reconciler, agents that dial out, and the four written decisions (ADR 002, 003, 007, 008).
- [Service templates](https://levelrail.com/templates/): 358 one-click self-host templates across databases, CMSs, analytics, automation, storage and monitoring.
- [Comparison](https://levelrail.com/compare/): A sourced comparison with Coolify, Dokploy, CapRover, Dokku, Kamal, Vercel, Heroku, Railway and Cloud Run across 28 capabilities, including what Levelrail does not do yet.
- [Open source](https://levelrail.com/open-source/): Apache 2.0, one edition, no license key and no enterprise tier; what is not here yet; frequently asked questions.

## Documentation
- [Quickstart](https://docs.levelrail.com/getting-started): Install and deploy a first app.
- [Installing](https://docs.levelrail.com/installing): Server install and requirements.
- [CLI reference](https://docs.levelrail.com/cli-reference): Every levelrail-cli command.
- [API reference](https://docs.levelrail.com/api-reference): REST endpoints and abilities.
- [Feature status](https://docs.levelrail.com/feature-status): What is stable, beta or experimental.
- [Security](https://docs.levelrail.com/security): Security model and hardening.
- [Comparison](https://docs.levelrail.com/comparison): Comparison with other platforms.
- [Roadmap](https://docs.levelrail.com/roadmap): What is planned next.

## Source and contact
- [GitHub](https://github.com/glincker/levelrail): source, issues and discussions
- Contact: support@levelrail.com
- Built by GLINR STUDIOS (https://glinr.com)

## Optional
- [Full text of this site](https://levelrail.com/llms-full.txt)