Compare, self-hosted

Deliberately minimal: no control plane, database or agent, running over SSH from your machine or CI.

As of 2026-11-05. Statements about Kamal come from its own public documentation, linked on each row. Spot something outdated? Tell us and we will fix it.

Latest release
v2.12.0, 2026-06-18
License
MIT, no paid tier
Pricing
Free
  • 38capabilities compared, from each project's own docs
  • 1rows where Kamal is ahead
  • 8rows where Levelrail is ahead

The short verdict

Kamal is good at

Kamal is good at: as few moving parts as possible; and pairs with kamal-proxy for zero-downtime cutover; and no dashboard needed, which suits some teams; and MIT licensed with no paid tier, a built-in deploy lock, hooks that can abort a deploy, and native OpenTelemetry for deploy logs.

When to choose Kamal

Choose Kamal when you want the fewest possible moving parts and do not need a dashboard.

Where Levelrail differs

Levelrail differs here: desired state lives in a database, with a reconciler recording a status reason after every pass; and agents dial out, so CI uses a scoped API token instead of holding SSH keys; and adds a dashboard, deploy history, rollback and built-in observability, and is heavier by design. Levelrail has a shorter track record: a single node is the well-tested path and multi-node is labelled beta, so its track record is much shorter than Kamal's.

Where Kamal is ahead

1
  • Multi-node

    Yes Kamal: SSH to each server.
    Partly Levelrail: partly, 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.

Where Levelrail is ahead

8
  • No SSH: agents dial out

    Yes Levelrail: Agents dial out over mTLS; no inbound ports.
    No Kamal: no, SSH from your machine or CI to each server.
  • Level-triggered reconciler with status reasons

    Yes Levelrail: Desired state converged, status condition with reason per pass.
    No Kamal: no, none: it runs Docker commands per deploy.
  • Metrics and log search built in

    Yes Levelrail: Node-local metrics at 15s and full-text log search.
    No Kamal: no, bring your own.
  • One-click rollback with pinned images

    Yes Levelrail: 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.
    Partly Kamal: partly, rollback to chosen version; old containers pruned after 3 days.
  • Encrypted secrets for env vars

    Yes Levelrail: Envelope-encrypted, masked in UI, injected at container create.
    Partly Kamal: partly, secrets from files or password managers; host env file, no encryption documented.
  • IAM, audit log and 2FA in the free edition

    Yes Levelrail: 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.
    Partly Kamal: partly, per-server audit log (.kamal/app-audit.log) of deploy steps, last 50 lines via kamal audit; no users, roles or 2FA.
  • Audit log of every action

    Yes Levelrail: Every mutating request recorded; verifiable hash chain, CSV or NDJSON export, retention, streaming to a webhook or S3 bucket.
    Partly Kamal: partly, per-server .kamal/app-audit.log of deploy steps, read with kamal audit; entries carry a user tag but the page does not say which person; hooks expose KAMAL_PERFORMER for custom reports.
  • Deploy freezes and policies

    Yes Levelrail: Cron-defined freeze windows per app with an audited override reason; also gate image auto-update and scheduled deploys.
    Partly Kamal: partly, kamal lock acquire can block deploys during a maintenance window and a non-zero exit from pre-deploy or other hooks aborts the command (hooks can be skipped with --skip_hooks); no scheduled freeze windows or policy engine.

38 capabilities side by side

Yes, partly and no are what each project's own documentation states. "Not stated" means their docs do not say, which is not the same as no. Levelrail maturity tags (beta, stable) come from its feature status page.

