Lightweight self-hosted PaaS

A lightweight self-hosted PaaS, with the number and its limits

Levelrail is a lightweight, self-hosted deployment platform built around one Go binary for the control plane, with a small separate agent on any node you add. This page gives the measured idle footprint with its hardware and date, who it suits, who it does not, and where the evidence stops.

docker pull ghcr.io/glincker/levelrail:latest

The measured footprint, with its limits

On 2026-10-19, a live Levelrail control plane on a 2 vCPU, 8 GB Linux test box idled at 200 MB of resident memory (peak 253 MB) and 1.5 percent CPU, with all features at their defaults and no apps under load. That is one instance on one box, measured once. It is not a promise for your hardware, and it describes the control plane, not the apps you run on top of it.

A Mac development build on an Apple M4 Max idled at 68 MB with no apps. That is a different machine and a different build, so the two numbers do not compare and the Linux figure is the one to plan with. The method and the raw rows are in the benchmarks, and every row has a date and hardware label. Anything without one is not measured.

Why it stays small: the control plane is one Go binary and nodes you add run a small separate agent, state lives in SQLite in WAL mode, and ingress, TLS and HTTP load balancing use an embedded Caddy. Metrics and logs stay on the node that produced them and are queried on demand, so there is no separate monitoring stack to run.

Who it fits

  • You have one or a few Linux servers, such as a VPS, a home server or a cloud VM, and want deploys from a git repository or an image tag with TLS, logs, metrics and rollback.
  • You want Docker on your own servers as the core runtime, without having to operate Kubernetes. A cluster you already run can still be connected as an experimental deploy target.
  • You want the platform to leave most of a small machine to your own apps, and you are happy to check the footprint on your own hardware before you rely on it.
  • You want an Apache 2.0 project with one edition, no license key.

What is verified and what is not

Levelrail is stable on a single server, and every feature is labelled stable, beta or flagged by the evidence behind it. See what is verified. A single node is the well-tested path and multi-node is labelled beta. Most stable-labelled features have a live end-to-end test on one machine, and almost none has a run on a fresh VPS with a real public domain.

The verified page lists each claim with its source and date, including what was checked on one host only and what has no evidence yet. Template numbers are a good example: 592 catalog entries exist, and 346 are proven on a real engine.

How to check it yourself

Install it on a spare server, leave it idle, and read the Control plane health page, which shows live memory, CPU, goroutines and every background loop. Then deploy your real apps next to your current setup and compare. The install docs cover requirements, and the feature status page labels every feature as stable, beta or flag-gated.

If you are comparing platforms by size, read each project's own documentation for its figures and measure them on the same hardware as yours. The sourced comparison lists what each project states itself and marks everything else as not stated.

Questions

How much memory does the control plane use when idle?

About 200 MB resident, with a peak of 253 MB, and 1.5 percent CPU on a 2 vCPU, 8 GB Linux test box on 2026-10-19 with no apps under load. It is one measurement on one box.

Is the 68 MB figure the real one?

It is the idle figure from a Mac development build. It is a different machine and build, so use the Linux figure for planning.

Is it production ready?

Levelrail is stable on a single server, and every feature is labelled stable, beta or flagged by the evidence behind it. See what is verified. Run it next to your current platform first.

Next