The lighter Dokploy alternative

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

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

The memory figures are different kinds of numbers: a documented minimum for Dokploy (their docs, stated as 2 GB (30 GB disk; no CPU minimum stated)), one idle measurement for Levelrail (method). As of 2026-11-18.

01

What you gain over Dokploy

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

Capabilities where Levelrail is ahead of Dokploy
Capability Levelrail Dokploy
No SSH: agents dial out Agents dial out over mTLS No Connects to remote servers over SSH keys
Single control plane binary One control plane binary, plus one agent per extra node No Three parts: Next.js app, PostgreSQL and Traefik
Metrics and log search built in Node-local metrics at 15s and full-text log search Partly CPU, memory, disk, network metrics with threshold alerts, real-time logs, and v0.31.0 Vector shipping of logs
Readiness-gated deploys (zero-downtime on one node) Cutover only after the readiness probe passes Partly Swarm health check plus update config with automatic rollback on failure is documented
Preview environments per pull request Stable on GitHub, beta on GitLab and Bitbucket Partly Preview per pull request, documented for GitHub only
Encrypted secrets for env vars Envelope-encrypted, masked in UI, injected at container create Partly External secrets providers fetch values at deploy time
CLI and HTTP API CLI and REST API documented Partly HTTP API and a CLI
IAM, audit log and 2FA in the free edition Allow/Deny IAM policies, passkeys and TOTP, and an audit log Partly Owner, Admin, Member roles and 2FA/passkeys in self-hosted
Audit log of every action Every mutating request recorded Partly Enterprise only
02

All 38 capabilities

Statuses for Dokploy 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
Dokploy
YesPartlyNo

A rule marks the 9 rows where Levelrail is ahead.

Levelrail compared with Dokploy, by capability
Capability Levelrail Dokploy
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 Connects to remote servers over SSH keys Source for Dokploy, No SSH: agents dial out
Level-triggered reconciler with status reasons Yes Desired state converged, status condition with reason per pass Source for Levelrail, Level-triggered reconciler with status reasons Not stated in their docs
Single control plane binary (Levelrail ahead) Yes One control plane binary, plus one agent per extra node Source for Levelrail, Single control plane binary No Three parts: Next.js app, PostgreSQL and Traefik Source for Dokploy, Single control plane binary
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 Partly CPU, memory, disk, network metrics with threshold alerts, real-time logs, and v0.31.0 Vector shipping of logs and metrics to external providers; log search not stated Source for Dokploy, Metrics and log search built in
Crashloop diagnosis with last log lines Yes Crashloop detection surfaces the last log lines Source for Levelrail, Crashloop diagnosis with last log lines Not stated in their docs
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 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 Yes Registry-based rollback to any previous deployment image (needs a configured registry); Swarm automatic rollback on failed health check Source for Dokploy, One-click rollback with pinned images
Readiness-gated deploys (zero-downtime on one node) (Levelrail ahead) 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) Partly Swarm health check plus update config with automatic rollback on failure is documented (needs a /health endpoint and curl in the image) Source for Dokploy, Readiness-gated deploys (zero-downtime on one node)
Preview environments per pull request (Levelrail ahead) Yesstable Stable on GitHub, beta on GitLab and Bitbucket Source for Levelrail, Preview environments per pull request Partly Preview per pull request, documented for GitHub only Source for Dokploy, Preview environments per pull request
Docker Compose apps Active Pre-built images from the dashboard; git deploys can build Source for Levelrail, Docker Compose apps Yes Compose deploys from Git or pasted file; build unsupported in Stack mode Source for Dokploy, 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 Yes Auto deploy on push for GitHub, GitLab, Bitbucket and Gitea Source for Dokploy, 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 Yes Nixpacks is the default; Railpack and buildpacks also offered Source for Dokploy, 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 Schedule Jobs runs cron jobs in apps, compose services or servers Source for Dokploy, Scheduled jobs
Deploy freezes and policies 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 Not stated in their docs
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 Not stated in their docs
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 Yes Static build type serves files through NGINX; Nixpacks publish directory for built output Source for Dokploy, Static site hosting
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 Yes Creates MySQL, Postgres, MongoDB, Redis, MariaDB; scheduled backups Source for Dokploy, 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 (Levelrail ahead) Yes Envelope-encrypted, masked in UI, injected at container create Source for Levelrail, Encrypted secrets for env vars Partly External secrets providers fetch values at deploy time; encryption not stated Source for Dokploy, Encrypted secrets for env vars
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 Not stated in their docs
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 Yes unchanged Source for Dokploy, 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 Yes Per-domain HTTPS with a Let's Encrypt certificate resolver option Source for Dokploy, 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 Yes Multi-node scheduling through Docker Swarm Source for Dokploy, 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 Yes 602 or more one-click open source templates Source for Dokploy, One-click service templates
Autoscaling Active Beta: CPU, memory or request-rate scaling with cooldowns and reasons Source for Levelrail, Autoscaling Not stated in their docs
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 HTTP API and a CLI; CLI covers app create, deploy, stop, delete Source for Dokploy, 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 Yes Slack, Discord, Email, Telegram, Teams and Webhook notifications Source for Dokploy, 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 Yes Official Dokploy/mcp package: 508 tools generated from the OpenAPI spec, stdio and Streamable HTTP, secret redaction by default. Documented in the GitHub repo, not the docs site Source for Dokploy, MCP / AI assistant integration
Runs on servers you own Yes Runs on Linux servers you provide Source for Levelrail, Runs on servers you own Yes Web application on your server Source for Dokploy, Runs on servers you own
Open source license Yes Apache 2.0, one edition, no paid tier Source for Levelrail, Open source license Yes Apache-2.0 core with a proprietary source-available directory; enterprise features need a license key Source for Dokploy, 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 Not stated in their docs
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 Schedule Jobs run cron commands in apps, compose services, remote hosts or the Dokploy container with run logs; no functions runtime documented Source for Dokploy, 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 Owner, Admin, Member roles and 2FA/passkeys in self-hosted; custom roles and audit logs need an Enterprise license Source for Dokploy, 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 Yes SAML and OIDC SSO plus SCIM, under the Enterprise license Source for Dokploy, SAML or SCIM single sign-on
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 Enterprise only; v0.31.0 adds export to CSV, TSV or JSON (newest 10,000 per export); retention not stated Source for Dokploy, 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 Dokploy

Levelrail has a read-only importer for Dokploy with a dry-run mode. It creates apps and databases here and never changes Dokploy, so you can run both and move DNS one domain at a time. Some things do not migrate automatically, such as compose stacks, volume contents and certificates.

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

Questions about Levelrail and Dokploy

Is Levelrail a good alternative to Dokploy?

Yes. Levelrail does what Dokploy does with a lighter footprint and more built in. Plain Docker with a reconciler and a small agent per node, with no Swarm or overlay network. Full-text log search and crashloop diagnosis ship in the core with no extra stack. Dokploy now has metrics with threshold alerts. One Go binary with embedded SQLite and embedded Caddy, instead of Traefik. A read-only importer and a dry-run mode let you move without touching Dokploy.

Can I move from Dokploy to Levelrail?

Yes. Levelrail has a read-only importer for Dokploy with a dry-run mode. It creates apps and databases here without touching Dokploy, so you can run both and move DNS one domain at a time. Some things do not migrate automatically, and the migrating from dokploy page lists them.

Is Levelrail ready to replace Dokploy in production?

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

05

Keep exploring