Levelrail compared with Kamal, by capability
Capability Levelrail Kamal
Architecture 3
No SSH: agents dial out Yesbeta Agents dial out over mTLS; no inbound portsSource for Levelrail, No SSH: agents dial out No SSH from your machine or CI to each serverSource for Kamal, No SSH: agents dial out
Level-triggered reconciler with status reasons Yes Desired state converged, status condition with reason per passSource for Levelrail, Level-triggered reconciler with status reasons No None: it runs Docker commands per deploySource for Kamal, Level-triggered reconciler with status reasons
Single control plane binary Yes One control plane binary, plus one agent per extra nodeSource for Levelrail, Single control plane binary Not applicable
Observability 3
Metrics and log search built in Yes Node-local metrics at 15s and full-text log searchSource for Levelrail, Metrics and log search built in No Bring your ownSource for Kamal, Metrics and log search built in
Crashloop diagnosis with last log lines Yes Crashloop detection surfaces the last log linesSource 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 RSSSource 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 betaSource for Levelrail, One-click rollback with pinned images Partly Rollback to chosen version; old containers pruned after 3 daysSource for Kamal, 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 betaSource for Levelrail, Readiness-gated deploys (zero-downtime on one node) Yes Zero-downtime cutover with kamal-proxySource for Kamal, Readiness-gated deploys (zero-downtime on one node)
Preview environments per pull request Yesstable Stable on GitHub, beta on GitLab and BitbucketSource for Levelrail, Preview environments per pull request Not stated in their docs
Docker Compose apps Partly Pre-built images from the dashboard; git deploys can buildSource for Levelrail, Docker Compose apps Not stated in their docs
Git push deploys from GitHub, GitLab, Bitbucket Partly 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 betaSource for Levelrail, Git push deploys from GitHub, GitLab, Bitbucket Not stated in their docs
Builds from source without a Dockerfile Partly 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 rejectedSource for Levelrail, Builds from source without a Dockerfile Partly Dockerfile required by default; buildpacks only when configured explicitlySource for Kamal, Builds from source without a Dockerfile
Scheduled jobs Yes Per-app cron jobs with run history, logs, retries and alertsSource for Levelrail, Scheduled jobs Not stated in their docs
Deploy freezes and policies Yesstable Cron-defined freeze windows per app with an audited override reason; also gate image auto-update and scheduled deploysSource for Levelrail, Deploy freezes and policies Partly kamal lock acquire can block deploys during a maintenance window and a non-zero exit from pre-deploy or other hooks aborts the command (hooks can be skipped with --skip_hooks); no scheduled freeze windows or policy engineSource for Kamal, Deploy freezes and policies
CI deploys with no stored secret Partly GitHub Actions only: a GitHub OIDC token is exchanged for a 15 minute token scoped to one app. Other CI uses an API tokenSource 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 deploySource for Levelrail, Static site hosting Not stated in their docs
Data 3
Managed databases with scheduled backups Partly Many engines, scheduled S3 backups. Postgres point-in-time restore is tested live; MySQL, MariaDB and MongoDB are betaSource for Levelrail, Managed databases with scheduled backups Partly Accessories run containers such as MySQL; no backups documentedSource for Kamal, Managed databases with scheduled backups
Point-in-time database restore Partly Postgres stable with an S3 compatible bucket; MySQL and MariaDB beta; MongoDB has no point-in-time restoreSource 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 createSource for Levelrail, Encrypted secrets for env vars Partly Secrets from files or password managers; host env file, no encryption documentedSource for Kamal, Encrypted secrets for env vars
Networking 4
Private networking between apps or nodes Partly Named networks and allow rules; cross-server mesh unverified on real hostsSource for Levelrail, Private networking between apps or nodes Partly Containers share a custom Docker network per host, no cross server networkingSource for Kamal, Private networking between apps or nodes
Load balancing across replicas Partly 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 onlySource for Levelrail, Load balancing across replicas Not stated in their docs
Request firewall, rate limits, bot protection Yes Ordered rules, IP bans, bot handling, challenges and rate limitsSource for Levelrail, Request firewall, rate limits, bot protection Not stated in their docs
Automatic TLS certificates Partly 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 unsupportedSource for Levelrail, Automatic TLS certificates Partly kamal-proxy Let's Encrypt HTTPS, only with one server and host setSource for Kamal, Automatic TLS certificates
Platform 11
Multi-node Partlybeta 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 betaSource for Levelrail, Multi-node Yes SSH to each serverSource for Kamal, Multi-node
One-click service templates Yesbeta 442 templates; 101 of 108 that need no operator configuration passed the 2026-10-25 local deploy smoke, the rest are untestedSource for Levelrail, One-click service templates Not stated in their docs
Autoscaling Partly Beta: CPU, memory or request-rate scaling with cooldowns and reasonsSource 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 ingressSource for Levelrail, Sleep idle apps, wake on request Not stated in their docs
CLI and HTTP API Yes CLI and REST API documented; MCP server is betaSource for Levelrail, CLI and HTTP API Not applicable
Deploy and alert notifications Partly Webhook and SMTP email have live e2e; 15 vendor kinds (Slack, Discord, PagerDuty and more) are beta, tested against local fakesSource for Levelrail, Deploy and alert notifications Partly Hooks run custom scripts; no built-in Slack, Discord or emailSource for Kamal, 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 flagSource for Levelrail, MCP / AI assistant integration Not stated in their docs
Runs on servers you own Yes Runs on Linux servers you provideSource for Levelrail, Runs on servers you own Yes Runs against servers you own over SSHSource for Kamal, Runs on servers you own
Open source license Yes Apache 2.0, one edition, no paid tierSource for Levelrail, Open source license Yes Released under the MIT LicenseSource for Kamal, Open source license
Declarative apply of the whole platform Partlybeta YAML export, plan and apply from CLI, dashboard, MCP or CI, plus a Terraform and OpenTofu provider. Experimental, behind a flagSource for Levelrail, Declarative apply of the whole platform Partly config/deploy.yml declares app, roles, proxy, accessories and servers and kamal setup/deploy applies it; commands run per deploy, no state reconciliation or drift detection documentedSource for Kamal, Declarative apply of the whole platform
Functions and one-off jobs Partly Node, Python or Go handlers that sleep when idle and wake on the first request; scheduled and background calls with retriesSource for Levelrail, Functions and one-off jobs Partly A role can run a custom cmd such as bin/jobs for a job server; scheduled jobs are not describedSource for Kamal, 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 editionSource for Levelrail, IAM, audit log and 2FA in the free edition Partly Per-server audit log (.kamal/app-audit.log) of deploy steps, last 50 lines via kamal audit; no users, roles or 2FASource for Kamal, IAM, audit log and 2FA in the free edition
SAML or SCIM single sign-on Partlybeta 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 EntraSource for Levelrail, SAML or SCIM single sign-on Not applicable
Audit log of every action Yes Every mutating request recorded; verifiable hash chain, CSV or NDJSON export, retention, streaming to a webhook or S3 bucketSource for Levelrail, Audit log of every action Partly Per-server .kamal/app-audit.log of deploy steps, read with kamal audit; entries carry a user tag but the page does not say which person; hooks expose KAMAL_PERFORMER for custom reportsSource for Kamal, 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 DiscordSource for Levelrail, Two-person deploy approvals Not stated in their docs
  • Kamal is ahead on this row
  • Levelrail is ahead on this row

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

