The lighter Coolify alternative

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

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

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

01

What you gain over Coolify

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

Capabilities where Levelrail is ahead of Coolify
Capability Levelrail Coolify
No SSH: agents dial out Agents dial out over mTLS No SSH from the control plane to each server
Single control plane binary One control plane binary, plus one agent per extra node No Three base containers: app, PostgreSQL and Redis
Metrics and log search built in Node-local metrics at 15s and full-text log search Partly Sentinel historical CPU, memory, disk, network and load charts
Readiness-gated deploys (zero-downtime on one node) Cutover only after the readiness probe passes Partly Starts replacement first
Encrypted secrets for env vars Envelope-encrypted, masked in UI, injected at container create Partly Doppler, Infisical and HashiCorp Vault secret managers documented
Request firewall, rate limits, bot protection Ordered rules, IP bans, bot handling, challenges and rate limits Partly Rate limits via custom Traefik middleware
CLI and HTTP API CLI and REST API documented Partly REST API with scoped tokens and a CLI built on it
Deploy freezes and policies Cron-defined freeze windows per app with an audited override reason Partly Image scanning has a per-instance/team/server/app 'Block deploys' policy with a 'Deploy anyway' override
02

All 38 capabilities

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

A rule marks the 8 rows where Levelrail is ahead.

Levelrail compared with Coolify, by capability
Capability Levelrail Coolify
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 SSH from the control plane to each server Source for Coolify, 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 base containers: app, PostgreSQL and Redis Source for Coolify, 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 Sentinel historical CPU, memory, disk, network and load charts; log drains to Axiom, New Relic, CloudWatch (new in v4.6.0), Fluent Bit; docs say log queries and dashboards need an external system Source for Coolify, 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 Redeploys a retained older image; retention is configurable Source for Coolify, 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 Starts replacement first; docs say no zero-downtime guarantee Source for Coolify, 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 Yes Per pull request previews; full UI needs a GitHub App Source for Coolify, 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 Deploys docker-compose.yml from a git repository or pasted file Source for Coolify, 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 Push webhooks for GitHub, GitLab and Bitbucket sources Source for Coolify, 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 and Railpack detect and build without a Dockerfile Source for Coolify, 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 tasks run commands in containers on cron schedules Source for Coolify, 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 Image scanning (Syft and Grype, v4.7.0) has a per-instance/team/server/app 'Block deploys' policy (Off, On, Strict) with a 'Deploy anyway' override; it is a vulnerability gate, not deploy freezes or change windows Source for Coolify, 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 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 pack serves committed files through Nginx; Nixpacks or Railpack with Static site type and publish directory for source projects Source for Coolify, 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 Scheduled backups to S3-compatible storage for six database engines Source for Coolify, 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 No Scheduled engine-aware dumps with S3 copy; no continuous archiving or restore to a timestamp is described Source for Coolify, Point-in-time database restore
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 Doppler, Infisical and HashiCorp Vault secret managers documented; encryption of ordinary env vars at rest not stated; v4.6.0 API/MCP can manage secret managers Source for Coolify, 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 Partly Shared Docker networks on one server; cross-server networking not documented Source for Coolify, 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 Traffic balancing needs an external cloud load balancer, set up manually Source for Coolify, Load balancing across replicas
Request firewall, rate limits, bot protection (Levelrail ahead) Yes Ordered rules, IP bans, bot handling, challenges and rate limits Source for Levelrail, Request firewall, rate limits, bot protection Partly Rate limits via custom Traefik middleware; no bot protection Source for Coolify, Request firewall, rate limits, bot protection
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 Traefik or Caddy requests and renews certificates for https domains Source for Coolify, 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 Manages each server over SSH Source for Coolify, 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 Large catalog of one-click services Source for Coolify, One-click service templates
Autoscaling Active Beta: CPU, memory or request-rate scaling with cooldowns and reasons Source for Levelrail, Autoscaling No Scaling is manual; operators decide when to add servers Source for Coolify, 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 REST API with scoped tokens (read to root, delete ability since v4.6.0) and a CLI built on it; docs do not claim full dashboard parity Source for Coolify, 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 Email, Discord, Telegram, Slack, Pushover and webhook channels Source for Coolify, 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 MCP server over Streamable HTTP with team-scoped tokens Source for Coolify, 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 Coolify, Runs on servers you own
Open source license Yes Apache 2.0, one edition, no paid tier Source for Levelrail, Open source license Yes Listed as open source Source for Coolify, 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 Scheduled tasks run commands in containers on cron with execution history; no functions runtime documented Source for Coolify, Functions and one-off jobs
Security 4
IAM, audit log and 2FA in the free edition 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 Yes Owner/Admin/Member roles, team audit log (90 day retention) and 2FA documented; docs and pricing say self-hosted has the same features, no paid tier Source for Coolify, 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 Partly OpenID Connect sign-in documented; SAML and SCIM not mentioned Source for Coolify, SAML or SCIM single sign-on
Audit log of every action 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 Yes Team audit log of resource changes, deployments, backups, membership, API tokens and settings from UI, API, MCP and webhooks; admins and owners; events pruned after 90 days; no plan restriction stated Source for Coolify, 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 Coolify

Levelrail has a read-only importer for Coolify with a dry-run mode. It creates apps and databases here and never changes Coolify, 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 Coolify

Is Levelrail a good alternative to Coolify?

Yes. Levelrail does what Coolify does with a lighter footprint and more built in. An agent dials out over mTLS to the Docker Engine API instead of SSH from the control plane. A level-triggered reconciler records a status reason per pass, instead of Docker Compose per resource. Full-text log search and pinned-image rollback ship in the core. A read-only importer and a dry-run mode let you move without touching Coolify.

Can I move from Coolify to Levelrail?

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

Is Levelrail ready to replace Coolify in production?

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

05

Keep exploring