The lighter Dokku alternative

Levelrail vs Dokku: one binary, about 200 MB idle, Apache 2.0.

Control plane memory, drawn to scale
Levelrail, idle, measured ~200 MB
Dokku, stated minimum 1 GB
Install
1 binaryplus one agent per extra node
License
Apache 2.0one edition, no license key
Ahead on
9 of 38capabilities, per Dokku's docs

The memory figures are different kinds of numbers: a documented minimum for Dokku (their docs, stated as 1 GB (docker scheduler), 2 GB per node (k3s scheduler); no CPU minimum stated), one idle measurement for Levelrail (method). As of 2026-11-18.

01

What you gain over Dokku

9 capabilities where Levelrail is a plain yes and Dokku's own docs say partly or no. Full wording and sources are in the table.

Capabilities where Levelrail is ahead of Dokku
Capability Levelrail Dokku
No SSH: agents dial out Agents dial out over mTLS No Commands run on the host, over SSH or git push
Level-triggered reconciler with status reasons Desired state converged, status condition with reason per pass No Event-driven trigger pipeline
Metrics and log search built in Node-local metrics at 15s and full-text log search No Add your own stack
Crashloop diagnosis with last log lines Crashloop detection surfaces the last log lines Partly Restart policy restarts failing containers
One-click rollback with pinned images Prior images pinned so cleanup cannot remove them Partly Failed image deploys restore the previous image reference
CLI and HTTP API CLI and REST API documented Partly CLI over SSH
IAM, audit log and 2FA in the free edition Allow/Deny IAM policies, passkeys and TOTP, and an audit log Partly SSH key users
Audit log of every action Every mutating request recorded Partly Optional event logger records plugin trigger invocations to syslog and /var/log/dokku/events.log
Deploy freezes and policies Cron-defined freeze windows per app with an audited override reason Partly Per-app deploy lock and checks:disable/skip exist
02

All 38 capabilities

Statuses for Dokku are what its own documentation states; "Not stated" means its docs do not say. For Levelrail, "Active" means the feature ships today, with beta and stable tags from the feature status page and the exact scope in each note.

Levelrail
YesActive
Dokku
YesPartlyNo

A rule marks the 9 rows where Levelrail is ahead.