Migrating from Kamal

No importer for Kamal. Point Levelrail at the same images and recreate configuration.

Questions about Levelrail and Kamal

Is Levelrail a good alternative to Kamal?

Deliberately minimal: no control plane, database or agent, running over SSH from your machine or CI. How Levelrail differs: Desired state lives in a database, with a reconciler recording a status reason after every pass. Agents dial out, so CI uses a scoped API token instead of holding SSH keys. Adds a dashboard, deploy history, rollback and built-in observability, and is heavier by design. Choose Kamal instead when you want the fewest possible moving parts and do not need a dashboard. Levelrail has a shorter track record, so check the comparison for what it does not do yet.

When should I choose Kamal instead of Levelrail?

Choose Kamal when you want the fewest possible moving parts and do not need a dashboard.

Can I move from Kamal to Levelrail?

No importer for Kamal. Point Levelrail at the same images and recreate configuration.

Is Levelrail ready to replace Kamal in production?

Formats can change: APIs, the app spec and the on-disk layout can change between releases. A single node is stable; multi-node is in beta and the WireGuard mesh is not battle-tested. Check the feature status page before moving anything you cannot afford to lose, and keep Kamal running alongside until you trust the result.

Other comparisons

Try it next to Kamal

One command installs the control plane. Apache 2.0, no license key. Levelrail has a shorter track record, so run it beside your current setup first.

curl -fsSL https://levelrail.com/install.sh | sudo sh