Get started
How-to guides
Reference
Concepts
Self-host gallery
Appendix
What is different under the hood
A reconciler, not Swarm services
Desired state lives in the database and a level-triggered loop converges each node toward it, recording a status condition with a reason after every pass.
Agent per node, nothing inbound
Each extra server runs a small agent that dials out to the control plane with mutual TLS. Cordon and drain relocate containers between real Docker daemons.
Observability is core
Metrics, full-text logs, crashloop detection with the last log lines, and alerts to 18 notification channel kinds all ship in the box, with no extra stack to install.
Bring your apps with you
The importer reads your existing instance through its own HTTP API and never changes anything there. Run it with —dry-run first to see exactly what would be created.install, import, verify
Dokploy and Levelrail, side by side
Dokploy is a polished project built on a mature mechanism. These are the design differences.
Read the full comparison
Evaluate it safely
1
Install on a spare box
Run the install script on any Linux server with outbound access.
2
Import read-only
The importer only reads from Dokploy through its API. Use —dry-run to see the report first.
3
Deploy and compare
Run both for a while. Rollback, readiness gating and the built-in charts are easy to judge side by side.
Frequently asked questions
Does Levelrail use Docker Swarm?
Does Levelrail use Docker Swarm?
No. It runs plain Docker containers on each node, driven through the Docker Engine API by a reconciler. Placement across nodes is explicit, and cordon and drain are supported.
How do I migrate from Dokploy?
How do I migrate from Dokploy?
Use the platform importer, levelrail-cli import platform dokploy with your Dokploy URL. It is read-only against the source and supports —dry-run and —only.
Is Levelrail free?
Is Levelrail free?
Yes, Apache 2.0 with a single edition and no feature gated behind a plan.
How mature is it?
How mature is it?
It is pre-release and moving fast. Single node is the most tested path, and multi-node enrollment, cordon and drain have been verified against real Docker daemons.