Levelrail compared with Dokku, by capability
Capability Levelrail Dokku
Architecture 3
No SSH: agents dial out (Levelrail ahead) Yesbeta Agents dial out over mTLS; no inbound ports Source for Levelrail, No SSH: agents dial out No Commands run on the host, over SSH or git push Source for Dokku, No SSH: agents dial out
Level-triggered reconciler with status reasons (Levelrail ahead) Yes Desired state converged, status condition with reason per pass Source for Levelrail, Level-triggered reconciler with status reasons No Event-driven trigger pipeline; no reconcile loop described Source for Dokku, Level-triggered reconciler with status reasons
Single control plane binary Yes One control plane binary, plus one agent per extra node Source for Levelrail, Single control plane binary Not applicable
Observability 3
Metrics and log search built in (Levelrail ahead) Yes Node-local metrics at 15s and full-text log search Source for Levelrail, Metrics and log search built in No Add your own stack Source for Dokku, Metrics and log search built in
Crashloop diagnosis with last log lines (Levelrail ahead) Yes Crashloop detection surfaces the last log lines Source for Levelrail, Crashloop diagnosis with last log lines Partly Restart policy restarts failing containers; no crashloop detection Source for Dokku, Crashloop diagnosis with last log lines
Public status page Yesstable Opt-in public page with components, 90 day uptime bars, incidents, maintenance and RSS Source for Levelrail, Public status page Not stated in their docs
Deploys 10
One-click rollback with pinned images (Levelrail ahead) Yesstable Prior images pinned so cleanup cannot remove them. A 5xx spike or crashloop after cutover rolls back automatically (live-tested); the latency signal is beta Source for Levelrail, One-click rollback with pinned images Partly Failed image deploys restore the previous image reference; old images are cleaned up unless skip-cleanup is set, and tags:deploy can redeploy a tagged image manually; no one-command rollback Source for Dokku, One-click rollback with pinned images
Readiness-gated deploys (zero-downtime on one node) Yes Cutover only after the readiness probe passes. Live-tested on one node; multi-node is beta Source for Levelrail, Readiness-gated deploys (zero-downtime on one node) Yes New containers start, proxy switches, old retired after delay Source for Dokku, Readiness-gated deploys (zero-downtime on one node)
Preview environments per pull request Yesstable Stable on GitHub, beta on GitLab and Bitbucket Source for Levelrail, Preview environments per pull request Not stated in their docs
Docker Compose apps Active Pre-built images from the dashboard; git deploys can build Source for Levelrail, Docker Compose apps No Deployment methods listed are git push, Dockerfile, Docker image and buildpacks; Compose files are not a documented deploy input Source for Dokku, Docker Compose apps
Git push deploys from GitHub, GitLab, Bitbucket Active GitHub, GitLab, Bitbucket and Gitea documented; GitLab and Bitbucket previews are beta (synthetic webhooks). A git push remote on your own server (no provider needed) is beta Source for Levelrail, Git push deploys from GitHub, GitLab, Bitbucket Partly git push to deploy branch; git:sync from any cloneable repo; GitHub push webhook deploys only in paid Dokku Pro 1.4.0; no GitLab or Bitbucket webhooks documented Source for Dokku, Git push deploys from GitHub, GitLab, Bitbucket
Builds from source without a Dockerfile Active Railpack detects Node, Python, Go and more. Ruby and PHP are accepted but only plan generation is verified, no live build; Rust, Deno and Elixir are rejected Source for Levelrail, Builds from source without a Dockerfile Partly Heroku buildpacks by default; pack and Railpack need config files Source for Dokku, Builds from source without a Dockerfile
Scheduled jobs Yes Per-app cron jobs with run history, logs, retries and alerts Source for Levelrail, Scheduled jobs Yes Scheduled dokku run tasks via cron:set and app.json Source for Dokku, Scheduled jobs
Deploy freezes and policies (Levelrail ahead) Yesstable Cron-defined freeze windows per app with an audited override reason; also gate image auto-update and scheduled deploys Source for Levelrail, Deploy freezes and policies Partly Per-app deploy lock (apps:lock) and checks:disable/skip exist; no freeze windows or policy engine documented Source for Dokku, Deploy freezes and policies
CI deploys with no stored secret Active GitHub Actions only: a GitHub OIDC token is exchanged for a 15 minute token scoped to one app. Other CI uses an API token Source for Levelrail, CI deploys with no stored secret No Official GitHub Action and Woodpecker examples use a static SSH private key stored as a CI secret; OIDC is not mentioned Source for Dokku, CI deploys with no stored secret
Static site hosting Yes Static HTML from git served by the embedded ingress with TLS; drag-and-drop folder or zip deploy Source for Levelrail, Static site hosting Not stated in their docs
Data 3
Managed databases with scheduled backups Active Many engines, scheduled S3 backups. Postgres point-in-time restore is tested live; MySQL, MariaDB and MongoDB are beta Source for Levelrail, Managed databases with scheduled backups Partly Official plugins create databases; backups manual export, no scheduling Source for Dokku, Managed databases with scheduled backups
Point-in-time database restore Active Postgres stable with an S3 compatible bucket; MySQL and MariaDB beta; MongoDB has no point-in-time restore Source for Levelrail, Point-in-time database restore Not stated in their docs
Encrypted secrets for env vars Yes Envelope-encrypted, masked in UI, injected at container create Source for Levelrail, Encrypted secrets for env vars Not stated in their docs
Networking 4
Private networking between apps or nodes Active Named networks and allow rules; cross-server mesh unverified on real hosts Source for Levelrail, Private networking between apps or nodes Partly Docker networks on one host only; no cross-host networking Source for Dokku, Private networking between apps or nodes
Load balancing across replicas Active Apps with more than one replica are round-robin balanced by default, with failed-replica skip and retry. The configurable balancer (health checks, sticky sessions, weights, drain) is experimental, behind a flag, verified on one machine only. HTTP only Source for Levelrail, Load balancing across replicas Partly Nginx round-robin across scaled web containers; other processes need config Source for Dokku, Load balancing across replicas
Request firewall, rate limits, bot protection Yes Ordered rules, IP bans, bot handling, challenges and rate limits Source for Levelrail, Request firewall, rate limits, bot protection Not stated in their docs
Automatic TLS certificates Active Self-signed by default; public ACME (HTTP-01) has one recorded run on a live VPS. Renewal near expiry and DNS-01 wildcards are not exercised live; CAs needing EAB are unsupported Source for Levelrail, Automatic TLS certificates Partly Let's Encrypt via official plugin; manual certs otherwise Source for Dokku, Automatic TLS certificates
Platform 11
Multi-node Activebeta Join, cordon and drain with real container relocation verified across two local Docker daemons; WireGuard mesh and cross-host transport still unverified. Resource-aware placement is beta Source for Levelrail, Multi-node Partly One host by default; optional k3s scheduler joins worker and server nodes over SSH with scheduler-k3s:cluster:add Source for Dokku, Multi-node
One-click service templates Yesbeta 592 catalog entries, 583 active; 346 proven on a real engine, 246 previews without that pass yet Source for Levelrail, One-click service templates Not stated in their docs
Autoscaling Active Beta: CPU, memory or request-rate scaling with cooldowns and reasons Source for Levelrail, Autoscaling Partly docker-local scheduler scales manually via ps:scale; the optional k3s scheduler documents autoscaling through KEDA Source for Dokku, Autoscaling
Sleep idle apps, wake on request Yesstable Opt in per app; stops after 5 minutes to 7 days idle and wakes on the next request. Verified live against a real Docker daemon and the real ingress Source for Levelrail, Sleep idle apps, wake on request Not stated in their docs
CLI and HTTP API (Levelrail ahead) Yes CLI and REST API documented; MCP server is beta Source for Levelrail, CLI and HTTP API Partly CLI over SSH; JSON API only in paid Dokku Pro Source for Dokku, CLI and HTTP API
Deploy and alert notifications Active Webhook and SMTP email have live e2e; 15 vendor kinds (Slack, Discord, PagerDuty and more) are beta, tested against local fakes Source for Levelrail, Deploy and alert notifications Partly Deploy webhook via community plugin; no built-in notifications Source for Dokku, Deploy and alert notifications
MCP / AI assistant integration Yesbeta MCP server (beta) with over 240 tools in toolsets an agent enables on demand (256 at last count, 21 in the default session); in-app chat is behind a flag Source for Levelrail, MCP / AI assistant integration Not stated in their docs
Runs on servers you own Yes Runs on Linux servers you provide Source for Levelrail, Runs on servers you own Yes Scripts running on your own host Source for Dokku, Runs on servers you own
Open source license Yes Apache 2.0, one edition, no paid tier Source for Levelrail, Open source license Yes Permissive MIT-style license per repo LICENSE file Source for Dokku, Open source license
Declarative apply of the whole platform Activebeta YAML export, plan and apply from CLI, dashboard, MCP or CI, plus a Terraform and OpenTofu provider. Experimental, behind a flag Source for Levelrail, Declarative apply of the whole platform Partly app.json declares per-app health checks, cron, formation and env; there is no whole-platform spec to apply Source for Dokku, Declarative apply of the whole platform
Functions and one-off jobs Active Node, Python or Go handlers that sleep when idle and wake on the first request; scheduled and background calls with retries Source for Levelrail, Functions and one-off jobs Partly Scheduled cron tasks in app.json run as one-off containers; a lambda builder exists for AWS Lambda functions; no functions runtime Source for Dokku, Functions and one-off jobs
Security 4
IAM, audit log and 2FA in the free edition (Levelrail ahead) Yesstable Allow/Deny IAM policies (stable, live e2e), passkeys and TOTP, and an audit log with a verifiable hash chain, CSV export and forwarding, all in the one edition Source for Levelrail, IAM, audit log and 2FA in the free edition Partly SSH key users; admin keyword grants key management; no RBAC Source for Dokku, IAM, audit log and 2FA in the free edition
SAML or SCIM single sign-on Activebeta OIDC sign-in (17 named providers plus generic OpenID Connect) is on by default once configured. SAML and SCIM are beta, behind a toggle and off by default; SAML ran against Keycloak and SimpleSAMLphp in a local lab, not Okta or Entra Source for Levelrail, SAML or SCIM single sign-on Not stated in their docs
Audit log of every action (Levelrail ahead) Yes Every mutating request recorded; verifiable hash chain, CSV or NDJSON export, retention, streaming to a webhook or S3 bucket Source for Levelrail, Audit log of every action Partly Optional event logger (events:on) records plugin trigger invocations to syslog and /var/log/dokku/events.log; page does not show who ran a command or a retention period Source for Dokku, Audit log of every action
Two-person deploy approvals Yesstable A different person with the deploy ability must approve; the requester cannot approve their own. Approval also works from Slack or Discord Source for Levelrail, Two-person deploy approvals Not stated in their docs

All ten projects are on the full matrix. Product names and logos belong to their owners and are used for identification only.

03

Move over from Dokku

No importer for Dokku. Deploy the same repositories and recreate environment variables and domains.

docker pull ghcr.io/glincker/levelrail:latest
04

Questions about Levelrail and Dokku

Is Levelrail a good alternative to Dokku?

Yes. Levelrail does what Dokku does with a lighter footprint and more built in. A dashboard with deploy history and one-click rollback to a pinned previous image in the free edition. Dokku Pro adds a paid web UI. Metrics and log search in the core, where Dokku ships log sinks and expects an external stack. More servers join with a one-time token and an agent that dials out. A read-only importer and a dry-run mode let you move without touching Dokku.

Can I move from Dokku to Levelrail?

No importer for Dokku. Deploy the same repositories and recreate environment variables and domains.

Is Levelrail ready to replace Dokku in production?

Run both side by side, move one domain at a time and keep Dokku as a fallback until you are happy. The feature status page lists the maturity of every area.

05

Keep exploring