Compare

An honest comparison, losses included.

This page compares architecture and feature breadth, not maturity. Levelrail is pre-release and most feature areas are labelled beta. It is positioning, not a ranking: any of these may be the right choice for you.

9 alternatives, 28 capabilities, as of 2026-10

Nine alternatives, 28 rows.

Only what each project's own documentation states. A question mark means their docs do not say, not that the answer is no. Point at a cell for its note and source, or switch on Notes. A question mark is a gap in their docs, listed once per row.

  • Yes
  • Partly
  • No
  • Not applicable
  • Not stated in their docs
Capability Levelrail Self-hosted Coolify Coolify Self-hosted Dokploy Self-hosted CapRover CapRover Self-hosted Dokku Self-hosted Kamal Self-hosted Vercel Hosted Heroku Hosted Railway Hosted Cloud Run Hosted
Documented answersyes, partly, no, unstated 17 / 11 / 0 / 0 17 yes, 11 partly, 0 no, 0 not stated, of 28 14 / 9 / 3 / 2 14 yes, 9 partly, 3 no, 2 not stated, of 28 13 / 6 / 2 / 7 13 yes, 6 partly, 2 no, 7 not stated, of 28 9 / 8 / 2 / 9 9 yes, 8 partly, 2 no, 9 not stated, of 28 4 / 12 / 4 / 7 4 yes, 12 partly, 4 no, 7 not stated, of 27 4 / 8 / 3 / 10 4 yes, 8 partly, 3 no, 10 not stated, of 25 9 / 9 / 1 / 3 9 yes, 9 partly, 1 no, 3 not stated, of 22 6 / 13 / 0 / 4 6 yes, 13 partly, 0 no, 4 not stated, of 23 11 / 10 / 1 / 1 11 yes, 10 partly, 1 no, 1 not stated, of 23 8 / 11 / 0 / 4 8 yes, 11 partly, 0 no, 4 not stated, of 23
Architecture
Yes. Agents dial out over mTLS; no inbound ports No. SSH from the control plane to each server No. Connects to remote servers over SSH keys No. Nodes join over SSH from the leader server No. Commands run on the host, over SSH or git push No. SSH from your machine or CI to each server Not applicable. Not applicable. Not applicable. Not applicable.

No answer in their docs or not applicable: Vercel, Heroku, Railway, Cloud Run.

Yes. Desired state converged, status condition with reason per pass Not stated in their docs. Not stated in their docs. Not stated in their docs. No. Event-driven trigger pipeline; no reconcile loop described No. None: it runs Docker commands per deploy Not applicable. Not applicable. Not applicable. Not applicable.

No answer in their docs or not applicable: Coolify, Dokploy, CapRover, Vercel, Heroku, Railway, Cloud Run.

Yes. One control plane binary, plus one agent per extra node No. Three base containers: app, PostgreSQL and Redis No. Three parts: Next.js app, PostgreSQL and Traefik Not stated in their docs. Not applicable. Not applicable. Not applicable. Not applicable. Not applicable. Not applicable.

No answer in their docs or not applicable: CapRover, Dokku, Kamal, Vercel, Heroku, Railway, Cloud Run.

Observability
Yes. Node-local metrics at 15s and full-text log search Partly. Historical metrics and traffic analytics; no built-in log search Partly. Monitoring features in the dashboard; log search not stated Partly. CPU, memory, network graphs; no log search documented No. Add your own stack No. Bring your own Partly. Logs and metrics on all plans; higher limits on Pro, Enterprise Partly. Dyno metrics and events shown; log search not documented Yes. Dashboard CPU, memory, network, disk metrics; log search Yes. Automatic Cloud Monitoring metrics; logs in Cloud Logging
Yes. Crashloop detection surfaces the last log lines Not stated in their docs. Not stated in their docs. Not stated in their docs. Partly. Restart policy restarts failing containers; no crashloop detection Not stated in their docs. Not stated in their docs. Partly. Error codes explain crashes in logs; no automatic diagnosis documented Partly. Auto restarts up to 10 times on free plans Partly. Troubleshooting guide; logs checked manually, no automatic crashloop view

No answer in their docs or not applicable: Coolify, Dokploy, CapRover, Kamal, Vercel.

Deploys
Yes. Prior images pinned so cleanup cannot remove them Yes. Redeploys a retained older image; retention is configurable Yes. Registry-based rollback to any previous deployment image Yes. One-click rollback restores image, not env vars Partly. Restores last good deploy when a deploy fails; no manual rollback Partly. Rollback to chosen version; old containers pruned after 3 days Partly. Instant rollback stated; image pinning not stated Yes. heroku rollback creates a release reusing the earlier slug or image Partly. Dashboard rollback to prior image; images kept 24 to 360 hours Yes. Traffic rolls back to a previous revision immediately
Yes. Cutover only after the readiness probe passes Partly. Starts replacement first; docs say no zero-downtime guarantee Partly. Swarm rolling updates; readiness gating not stated Yes. Health-gated start-first deploys; persistent apps have downtime Yes. New containers start, proxy switches, old retired after delay Yes. Zero-downtime cutover with kamal-proxy Not stated in their docs. Partly. Preboot is opt-in, standard and performance dynos; not guaranteed Partly. Healthcheck gates cutover; volume services see brief downtime Partly. Gradual rollouts and traffic splits; health gating of cutover not stated

No answer in their docs or not applicable: Vercel.

Yes. Stable on GitHub, beta on GitLab and Bitbucket Yes. Per pull request previews; full UI needs a GitHub App Partly. Preview per pull request, documented for GitHub only Not stated in their docs. Not stated in their docs. Not stated in their docs. Yes. Previews listed under deploys Yes. Review apps per GitHub pull request; GitHub only Yes. Environments per PR Partly. Revision tags give separate URLs without traffic; no PR previews

No answer in their docs or not applicable: CapRover, Dokku, Kamal.

Partly. Pre-built images from the dashboard; git deploys can build Yes. Deploys docker-compose.yml from a git repository or pasted file Yes. Compose deploys from Git or pasted file; build unsupported in Stack mode Partly. Subset of Compose from dashboard; build and networks ignored Not stated in their docs. Not stated in their docs. No. Compose file is not read; translate it manually to vercel.json Not stated in their docs. Partly. Imports Compose services; docker-compose.yml not run directly Partly. Compose file deploys as one multi container service; alpha or preview

No answer in their docs or not applicable: Dokku, Kamal, Heroku.

Partly. All four documented; GitLab and Bitbucket previews are beta, synthetic-webhook tested Yes. Push webhooks for GitHub, GitLab and Bitbucket sources Yes. Auto deploy on push for GitHub, GitLab, Bitbucket and Gitea Partly. Webhooks documented for GitHub and Bitbucket; GitLab via CI job Partly. git push to deploy branch; git:sync from any cloneable repo; no webhook Not stated in their docs. Yes. Auto deploys on push from GitHub, GitLab and Bitbucket Partly. GitHub automatic deploys; no first-party GitLab or Bitbucket integration Partly. Autodeploy from GitHub only; GitLab and Bitbucket not documented Yes. Developer Connect covers GitHub, GitLab, Bitbucket; Cloud Build covers GitHub

No answer in their docs or not applicable: Kamal.

Partly. Railpack detects Node, Python, Go and more; Ruby is rejected Yes. Nixpacks and Railpack detect and build without a Dockerfile Yes. Nixpacks is the default; Railpack and buildpacks also offered Partly. Explicit templates only: node, php, python-django, ruby-rack Partly. Heroku buildpacks by default; pack and Railpack need config files Partly. Dockerfile required by default; buildpacks only when configured explicitly Yes. Framework auto-detection builds with no Dockerfile needed Yes. Buildpacks auto-detect language and build source with no Dockerfile Yes. Railpack detects stack without Dockerfile; Dockerfile takes priority Yes. Google Cloud buildpacks detect the language; no Dockerfile needed
Yes. Per-app cron jobs with run history, logs, retries and alerts Yes. Scheduled tasks run commands in containers on cron schedules Yes. Schedule Jobs runs cron jobs in apps, compose services or servers Not stated in their docs. Yes. Scheduled dokku run tasks via cron:set and app.json Not stated in their docs. Yes. Cron jobs on all plans, UTC schedules, run Vercel Functions Partly. Heroku Scheduler add-on; jobs billed as one-off dyno hours Yes. Cron schedule per service; runs at least 5 minutes apart, UTC Partly. Scheduled job runs need Cloud Scheduler calling the job endpoint

No answer in their docs or not applicable: CapRover, Kamal.

Data
Partly. Many engines, scheduled S3 backups; Postgres restores tested live Yes. Scheduled backups to S3-compatible storage for six database engines Yes. Creates MySQL, Postgres, MongoDB, Redis, MariaDB; scheduled backups Partly. One-click databases; backups manual, no schedule, no S3 Partly. Official plugins create databases; backups manual export, no scheduling Partly. Accessories run containers such as MySQL; no backups documented Partly. Marketplace databases from the dashboard; backup schedules not stated Partly. Postgres scheduled backups on paid plans; no S3 export documented Partly. Scheduled volume and Postgres PITR backups; S3 export needs own job Not stated in their docs.

No answer in their docs or not applicable: Cloud Run.

Yes. Envelope-encrypted, masked in UI, injected at container create Partly. External secret managers documented; env var encryption not stated Partly. External secrets providers fetch values at deploy time; encryption not stated Not stated in their docs. Not stated in their docs. Partly. Secrets from files or password managers; host env file, no encryption documented Yes. Encrypted at rest; Secret type values are write-only after saving Not stated in their docs. Yes. Variables encrypted at rest; sealed values write-only Yes. Secret Manager values injected as env vars or mounted volumes

No answer in their docs or not applicable: CapRover, Dokku, Heroku.

Networking
Partly. Named networks and allow rules; cross-server mesh unverified on real hosts Partly. Shared Docker networks on one server; cross-server networking not documented Not stated in their docs. Yes. Apps reach each other by service name across cluster Partly. Docker networks on one host only; no cross-host networking Partly. Containers share a custom Docker network per host, no cross server networking Partly. Secure Compute private networks and VPC peering, Enterprise only Partly. Private Spaces, Teams or Enterprise only: internal routing and DNS Yes. WireGuard private DNS per environment, service.railway.internal Partly. Direct VPC egress reaches private IPs; internal DNS not documented

No answer in their docs or not applicable: Dokploy.

Partly. Experimental and flag gated; not tried across real hosts Partly. Traffic balancing needs an external cloud load balancer, set up manually Yes. Swarm replicas across servers; Traefik load-balances traffic to them Yes. Requests spread automatically across app instances Partly. Nginx round-robin across scaled web containers; other processes need config Not stated in their docs. Not applicable. Yes. Router randomly balances requests across web dynos Yes. Traffic spread across replicas and regions; no sticky sessions Yes. Requests balanced across regional instances automatically; multi region needs load balancer

No answer in their docs or not applicable: Kamal, Vercel.

Yes. Ordered rules, IP bans, bot handling, challenges and rate limits Partly. Rate limits via custom Traefik middleware; no bot protection Not stated in their docs. Not stated in their docs. Not stated in their docs. Not stated in their docs. Partly. Rule counts and rate limit options vary by plan Not stated in their docs. Partly. Under Attack Mode only; no rate limits or custom rules Partly. Cloud Armor filters traffic only through an external load balancer

No answer in their docs or not applicable: Dokploy, CapRover, Dokku, Kamal, Heroku.

Partly. Internal issuer by default; public ACME verified once live Yes. Traefik or Caddy requests and renews certificates for https domains Yes. Per-domain HTTPS with a Let's Encrypt certificate resolver option Yes. Let's Encrypt certificates managed automatically by CapRover Partly. Let's Encrypt via official plugin; manual certs otherwise Partly. kamal-proxy Let's Encrypt HTTPS, only with one server and host set Yes. Let's Encrypt certs issued and renewed automatically per domain Yes. Automated Certificate Management: free Let's Encrypt certs for custom domains Yes. Let's Encrypt certificates for custom domains, renewed automatically Partly. Managed certificates on custom domain mappings, which are in Preview
Platform
Partly. Enrollment verified locally; WireGuard mesh still unverified Yes. Manages each server over SSH Yes. Multi-node scheduling through Docker Swarm Yes. Join nodes via UI or docker swarm join over SSH Partly. One host by default; other schedulers exist Yes. SSH to each server Not applicable. Not applicable. Not applicable. Not applicable.

No answer in their docs or not applicable: Vercel, Heroku, Railway, Cloud Run.

Yes. 358 templates; a sample is live-deployed in e2e Yes. Large catalog of one-click services Yes. 568 or more one-click open source templates Yes. One-click app store Not stated in their docs. Not stated in their docs. Partly. Framework starter templates listed; no service template catalog stated Partly. app.json and Deploy button; no one-click service catalog Yes. Template marketplace with one-click deploys Not stated in their docs.

No answer in their docs or not applicable: Dokku, Kamal, Cloud Run.

Partly. Beta: CPU, memory or request-rate scaling with cooldowns and reasons No. Scaling is manual; operators decide when to add servers Not stated in their docs. No. Replica count is set by hand in the dashboard No. Scaling is manual via ps:scale; no autoscaling Not stated in their docs. Yes. Fluid compute scales instances automatically with traffic Partly. Web dynos only, on Performance, Private or Shield tiers, by p95 No. No native replica autoscaling; custom script via API Yes. Scales instances on request volume, with configurable maximums

No answer in their docs or not applicable: Dokploy, Kamal.

Yes. CLI and REST API documented; MCP server is beta Partly. CLI and API exist; docs do not confirm full dashboard parity Partly. HTTP API and a CLI; CLI covers app create, deploy, stop, delete Partly. CLI covers deploy, login, list; API documented only for login Partly. CLI over SSH; JSON API only in paid Dokku Pro Not applicable. Yes. CLI covers deploy, logs, env, promote; REST API also available Partly. CLI and Platform API for apps and config; full parity not stated Partly. Public GraphQL API and CLI; dashboard parity not stated Yes. gcloud CLI and Admin API manage services and jobs

No answer in their docs or not applicable: Kamal.

Partly. 18 channel kinds in beta, tested only against mocks Yes. Email, Discord, Telegram, Slack, Pushover and webhook channels Yes. Slack, Discord, Email, Telegram, Teams and Webhook notifications Partly. Build status notifications are Pro only; channels not named Partly. Deploy webhook via community plugin; no built-in notifications Partly. Hooks run custom scripts; no built-in Slack, Discord or email Partly. Email, dashboard and push alerts; Slack or Discord not stated Partly. Slack via ChatOps or add-ons; HTTP webhooks; no deploy email Yes. Slack and Discord webhooks; email via account notifications Partly. Cloud Monitoring alerts to email, Slack, webhooks, Pub/Sub
Yes. MCP server: 145 read-only tools, 186 in full mode Yes. MCP server over Streamable HTTP with team-scoped tokens Not stated in their docs. Not stated in their docs. Not stated in their docs. Not stated in their docs. Yes. Official remote Vercel MCP server at mcp.vercel.com, OAuth Yes. Remote MCP server at mcp.heroku.com with OAuth login Yes. Official hosted MCP server at mcp.railway.com Partly. Managed remote MCP server deploys and inspects services

No answer in their docs or not applicable: Dokploy, CapRover, Dokku, Kamal.

Yes. Runs on Linux servers you provide Yes. Web application on your server Yes. Web application on your server Yes. Web application running as a Swarm service Yes. Scripts running on your own host Yes. Runs against servers you own over SSH Not applicable. Not applicable. Not applicable. Not applicable.

No answer in their docs or not applicable: Vercel, Heroku, Railway, Cloud Run.

Yes. Apache 2.0, one edition, no paid tier Yes. Listed as open source Not stated in their docs. Yes. Listed as open source Yes. Permissive MIT-style license per repo LICENSE file Yes. Released under the MIT License Not stated in their docs. Not stated in their docs. Not stated in their docs. Not stated in their docs.

No answer in their docs or not applicable: Dokploy, Vercel, Heroku, Railway, Cloud Run.

Security
Yes. Allow/Deny policies, audit log and TOTP in one edition Partly. Roles, audit log and 2FA documented; editions not described Partly. Owner, Admin, Member roles and 2FA; audit logs are Enterprise Partly. 2FA is Pro only; no roles or audit log documented Partly. SSH key users; admin keyword grants key management; no RBAC Partly. Audit log of commands per server; no users, roles or 2FA Partly. Team roles on Pro; project-level roles on Enterprise only Partly. Four team roles and mandatory MFA; audit trails Enterprise only Partly. Audit logs kept 48 hours on free plans; longer on paid Partly. Cloud IAM and audit logs; 2FA is not a Cloud Run feature
Partly. SAML and SCIM are experimental and off by default Partly. OpenID Connect sign-in documented; SAML and SCIM not mentioned Yes. SAML and OIDC SSO plus SCIM, under the Enterprise license Not stated in their docs. Not stated in their docs. Not applicable. Partly. SAML SSO on Pro add-on; Directory Sync provisioning on Enterprise Partly. SAML 2.0 SSO for Teams and Enterprise; SCIM not documented Partly. SAML SSO on Enterprise; SCIM not documented Not stated in their docs.

No answer in their docs or not applicable: CapRover, Dokku, Kamal, Cloud Run.

Pick a project to see it next to Levelrail, row by row.

Architecture

No SSH: agents dial out

Levelrail Yes. Agents dial out over mTLS; no inbound ports Source for Levelrail, No SSH: agents dial out

Coolify No. SSH from the control plane to each server Source for Coolify, No SSH: agents dial out

Level-triggered reconciler with status reasons

Levelrail Yes. Desired state converged, status condition with reason per pass Source for Levelrail, Level-triggered reconciler with status reasons

Coolify Not stated in their docs

Single control plane binary

Levelrail Yes. One control plane binary, plus one agent per extra node Source for Levelrail, Single control plane binary

Coolify No. Three base containers: app, PostgreSQL and Redis Source for Coolify, Single control plane binary

Observability

Metrics and log search built in

Levelrail Yes. Node-local metrics at 15s and full-text log search Source for Levelrail, Metrics and log search built in

Coolify Partly. Historical metrics and traffic analytics; no built-in log search Source for Coolify, Metrics and log search built in

Crashloop diagnosis with last log lines

Levelrail Yes. Crashloop detection surfaces the last log lines Source for Levelrail, Crashloop diagnosis with last log lines

Coolify Not stated in their docs

Deploys

One-click rollback with pinned images

Levelrail Yes. Prior images pinned so cleanup cannot remove them Source for Levelrail, One-click rollback with pinned images

Coolify Yes. Redeploys a retained older image; retention is configurable Source for Coolify, One-click rollback with pinned images

Readiness-gated zero-downtime deploys

Levelrail Yes. Cutover only after the readiness probe passes Source for Levelrail, Readiness-gated zero-downtime deploys

Coolify Partly. Starts replacement first; docs say no zero-downtime guarantee Source for Coolify, Readiness-gated zero-downtime deploys

Preview environments per pull request

Levelrail Yes. Stable on GitHub, beta on GitLab and Bitbucket Source for Levelrail, Preview environments per pull request

Coolify Yes. Per pull request previews; full UI needs a GitHub App Source for Coolify, Preview environments per pull request

Docker Compose apps

Levelrail Partly. Pre-built images from the dashboard; git deploys can build Source for Levelrail, Docker Compose apps

Coolify 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

Levelrail Partly. All four documented; GitLab and Bitbucket previews are beta, synthetic-webhook tested Source for Levelrail, Git push deploys from GitHub, GitLab, Bitbucket

Coolify 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

Levelrail Partly. Railpack detects Node, Python, Go and more; Ruby is rejected Source for Levelrail, Builds from source without a Dockerfile

Coolify Yes. Nixpacks and Railpack detect and build without a Dockerfile Source for Coolify, Builds from source without a Dockerfile

Scheduled jobs

Levelrail Yes. Per-app cron jobs with run history, logs, retries and alerts Source for Levelrail, Scheduled jobs

Coolify Yes. Scheduled tasks run commands in containers on cron schedules Source for Coolify, Scheduled jobs

Data

Managed databases with scheduled backups

Levelrail Partly. Many engines, scheduled S3 backups; Postgres restores tested live Source for Levelrail, Managed databases with scheduled backups

Coolify Yes. Scheduled backups to S3-compatible storage for six database engines Source for Coolify, Managed databases with scheduled backups

Encrypted secrets for env vars

Levelrail Yes. Envelope-encrypted, masked in UI, injected at container create Source for Levelrail, Encrypted secrets for env vars

Coolify Partly. External secret managers documented; env var encryption not stated Source for Coolify, Encrypted secrets for env vars

Networking

Private networking between apps or nodes

Levelrail Partly. Named networks and allow rules; cross-server mesh unverified on real hosts Source for Levelrail, Private networking between apps or nodes

Coolify 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

Levelrail Partly. Experimental and flag gated; not tried across real hosts Source for Levelrail, Load balancing across replicas

Coolify 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 Yes. Ordered rules, IP bans, bot handling, challenges and rate limits Source for Levelrail, Request firewall, rate limits, bot protection

Coolify Partly. Rate limits via custom Traefik middleware; no bot protection Source for Coolify, Request firewall, rate limits, bot protection

Automatic TLS certificates

Levelrail Partly. Internal issuer by default; public ACME verified once live Source for Levelrail, Automatic TLS certificates

Coolify Yes. Traefik or Caddy requests and renews certificates for https domains Source for Coolify, Automatic TLS certificates

Platform

Multi-node

Levelrail Partly. Enrollment verified locally; WireGuard mesh still unverified Source for Levelrail, Multi-node

Coolify Yes. Manages each server over SSH Source for Coolify, Multi-node

One-click service templates

Levelrail Yes. 358 templates; a sample is live-deployed in e2e Source for Levelrail, One-click service templates

Coolify Yes. Large catalog of one-click services Source for Coolify, One-click service templates

Autoscaling

Levelrail Partly. Beta: CPU, memory or request-rate scaling with cooldowns and reasons Source for Levelrail, Autoscaling

Coolify No. Scaling is manual; operators decide when to add servers Source for Coolify, Autoscaling

CLI and HTTP API

Levelrail Yes. CLI and REST API documented; MCP server is beta Source for Levelrail, CLI and HTTP API

Coolify Partly. CLI and API exist; docs do not confirm full dashboard parity Source for Coolify, CLI and HTTP API

Deploy and alert notifications

Levelrail Partly. 18 channel kinds in beta, tested only against mocks Source for Levelrail, Deploy and alert notifications

Coolify Yes. Email, Discord, Telegram, Slack, Pushover and webhook channels Source for Coolify, Deploy and alert notifications

MCP / AI assistant integration

Levelrail Yes. MCP server: 145 read-only tools, 186 in full mode Source for Levelrail, MCP / AI assistant integration

Coolify Yes. MCP server over Streamable HTTP with team-scoped tokens Source for Coolify, MCP / AI assistant integration

Runs on servers you own

Levelrail Yes. Runs on Linux servers you provide Source for Levelrail, Runs on servers you own

Coolify Yes. Web application on your server Source for Coolify, Runs on servers you own

Open source license

Levelrail Yes. Apache 2.0, one edition, no paid tier Source for Levelrail, Open source license

Coolify Yes. Listed as open source Source for Coolify, Open source license

Security

IAM, audit log and 2FA in the free edition

Levelrail Yes. Allow/Deny policies, audit log and TOTP in one edition Source for Levelrail, IAM, audit log and 2FA in the free edition

Coolify Partly. Roles, audit log and 2FA documented; editions not described Source for Coolify, IAM, audit log and 2FA in the free edition

SAML or SCIM single sign-on

Levelrail Partly. SAML and SCIM are experimental and off by default Source for Levelrail, SAML or SCIM single sign-on

Coolify Partly. OpenID Connect sign-in documented; SAML and SCIM not mentioned Source for Coolify, SAML or SCIM single sign-on

Architecture

No SSH: agents dial out

Levelrail Yes. Agents dial out over mTLS; no inbound ports Source for Levelrail, No SSH: agents dial out

Dokploy No. Connects to remote servers over SSH keys Source for Dokploy, No SSH: agents dial out

Level-triggered reconciler with status reasons

Levelrail Yes. Desired state converged, status condition with reason per pass Source for Levelrail, Level-triggered reconciler with status reasons

Dokploy Not stated in their docs

Single control plane binary

Levelrail Yes. One control plane binary, plus one agent per extra node Source for Levelrail, Single control plane binary

Dokploy No. Three parts: Next.js app, PostgreSQL and Traefik Source for Dokploy, Single control plane binary

Observability

Metrics and log search built in

Levelrail Yes. Node-local metrics at 15s and full-text log search Source for Levelrail, Metrics and log search built in

Dokploy Partly. Monitoring features in the dashboard; log search not stated Source for Dokploy, Metrics and log search built in

Crashloop diagnosis with last log lines

Levelrail Yes. Crashloop detection surfaces the last log lines Source for Levelrail, Crashloop diagnosis with last log lines

Dokploy Not stated in their docs

Deploys

One-click rollback with pinned images

Levelrail Yes. Prior images pinned so cleanup cannot remove them Source for Levelrail, One-click rollback with pinned images

Dokploy Yes. Registry-based rollback to any previous deployment image Source for Dokploy, One-click rollback with pinned images

Readiness-gated zero-downtime deploys

Levelrail Yes. Cutover only after the readiness probe passes Source for Levelrail, Readiness-gated zero-downtime deploys

Dokploy Partly. Swarm rolling updates; readiness gating not stated Source for Dokploy, Readiness-gated zero-downtime deploys

Preview environments per pull request

Levelrail Yes. Stable on GitHub, beta on GitLab and Bitbucket Source for Levelrail, Preview environments per pull request

Dokploy Partly. Preview per pull request, documented for GitHub only Source for Dokploy, Preview environments per pull request

Docker Compose apps

Levelrail Partly. Pre-built images from the dashboard; git deploys can build Source for Levelrail, Docker Compose apps

Dokploy 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

Levelrail Partly. All four documented; GitLab and Bitbucket previews are beta, synthetic-webhook tested Source for Levelrail, Git push deploys from GitHub, GitLab, Bitbucket

Dokploy 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

Levelrail Partly. Railpack detects Node, Python, Go and more; Ruby is rejected Source for Levelrail, Builds from source without a Dockerfile

Dokploy Yes. Nixpacks is the default; Railpack and buildpacks also offered Source for Dokploy, Builds from source without a Dockerfile

Scheduled jobs

Levelrail Yes. Per-app cron jobs with run history, logs, retries and alerts Source for Levelrail, Scheduled jobs

Dokploy Yes. Schedule Jobs runs cron jobs in apps, compose services or servers Source for Dokploy, Scheduled jobs

Data

Managed databases with scheduled backups

Levelrail Partly. Many engines, scheduled S3 backups; Postgres restores tested live Source for Levelrail, Managed databases with scheduled backups

Dokploy Yes. Creates MySQL, Postgres, MongoDB, Redis, MariaDB; scheduled backups Source for Dokploy, Managed databases with scheduled backups

Encrypted secrets for env vars

Levelrail Yes. Envelope-encrypted, masked in UI, injected at container create Source for Levelrail, Encrypted secrets for env vars

Dokploy Partly. External secrets providers fetch values at deploy time; encryption not stated Source for Dokploy, Encrypted secrets for env vars

Networking

Private networking between apps or nodes

Levelrail Partly. Named networks and allow rules; cross-server mesh unverified on real hosts Source for Levelrail, Private networking between apps or nodes

Dokploy Not stated in their docs

Load balancing across replicas

Levelrail Partly. Experimental and flag gated; not tried across real hosts Source for Levelrail, Load balancing across replicas

Dokploy Yes. Swarm replicas across servers; Traefik load-balances traffic to them Source for Dokploy, Load balancing across replicas

Request firewall, rate limits, bot protection

Levelrail Yes. Ordered rules, IP bans, bot handling, challenges and rate limits Source for Levelrail, Request firewall, rate limits, bot protection

Dokploy Not stated in their docs

Automatic TLS certificates

Levelrail Partly. Internal issuer by default; public ACME verified once live Source for Levelrail, Automatic TLS certificates

Dokploy Yes. Per-domain HTTPS with a Let's Encrypt certificate resolver option Source for Dokploy, Automatic TLS certificates

Platform

Multi-node

Levelrail Partly. Enrollment verified locally; WireGuard mesh still unverified Source for Levelrail, Multi-node

Dokploy Yes. Multi-node scheduling through Docker Swarm Source for Dokploy, Multi-node

One-click service templates

Levelrail Yes. 358 templates; a sample is live-deployed in e2e Source for Levelrail, One-click service templates

Dokploy Yes. 568 or more one-click open source templates Source for Dokploy, One-click service templates

Autoscaling

Levelrail Partly. Beta: CPU, memory or request-rate scaling with cooldowns and reasons Source for Levelrail, Autoscaling

Dokploy Not stated in their docs

CLI and HTTP API

Levelrail Yes. CLI and REST API documented; MCP server is beta Source for Levelrail, CLI and HTTP API

Dokploy Partly. HTTP API and a CLI; CLI covers app create, deploy, stop, delete Source for Dokploy, CLI and HTTP API

Deploy and alert notifications

Levelrail Partly. 18 channel kinds in beta, tested only against mocks Source for Levelrail, Deploy and alert notifications

Dokploy Yes. Slack, Discord, Email, Telegram, Teams and Webhook notifications Source for Dokploy, Deploy and alert notifications

MCP / AI assistant integration

Levelrail Yes. MCP server: 145 read-only tools, 186 in full mode Source for Levelrail, MCP / AI assistant integration

Dokploy Not stated in their docs

Runs on servers you own

Levelrail Yes. Runs on Linux servers you provide Source for Levelrail, Runs on servers you own

Dokploy Yes. Web application on your server Source for Dokploy, Runs on servers you own

Open source license

Levelrail Yes. Apache 2.0, one edition, no paid tier Source for Levelrail, Open source license

Dokploy Not stated in their docs

Security

IAM, audit log and 2FA in the free edition

Levelrail Yes. Allow/Deny policies, audit log and TOTP in one edition Source for Levelrail, IAM, audit log and 2FA in the free edition

Dokploy Partly. Owner, Admin, Member roles and 2FA; audit logs are Enterprise Source for Dokploy, IAM, audit log and 2FA in the free edition

SAML or SCIM single sign-on

Levelrail Partly. SAML and SCIM are experimental and off by default Source for Levelrail, SAML or SCIM single sign-on

Dokploy Yes. SAML and OIDC SSO plus SCIM, under the Enterprise license Source for Dokploy, SAML or SCIM single sign-on

Architecture

No SSH: agents dial out

Levelrail Yes. Agents dial out over mTLS; no inbound ports Source for Levelrail, No SSH: agents dial out

CapRover No. Nodes join over SSH from the leader server Source for CapRover, No SSH: agents dial out

Level-triggered reconciler with status reasons

Levelrail Yes. Desired state converged, status condition with reason per pass Source for Levelrail, Level-triggered reconciler with status reasons

CapRover Not stated in their docs

Single control plane binary

Levelrail Yes. One control plane binary, plus one agent per extra node Source for Levelrail, Single control plane binary

CapRover Not stated in their docs

Observability

Metrics and log search built in

Levelrail Yes. Node-local metrics at 15s and full-text log search Source for Levelrail, Metrics and log search built in

CapRover Partly. CPU, memory, network graphs; no log search documented Source for CapRover, Metrics and log search built in

Crashloop diagnosis with last log lines

Levelrail Yes. Crashloop detection surfaces the last log lines Source for Levelrail, Crashloop diagnosis with last log lines

CapRover Not stated in their docs

Deploys

One-click rollback with pinned images

Levelrail Yes. Prior images pinned so cleanup cannot remove them Source for Levelrail, One-click rollback with pinned images

CapRover Yes. One-click rollback restores image, not env vars Source for CapRover, One-click rollback with pinned images

Readiness-gated zero-downtime deploys

Levelrail Yes. Cutover only after the readiness probe passes Source for Levelrail, Readiness-gated zero-downtime deploys

CapRover Yes. Health-gated start-first deploys; persistent apps have downtime Source for CapRover, Readiness-gated zero-downtime deploys

Preview environments per pull request

Levelrail Yes. Stable on GitHub, beta on GitLab and Bitbucket Source for Levelrail, Preview environments per pull request

CapRover Not stated in their docs

Docker Compose apps

Levelrail Partly. Pre-built images from the dashboard; git deploys can build Source for Levelrail, Docker Compose apps

CapRover Partly. Subset of Compose from dashboard; build and networks ignored Source for CapRover, Docker Compose apps

Git push deploys from GitHub, GitLab, Bitbucket

Levelrail Partly. All four documented; GitLab and Bitbucket previews are beta, synthetic-webhook tested Source for Levelrail, Git push deploys from GitHub, GitLab, Bitbucket

CapRover Partly. Webhooks documented for GitHub and Bitbucket; GitLab via CI job Source for CapRover, Git push deploys from GitHub, GitLab, Bitbucket

Builds from source without a Dockerfile

Levelrail Partly. Railpack detects Node, Python, Go and more; Ruby is rejected Source for Levelrail, Builds from source without a Dockerfile

CapRover Partly. Explicit templates only: node, php, python-django, ruby-rack Source for CapRover, Builds from source without a Dockerfile

Scheduled jobs

Levelrail Yes. Per-app cron jobs with run history, logs, retries and alerts Source for Levelrail, Scheduled jobs

CapRover Not stated in their docs

Data

Managed databases with scheduled backups

Levelrail Partly. Many engines, scheduled S3 backups; Postgres restores tested live Source for Levelrail, Managed databases with scheduled backups

CapRover Partly. One-click databases; backups manual, no schedule, no S3 Source for CapRover, Managed databases with scheduled backups

Encrypted secrets for env vars

Levelrail Yes. Envelope-encrypted, masked in UI, injected at container create Source for Levelrail, Encrypted secrets for env vars

CapRover Not stated in their docs

Networking

Private networking between apps or nodes

Levelrail Partly. Named networks and allow rules; cross-server mesh unverified on real hosts Source for Levelrail, Private networking between apps or nodes

CapRover Yes. Apps reach each other by service name across cluster Source for CapRover, Private networking between apps or nodes

Load balancing across replicas

Levelrail Partly. Experimental and flag gated; not tried across real hosts Source for Levelrail, Load balancing across replicas

CapRover Yes. Requests spread automatically across app instances Source for CapRover, Load balancing across replicas

Request firewall, rate limits, bot protection

Levelrail Yes. Ordered rules, IP bans, bot handling, challenges and rate limits Source for Levelrail, Request firewall, rate limits, bot protection

CapRover Not stated in their docs

Automatic TLS certificates

Levelrail Partly. Internal issuer by default; public ACME verified once live Source for Levelrail, Automatic TLS certificates

CapRover Yes. Let's Encrypt certificates managed automatically by CapRover Source for CapRover, Automatic TLS certificates

Platform

Multi-node

Levelrail Partly. Enrollment verified locally; WireGuard mesh still unverified Source for Levelrail, Multi-node

CapRover Yes. Join nodes via UI or docker swarm join over SSH Source for CapRover, Multi-node

One-click service templates

Levelrail Yes. 358 templates; a sample is live-deployed in e2e Source for Levelrail, One-click service templates

CapRover Yes. One-click app store Source for CapRover, One-click service templates

Autoscaling

Levelrail Partly. Beta: CPU, memory or request-rate scaling with cooldowns and reasons Source for Levelrail, Autoscaling

CapRover No. Replica count is set by hand in the dashboard Source for CapRover, Autoscaling

CLI and HTTP API

Levelrail Yes. CLI and REST API documented; MCP server is beta Source for Levelrail, CLI and HTTP API

CapRover Partly. CLI covers deploy, login, list; API documented only for login Source for CapRover, CLI and HTTP API

Deploy and alert notifications

Levelrail Partly. 18 channel kinds in beta, tested only against mocks Source for Levelrail, Deploy and alert notifications

CapRover Partly. Build status notifications are Pro only; channels not named Source for CapRover, Deploy and alert notifications

MCP / AI assistant integration

Levelrail Yes. MCP server: 145 read-only tools, 186 in full mode Source for Levelrail, MCP / AI assistant integration

CapRover Not stated in their docs

Runs on servers you own

Levelrail Yes. Runs on Linux servers you provide Source for Levelrail, Runs on servers you own

CapRover Yes. Web application running as a Swarm service Source for CapRover, Runs on servers you own

Open source license

Levelrail Yes. Apache 2.0, one edition, no paid tier Source for Levelrail, Open source license

CapRover Yes. Listed as open source Source for CapRover, Open source license

Security

IAM, audit log and 2FA in the free edition

Levelrail Yes. Allow/Deny policies, audit log and TOTP in one edition Source for Levelrail, IAM, audit log and 2FA in the free edition

CapRover Partly. 2FA is Pro only; no roles or audit log documented Source for CapRover, IAM, audit log and 2FA in the free edition

SAML or SCIM single sign-on

Levelrail Partly. SAML and SCIM are experimental and off by default Source for Levelrail, SAML or SCIM single sign-on

CapRover Not stated in their docs

Architecture

No SSH: agents dial out

Levelrail Yes. Agents dial out over mTLS; no inbound ports Source for Levelrail, No SSH: agents dial out

Dokku 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 Yes. Desired state converged, status condition with reason per pass Source for Levelrail, Level-triggered reconciler with status reasons

Dokku No. Event-driven trigger pipeline; no reconcile loop described Source for Dokku, Level-triggered reconciler with status reasons

Single control plane binary

Levelrail Yes. One control plane binary, plus one agent per extra node Source for Levelrail, Single control plane binary

Dokku Not applicable

Observability

Metrics and log search built in

Levelrail Yes. Node-local metrics at 15s and full-text log search Source for Levelrail, Metrics and log search built in

Dokku No. Add your own stack Source for Dokku, Metrics and log search built in

Crashloop diagnosis with last log lines

Levelrail Yes. Crashloop detection surfaces the last log lines Source for Levelrail, Crashloop diagnosis with last log lines

Dokku Partly. Restart policy restarts failing containers; no crashloop detection Source for Dokku, Crashloop diagnosis with last log lines

Deploys

One-click rollback with pinned images

Levelrail Yes. Prior images pinned so cleanup cannot remove them Source for Levelrail, One-click rollback with pinned images

Dokku Partly. Restores last good deploy when a deploy fails; no manual rollback Source for Dokku, One-click rollback with pinned images

Readiness-gated zero-downtime deploys

Levelrail Yes. Cutover only after the readiness probe passes Source for Levelrail, Readiness-gated zero-downtime deploys

Dokku Yes. New containers start, proxy switches, old retired after delay Source for Dokku, Readiness-gated zero-downtime deploys

Preview environments per pull request

Levelrail Yes. Stable on GitHub, beta on GitLab and Bitbucket Source for Levelrail, Preview environments per pull request

Dokku Not stated in their docs

Docker Compose apps

Levelrail Partly. Pre-built images from the dashboard; git deploys can build Source for Levelrail, Docker Compose apps

Dokku Not stated in their docs

Git push deploys from GitHub, GitLab, Bitbucket

Levelrail Partly. All four documented; GitLab and Bitbucket previews are beta, synthetic-webhook tested Source for Levelrail, Git push deploys from GitHub, GitLab, Bitbucket

Dokku Partly. git push to deploy branch; git:sync from any cloneable repo; no webhook Source for Dokku, Git push deploys from GitHub, GitLab, Bitbucket

Builds from source without a Dockerfile

Levelrail Partly. Railpack detects Node, Python, Go and more; Ruby is rejected Source for Levelrail, Builds from source without a Dockerfile

Dokku Partly. Heroku buildpacks by default; pack and Railpack need config files Source for Dokku, Builds from source without a Dockerfile

Scheduled jobs

Levelrail Yes. Per-app cron jobs with run history, logs, retries and alerts Source for Levelrail, Scheduled jobs

Dokku Yes. Scheduled dokku run tasks via cron:set and app.json Source for Dokku, Scheduled jobs

Data

Managed databases with scheduled backups

Levelrail Partly. Many engines, scheduled S3 backups; Postgres restores tested live Source for Levelrail, Managed databases with scheduled backups

Dokku Partly. Official plugins create databases; backups manual export, no scheduling Source for Dokku, Managed databases with scheduled backups

Encrypted secrets for env vars

Levelrail Yes. Envelope-encrypted, masked in UI, injected at container create Source for Levelrail, Encrypted secrets for env vars

Dokku Not stated in their docs

Networking

Private networking between apps or nodes

Levelrail Partly. Named networks and allow rules; cross-server mesh unverified on real hosts Source for Levelrail, Private networking between apps or nodes

Dokku Partly. Docker networks on one host only; no cross-host networking Source for Dokku, Private networking between apps or nodes

Load balancing across replicas

Levelrail Partly. Experimental and flag gated; not tried across real hosts Source for Levelrail, Load balancing across replicas

Dokku 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

Levelrail Yes. Ordered rules, IP bans, bot handling, challenges and rate limits Source for Levelrail, Request firewall, rate limits, bot protection

Dokku Not stated in their docs

Automatic TLS certificates

Levelrail Partly. Internal issuer by default; public ACME verified once live Source for Levelrail, Automatic TLS certificates

Dokku Partly. Let's Encrypt via official plugin; manual certs otherwise Source for Dokku, Automatic TLS certificates

Platform

Multi-node

Levelrail Partly. Enrollment verified locally; WireGuard mesh still unverified Source for Levelrail, Multi-node

Dokku Partly. One host by default; other schedulers exist Source for Dokku, Multi-node

One-click service templates

Levelrail Yes. 358 templates; a sample is live-deployed in e2e Source for Levelrail, One-click service templates

Dokku Not stated in their docs

Autoscaling

Levelrail Partly. Beta: CPU, memory or request-rate scaling with cooldowns and reasons Source for Levelrail, Autoscaling

Dokku No. Scaling is manual via ps:scale; no autoscaling Source for Dokku, Autoscaling

CLI and HTTP API

Levelrail Yes. CLI and REST API documented; MCP server is beta Source for Levelrail, CLI and HTTP API

Dokku Partly. CLI over SSH; JSON API only in paid Dokku Pro Source for Dokku, CLI and HTTP API

Deploy and alert notifications

Levelrail Partly. 18 channel kinds in beta, tested only against mocks Source for Levelrail, Deploy and alert notifications

Dokku Partly. Deploy webhook via community plugin; no built-in notifications Source for Dokku, Deploy and alert notifications

MCP / AI assistant integration

Levelrail Yes. MCP server: 145 read-only tools, 186 in full mode Source for Levelrail, MCP / AI assistant integration

Dokku Not stated in their docs

Runs on servers you own

Levelrail Yes. Runs on Linux servers you provide Source for Levelrail, Runs on servers you own

Dokku Yes. Scripts running on your own host Source for Dokku, Runs on servers you own

Open source license

Levelrail Yes. Apache 2.0, one edition, no paid tier Source for Levelrail, Open source license

Dokku Yes. Permissive MIT-style license per repo LICENSE file Source for Dokku, Open source license

Security

IAM, audit log and 2FA in the free edition

Levelrail Yes. Allow/Deny policies, audit log and TOTP in one edition Source for Levelrail, IAM, audit log and 2FA in the free edition

Dokku 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

Levelrail Partly. SAML and SCIM are experimental and off by default Source for Levelrail, SAML or SCIM single sign-on

Dokku Not stated in their docs

Architecture

No SSH: agents dial out

Levelrail Yes. Agents dial out over mTLS; no inbound ports Source for Levelrail, No SSH: agents dial out

Kamal No. SSH from your machine or CI to each server Source for Kamal, No SSH: agents dial out

Level-triggered reconciler with status reasons

Levelrail Yes. Desired state converged, status condition with reason per pass Source for Levelrail, Level-triggered reconciler with status reasons

Kamal No. None: it runs Docker commands per deploy Source for Kamal, Level-triggered reconciler with status reasons

Single control plane binary

Levelrail Yes. One control plane binary, plus one agent per extra node Source for Levelrail, Single control plane binary

Kamal Not applicable

Observability

Metrics and log search built in

Levelrail Yes. Node-local metrics at 15s and full-text log search Source for Levelrail, Metrics and log search built in

Kamal No. Bring your own Source for Kamal, Metrics and log search built in

Crashloop diagnosis with last log lines

Levelrail Yes. Crashloop detection surfaces the last log lines Source for Levelrail, Crashloop diagnosis with last log lines

Kamal Not stated in their docs

Deploys

One-click rollback with pinned images

Levelrail Yes. Prior images pinned so cleanup cannot remove them Source for Levelrail, One-click rollback with pinned images

Kamal Partly. Rollback to chosen version; old containers pruned after 3 days Source for Kamal, One-click rollback with pinned images

Readiness-gated zero-downtime deploys

Levelrail Yes. Cutover only after the readiness probe passes Source for Levelrail, Readiness-gated zero-downtime deploys

Kamal Yes. Zero-downtime cutover with kamal-proxy Source for Kamal, Readiness-gated zero-downtime deploys

Preview environments per pull request

Levelrail Yes. Stable on GitHub, beta on GitLab and Bitbucket Source for Levelrail, Preview environments per pull request

Kamal Not stated in their docs

Docker Compose apps

Levelrail Partly. Pre-built images from the dashboard; git deploys can build Source for Levelrail, Docker Compose apps

Kamal Not stated in their docs

Git push deploys from GitHub, GitLab, Bitbucket

Levelrail Partly. All four documented; GitLab and Bitbucket previews are beta, synthetic-webhook tested Source for Levelrail, Git push deploys from GitHub, GitLab, Bitbucket

Kamal Not stated in their docs

Builds from source without a Dockerfile

Levelrail Partly. Railpack detects Node, Python, Go and more; Ruby is rejected Source for Levelrail, Builds from source without a Dockerfile

Kamal Partly. Dockerfile required by default; buildpacks only when configured explicitly Source for Kamal, Builds from source without a Dockerfile

Scheduled jobs

Levelrail Yes. Per-app cron jobs with run history, logs, retries and alerts Source for Levelrail, Scheduled jobs

Kamal Not stated in their docs

Data

Managed databases with scheduled backups

Levelrail Partly. Many engines, scheduled S3 backups; Postgres restores tested live Source for Levelrail, Managed databases with scheduled backups

Kamal Partly. Accessories run containers such as MySQL; no backups documented Source for Kamal, Managed databases with scheduled backups

Encrypted secrets for env vars

Levelrail Yes. Envelope-encrypted, masked in UI, injected at container create Source for Levelrail, Encrypted secrets for env vars

Kamal Partly. Secrets from files or password managers; host env file, no encryption documented Source for Kamal, Encrypted secrets for env vars

Networking

Private networking between apps or nodes

Levelrail Partly. Named networks and allow rules; cross-server mesh unverified on real hosts Source for Levelrail, Private networking between apps or nodes

Kamal Partly. Containers share a custom Docker network per host, no cross server networking Source for Kamal, Private networking between apps or nodes

Load balancing across replicas

Levelrail Partly. Experimental and flag gated; not tried across real hosts Source for Levelrail, Load balancing across replicas

Kamal Not stated in their docs

Request firewall, rate limits, bot protection

Levelrail Yes. Ordered rules, IP bans, bot handling, challenges and rate limits Source for Levelrail, Request firewall, rate limits, bot protection

Kamal Not stated in their docs

Automatic TLS certificates

Levelrail Partly. Internal issuer by default; public ACME verified once live Source for Levelrail, Automatic TLS certificates

Kamal Partly. kamal-proxy Let's Encrypt HTTPS, only with one server and host set Source for Kamal, Automatic TLS certificates

Platform

Multi-node

Levelrail Partly. Enrollment verified locally; WireGuard mesh still unverified Source for Levelrail, Multi-node

Kamal Yes. SSH to each server Source for Kamal, Multi-node

One-click service templates

Levelrail Yes. 358 templates; a sample is live-deployed in e2e Source for Levelrail, One-click service templates

Kamal Not stated in their docs

Autoscaling

Levelrail Partly. Beta: CPU, memory or request-rate scaling with cooldowns and reasons Source for Levelrail, Autoscaling

Kamal Not stated in their docs

CLI and HTTP API

Levelrail Yes. CLI and REST API documented; MCP server is beta Source for Levelrail, CLI and HTTP API

Kamal Not applicable

Deploy and alert notifications

Levelrail Partly. 18 channel kinds in beta, tested only against mocks Source for Levelrail, Deploy and alert notifications

Kamal Partly. Hooks run custom scripts; no built-in Slack, Discord or email Source for Kamal, Deploy and alert notifications

MCP / AI assistant integration

Levelrail Yes. MCP server: 145 read-only tools, 186 in full mode Source for Levelrail, MCP / AI assistant integration

Kamal Not stated in their docs

Runs on servers you own

Levelrail Yes. Runs on Linux servers you provide Source for Levelrail, Runs on servers you own

Kamal Yes. Runs against servers you own over SSH Source for Kamal, Runs on servers you own

Open source license

Levelrail Yes. Apache 2.0, one edition, no paid tier Source for Levelrail, Open source license

Kamal Yes. Released under the MIT License Source for Kamal, Open source license

Security

IAM, audit log and 2FA in the free edition

Levelrail Yes. Allow/Deny policies, audit log and TOTP in one edition Source for Levelrail, IAM, audit log and 2FA in the free edition

Kamal Partly. Audit log of commands per server; no users, roles or 2FA Source for Kamal, IAM, audit log and 2FA in the free edition

SAML or SCIM single sign-on

Levelrail Partly. SAML and SCIM are experimental and off by default Source for Levelrail, SAML or SCIM single sign-on

Kamal Not applicable

Architecture

No SSH: agents dial out

Levelrail Yes. Agents dial out over mTLS; no inbound ports Source for Levelrail, No SSH: agents dial out

Vercel Not applicable

Level-triggered reconciler with status reasons

Levelrail Yes. Desired state converged, status condition with reason per pass Source for Levelrail, Level-triggered reconciler with status reasons

Vercel Not applicable

Single control plane binary

Levelrail Yes. One control plane binary, plus one agent per extra node Source for Levelrail, Single control plane binary

Vercel Not applicable

Observability

Metrics and log search built in

Levelrail Yes. Node-local metrics at 15s and full-text log search Source for Levelrail, Metrics and log search built in

Vercel Partly. Logs and metrics on all plans; higher limits on Pro, Enterprise Source for Vercel, Metrics and log search built in

Crashloop diagnosis with last log lines

Levelrail Yes. Crashloop detection surfaces the last log lines Source for Levelrail, Crashloop diagnosis with last log lines

Vercel Not stated in their docs

Deploys

One-click rollback with pinned images

Levelrail Yes. Prior images pinned so cleanup cannot remove them Source for Levelrail, One-click rollback with pinned images

Vercel Partly. Instant rollback stated; image pinning not stated Source for Vercel, One-click rollback with pinned images

Readiness-gated zero-downtime deploys

Levelrail Yes. Cutover only after the readiness probe passes Source for Levelrail, Readiness-gated zero-downtime deploys

Vercel Not stated in their docs

Preview environments per pull request

Levelrail Yes. Stable on GitHub, beta on GitLab and Bitbucket Source for Levelrail, Preview environments per pull request

Vercel Yes. Previews listed under deploys Source for Vercel, Preview environments per pull request

Docker Compose apps

Levelrail Partly. Pre-built images from the dashboard; git deploys can build Source for Levelrail, Docker Compose apps

Vercel No. Compose file is not read; translate it manually to vercel.json Source for Vercel, Docker Compose apps

Git push deploys from GitHub, GitLab, Bitbucket

Levelrail Partly. All four documented; GitLab and Bitbucket previews are beta, synthetic-webhook tested Source for Levelrail, Git push deploys from GitHub, GitLab, Bitbucket

Vercel Yes. Auto deploys on push from GitHub, GitLab and Bitbucket Source for Vercel, Git push deploys from GitHub, GitLab, Bitbucket

Builds from source without a Dockerfile

Levelrail Partly. Railpack detects Node, Python, Go and more; Ruby is rejected Source for Levelrail, Builds from source without a Dockerfile

Vercel Yes. Framework auto-detection builds with no Dockerfile needed Source for Vercel, Builds from source without a Dockerfile

Scheduled jobs

Levelrail Yes. Per-app cron jobs with run history, logs, retries and alerts Source for Levelrail, Scheduled jobs

Vercel Yes. Cron jobs on all plans, UTC schedules, run Vercel Functions Source for Vercel, Scheduled jobs

Data

Managed databases with scheduled backups

Levelrail Partly. Many engines, scheduled S3 backups; Postgres restores tested live Source for Levelrail, Managed databases with scheduled backups

Vercel Partly. Marketplace databases from the dashboard; backup schedules not stated Source for Vercel, Managed databases with scheduled backups

Encrypted secrets for env vars

Levelrail Yes. Envelope-encrypted, masked in UI, injected at container create Source for Levelrail, Encrypted secrets for env vars

Vercel Yes. Encrypted at rest; Secret type values are write-only after saving Source for Vercel, Encrypted secrets for env vars

Networking

Private networking between apps or nodes

Levelrail Partly. Named networks and allow rules; cross-server mesh unverified on real hosts Source for Levelrail, Private networking between apps or nodes

Vercel Partly. Secure Compute private networks and VPC peering, Enterprise only Source for Vercel, Private networking between apps or nodes

Load balancing across replicas

Levelrail Partly. Experimental and flag gated; not tried across real hosts Source for Levelrail, Load balancing across replicas

Vercel Not applicable

Request firewall, rate limits, bot protection

Levelrail Yes. Ordered rules, IP bans, bot handling, challenges and rate limits Source for Levelrail, Request firewall, rate limits, bot protection

Vercel Partly. Rule counts and rate limit options vary by plan Source for Vercel, Request firewall, rate limits, bot protection

Automatic TLS certificates

Levelrail Partly. Internal issuer by default; public ACME verified once live Source for Levelrail, Automatic TLS certificates

Vercel Yes. Let's Encrypt certs issued and renewed automatically per domain Source for Vercel, Automatic TLS certificates

Platform

Multi-node

Levelrail Partly. Enrollment verified locally; WireGuard mesh still unverified Source for Levelrail, Multi-node

Vercel Not applicable

One-click service templates

Levelrail Yes. 358 templates; a sample is live-deployed in e2e Source for Levelrail, One-click service templates

Vercel Partly. Framework starter templates listed; no service template catalog stated Source for Vercel, One-click service templates

Autoscaling

Levelrail Partly. Beta: CPU, memory or request-rate scaling with cooldowns and reasons Source for Levelrail, Autoscaling

Vercel Yes. Fluid compute scales instances automatically with traffic Source for Vercel, Autoscaling

CLI and HTTP API

Levelrail Yes. CLI and REST API documented; MCP server is beta Source for Levelrail, CLI and HTTP API

Vercel Yes. CLI covers deploy, logs, env, promote; REST API also available Source for Vercel, CLI and HTTP API

Deploy and alert notifications

Levelrail Partly. 18 channel kinds in beta, tested only against mocks Source for Levelrail, Deploy and alert notifications

Vercel Partly. Email, dashboard and push alerts; Slack or Discord not stated Source for Vercel, Deploy and alert notifications

MCP / AI assistant integration

Levelrail Yes. MCP server: 145 read-only tools, 186 in full mode Source for Levelrail, MCP / AI assistant integration

Vercel Yes. Official remote Vercel MCP server at mcp.vercel.com, OAuth Source for Vercel, MCP / AI assistant integration

Runs on servers you own

Levelrail Yes. Runs on Linux servers you provide Source for Levelrail, Runs on servers you own

Vercel Not applicable

Open source license

Levelrail Yes. Apache 2.0, one edition, no paid tier Source for Levelrail, Open source license

Vercel Not stated in their docs

Security

IAM, audit log and 2FA in the free edition

Levelrail Yes. Allow/Deny policies, audit log and TOTP in one edition Source for Levelrail, IAM, audit log and 2FA in the free edition

Vercel Partly. Team roles on Pro; project-level roles on Enterprise only Source for Vercel, IAM, audit log and 2FA in the free edition

SAML or SCIM single sign-on

Levelrail Partly. SAML and SCIM are experimental and off by default Source for Levelrail, SAML or SCIM single sign-on

Vercel Partly. SAML SSO on Pro add-on; Directory Sync provisioning on Enterprise Source for Vercel, SAML or SCIM single sign-on

Architecture

No SSH: agents dial out

Levelrail Yes. Agents dial out over mTLS; no inbound ports Source for Levelrail, No SSH: agents dial out

Heroku Not applicable

Level-triggered reconciler with status reasons

Levelrail Yes. Desired state converged, status condition with reason per pass Source for Levelrail, Level-triggered reconciler with status reasons

Heroku Not applicable

Single control plane binary

Levelrail Yes. One control plane binary, plus one agent per extra node Source for Levelrail, Single control plane binary

Heroku Not applicable

Observability

Metrics and log search built in

Levelrail Yes. Node-local metrics at 15s and full-text log search Source for Levelrail, Metrics and log search built in

Heroku Partly. Dyno metrics and events shown; log search not documented Source for Heroku, Metrics and log search built in

Crashloop diagnosis with last log lines

Levelrail Yes. Crashloop detection surfaces the last log lines Source for Levelrail, Crashloop diagnosis with last log lines

Heroku Partly. Error codes explain crashes in logs; no automatic diagnosis documented Source for Heroku, Crashloop diagnosis with last log lines

Deploys

One-click rollback with pinned images

Levelrail Yes. Prior images pinned so cleanup cannot remove them Source for Levelrail, One-click rollback with pinned images

Heroku Yes. heroku rollback creates a release reusing the earlier slug or image Source for Heroku, One-click rollback with pinned images

Readiness-gated zero-downtime deploys

Levelrail Yes. Cutover only after the readiness probe passes Source for Levelrail, Readiness-gated zero-downtime deploys

Heroku Partly. Preboot is opt-in, standard and performance dynos; not guaranteed Source for Heroku, Readiness-gated zero-downtime deploys

Preview environments per pull request

Levelrail Yes. Stable on GitHub, beta on GitLab and Bitbucket Source for Levelrail, Preview environments per pull request

Heroku Yes. Review apps per GitHub pull request; GitHub only Source for Heroku, Preview environments per pull request

Docker Compose apps

Levelrail Partly. Pre-built images from the dashboard; git deploys can build Source for Levelrail, Docker Compose apps

Heroku Not stated in their docs

Git push deploys from GitHub, GitLab, Bitbucket

Levelrail Partly. All four documented; GitLab and Bitbucket previews are beta, synthetic-webhook tested Source for Levelrail, Git push deploys from GitHub, GitLab, Bitbucket

Heroku Partly. GitHub automatic deploys; no first-party GitLab or Bitbucket integration Source for Heroku, Git push deploys from GitHub, GitLab, Bitbucket

Builds from source without a Dockerfile

Levelrail Partly. Railpack detects Node, Python, Go and more; Ruby is rejected Source for Levelrail, Builds from source without a Dockerfile

Heroku Yes. Buildpacks auto-detect language and build source with no Dockerfile Source for Heroku, Builds from source without a Dockerfile

Scheduled jobs

Levelrail Yes. Per-app cron jobs with run history, logs, retries and alerts Source for Levelrail, Scheduled jobs

Heroku Partly. Heroku Scheduler add-on; jobs billed as one-off dyno hours Source for Heroku, Scheduled jobs

Data

Managed databases with scheduled backups

Levelrail Partly. Many engines, scheduled S3 backups; Postgres restores tested live Source for Levelrail, Managed databases with scheduled backups

Heroku Partly. Postgres scheduled backups on paid plans; no S3 export documented Source for Heroku, Managed databases with scheduled backups

Encrypted secrets for env vars

Levelrail Yes. Envelope-encrypted, masked in UI, injected at container create Source for Levelrail, Encrypted secrets for env vars

Heroku Not stated in their docs

Networking

Private networking between apps or nodes

Levelrail Partly. Named networks and allow rules; cross-server mesh unverified on real hosts Source for Levelrail, Private networking between apps or nodes

Heroku Partly. Private Spaces, Teams or Enterprise only: internal routing and DNS Source for Heroku, Private networking between apps or nodes

Load balancing across replicas

Levelrail Partly. Experimental and flag gated; not tried across real hosts Source for Levelrail, Load balancing across replicas

Heroku Yes. Router randomly balances requests across web dynos Source for Heroku, Load balancing across replicas

Request firewall, rate limits, bot protection

Levelrail Yes. Ordered rules, IP bans, bot handling, challenges and rate limits Source for Levelrail, Request firewall, rate limits, bot protection

Heroku Not stated in their docs

Automatic TLS certificates

Levelrail Partly. Internal issuer by default; public ACME verified once live Source for Levelrail, Automatic TLS certificates

Heroku Yes. Automated Certificate Management: free Let's Encrypt certs for custom domains Source for Heroku, Automatic TLS certificates

Platform

Multi-node

Levelrail Partly. Enrollment verified locally; WireGuard mesh still unverified Source for Levelrail, Multi-node

Heroku Not applicable

One-click service templates

Levelrail Yes. 358 templates; a sample is live-deployed in e2e Source for Levelrail, One-click service templates

Heroku Partly. app.json and Deploy button; no one-click service catalog Source for Heroku, One-click service templates

Autoscaling

Levelrail Partly. Beta: CPU, memory or request-rate scaling with cooldowns and reasons Source for Levelrail, Autoscaling

Heroku Partly. Web dynos only, on Performance, Private or Shield tiers, by p95 Source for Heroku, Autoscaling

CLI and HTTP API

Levelrail Yes. CLI and REST API documented; MCP server is beta Source for Levelrail, CLI and HTTP API

Heroku Partly. CLI and Platform API for apps and config; full parity not stated Source for Heroku, CLI and HTTP API

Deploy and alert notifications

Levelrail Partly. 18 channel kinds in beta, tested only against mocks Source for Levelrail, Deploy and alert notifications

Heroku Partly. Slack via ChatOps or add-ons; HTTP webhooks; no deploy email Source for Heroku, Deploy and alert notifications

MCP / AI assistant integration

Levelrail Yes. MCP server: 145 read-only tools, 186 in full mode Source for Levelrail, MCP / AI assistant integration

Heroku Yes. Remote MCP server at mcp.heroku.com with OAuth login Source for Heroku, MCP / AI assistant integration

Runs on servers you own

Levelrail Yes. Runs on Linux servers you provide Source for Levelrail, Runs on servers you own

Heroku Not applicable

Open source license

Levelrail Yes. Apache 2.0, one edition, no paid tier Source for Levelrail, Open source license

Heroku Not stated in their docs

Security

IAM, audit log and 2FA in the free edition

Levelrail Yes. Allow/Deny policies, audit log and TOTP in one edition Source for Levelrail, IAM, audit log and 2FA in the free edition

Heroku Partly. Four team roles and mandatory MFA; audit trails Enterprise only Source for Heroku, IAM, audit log and 2FA in the free edition

SAML or SCIM single sign-on

Levelrail Partly. SAML and SCIM are experimental and off by default Source for Levelrail, SAML or SCIM single sign-on

Heroku Partly. SAML 2.0 SSO for Teams and Enterprise; SCIM not documented Source for Heroku, SAML or SCIM single sign-on

Architecture

No SSH: agents dial out

Levelrail Yes. Agents dial out over mTLS; no inbound ports Source for Levelrail, No SSH: agents dial out

Railway Not applicable

Level-triggered reconciler with status reasons

Levelrail Yes. Desired state converged, status condition with reason per pass Source for Levelrail, Level-triggered reconciler with status reasons

Railway Not applicable

Single control plane binary

Levelrail Yes. One control plane binary, plus one agent per extra node Source for Levelrail, Single control plane binary

Railway Not applicable

Observability

Metrics and log search built in

Levelrail Yes. Node-local metrics at 15s and full-text log search Source for Levelrail, Metrics and log search built in

Railway Yes. Dashboard CPU, memory, network, disk metrics; log search Source for Railway, Metrics and log search built in

Crashloop diagnosis with last log lines

Levelrail Yes. Crashloop detection surfaces the last log lines Source for Levelrail, Crashloop diagnosis with last log lines

Railway Partly. Auto restarts up to 10 times on free plans Source for Railway, Crashloop diagnosis with last log lines

Deploys

One-click rollback with pinned images

Levelrail Yes. Prior images pinned so cleanup cannot remove them Source for Levelrail, One-click rollback with pinned images

Railway Partly. Dashboard rollback to prior image; images kept 24 to 360 hours Source for Railway, One-click rollback with pinned images

Readiness-gated zero-downtime deploys

Levelrail Yes. Cutover only after the readiness probe passes Source for Levelrail, Readiness-gated zero-downtime deploys

Railway Partly. Healthcheck gates cutover; volume services see brief downtime Source for Railway, Readiness-gated zero-downtime deploys

Preview environments per pull request

Levelrail Yes. Stable on GitHub, beta on GitLab and Bitbucket Source for Levelrail, Preview environments per pull request

Railway Yes. Environments per PR Source for Railway, Preview environments per pull request

Docker Compose apps

Levelrail Partly. Pre-built images from the dashboard; git deploys can build Source for Levelrail, Docker Compose apps

Railway Partly. Imports Compose services; docker-compose.yml not run directly Source for Railway, Docker Compose apps

Git push deploys from GitHub, GitLab, Bitbucket

Levelrail Partly. All four documented; GitLab and Bitbucket previews are beta, synthetic-webhook tested Source for Levelrail, Git push deploys from GitHub, GitLab, Bitbucket

Railway Partly. Autodeploy from GitHub only; GitLab and Bitbucket not documented Source for Railway, Git push deploys from GitHub, GitLab, Bitbucket

Builds from source without a Dockerfile

Levelrail Partly. Railpack detects Node, Python, Go and more; Ruby is rejected Source for Levelrail, Builds from source without a Dockerfile

Railway Yes. Railpack detects stack without Dockerfile; Dockerfile takes priority Source for Railway, Builds from source without a Dockerfile

Scheduled jobs

Levelrail Yes. Per-app cron jobs with run history, logs, retries and alerts Source for Levelrail, Scheduled jobs

Railway Yes. Cron schedule per service; runs at least 5 minutes apart, UTC Source for Railway, Scheduled jobs

Data

Managed databases with scheduled backups

Levelrail Partly. Many engines, scheduled S3 backups; Postgres restores tested live Source for Levelrail, Managed databases with scheduled backups

Railway Partly. Scheduled volume and Postgres PITR backups; S3 export needs own job Source for Railway, Managed databases with scheduled backups

Encrypted secrets for env vars

Levelrail Yes. Envelope-encrypted, masked in UI, injected at container create Source for Levelrail, Encrypted secrets for env vars

Railway Yes. Variables encrypted at rest; sealed values write-only Source for Railway, Encrypted secrets for env vars

Networking

Private networking between apps or nodes

Levelrail Partly. Named networks and allow rules; cross-server mesh unverified on real hosts Source for Levelrail, Private networking between apps or nodes

Railway Yes. WireGuard private DNS per environment, service.railway.internal Source for Railway, Private networking between apps or nodes

Load balancing across replicas

Levelrail Partly. Experimental and flag gated; not tried across real hosts Source for Levelrail, Load balancing across replicas

Railway Yes. Traffic spread across replicas and regions; no sticky sessions Source for Railway, Load balancing across replicas

Request firewall, rate limits, bot protection

Levelrail Yes. Ordered rules, IP bans, bot handling, challenges and rate limits Source for Levelrail, Request firewall, rate limits, bot protection

Railway Partly. Under Attack Mode only; no rate limits or custom rules Source for Railway, Request firewall, rate limits, bot protection

Automatic TLS certificates

Levelrail Partly. Internal issuer by default; public ACME verified once live Source for Levelrail, Automatic TLS certificates

Railway Yes. Let's Encrypt certificates for custom domains, renewed automatically Source for Railway, Automatic TLS certificates

Platform

Multi-node

Levelrail Partly. Enrollment verified locally; WireGuard mesh still unverified Source for Levelrail, Multi-node

Railway Not applicable

One-click service templates

Levelrail Yes. 358 templates; a sample is live-deployed in e2e Source for Levelrail, One-click service templates

Railway Yes. Template marketplace with one-click deploys Source for Railway, One-click service templates

Autoscaling

Levelrail Partly. Beta: CPU, memory or request-rate scaling with cooldowns and reasons Source for Levelrail, Autoscaling

Railway No. No native replica autoscaling; custom script via API Source for Railway, Autoscaling

CLI and HTTP API

Levelrail Yes. CLI and REST API documented; MCP server is beta Source for Levelrail, CLI and HTTP API

Railway Partly. Public GraphQL API and CLI; dashboard parity not stated Source for Railway, CLI and HTTP API

Deploy and alert notifications

Levelrail Partly. 18 channel kinds in beta, tested only against mocks Source for Levelrail, Deploy and alert notifications

Railway Yes. Slack and Discord webhooks; email via account notifications Source for Railway, Deploy and alert notifications

MCP / AI assistant integration

Levelrail Yes. MCP server: 145 read-only tools, 186 in full mode Source for Levelrail, MCP / AI assistant integration

Railway Yes. Official hosted MCP server at mcp.railway.com Source for Railway, MCP / AI assistant integration

Runs on servers you own

Levelrail Yes. Runs on Linux servers you provide Source for Levelrail, Runs on servers you own

Railway Not applicable

Open source license

Levelrail Yes. Apache 2.0, one edition, no paid tier Source for Levelrail, Open source license

Railway Not stated in their docs

Security

IAM, audit log and 2FA in the free edition

Levelrail Yes. Allow/Deny policies, audit log and TOTP in one edition Source for Levelrail, IAM, audit log and 2FA in the free edition

Railway Partly. Audit logs kept 48 hours on free plans; longer on paid Source for Railway, IAM, audit log and 2FA in the free edition

SAML or SCIM single sign-on

Levelrail Partly. SAML and SCIM are experimental and off by default Source for Levelrail, SAML or SCIM single sign-on

Railway Partly. SAML SSO on Enterprise; SCIM not documented Source for Railway, SAML or SCIM single sign-on

Architecture

No SSH: agents dial out

Levelrail Yes. Agents dial out over mTLS; no inbound ports Source for Levelrail, No SSH: agents dial out

Cloud Run Not applicable

Level-triggered reconciler with status reasons

Levelrail Yes. Desired state converged, status condition with reason per pass Source for Levelrail, Level-triggered reconciler with status reasons

Cloud Run Not applicable

Single control plane binary

Levelrail Yes. One control plane binary, plus one agent per extra node Source for Levelrail, Single control plane binary

Cloud Run Not applicable

Observability

Metrics and log search built in

Levelrail Yes. Node-local metrics at 15s and full-text log search Source for Levelrail, Metrics and log search built in

Cloud Run Yes. Automatic Cloud Monitoring metrics; logs in Cloud Logging Source for Cloud Run, Metrics and log search built in

Crashloop diagnosis with last log lines

Levelrail Yes. Crashloop detection surfaces the last log lines Source for Levelrail, Crashloop diagnosis with last log lines

Cloud Run Partly. Troubleshooting guide; logs checked manually, no automatic crashloop view Source for Cloud Run, Crashloop diagnosis with last log lines

Deploys

One-click rollback with pinned images

Levelrail Yes. Prior images pinned so cleanup cannot remove them Source for Levelrail, One-click rollback with pinned images

Cloud Run Yes. Traffic rolls back to a previous revision immediately Source for Cloud Run, One-click rollback with pinned images

Readiness-gated zero-downtime deploys

Levelrail Yes. Cutover only after the readiness probe passes Source for Levelrail, Readiness-gated zero-downtime deploys

Cloud Run Partly. Gradual rollouts and traffic splits; health gating of cutover not stated Source for Cloud Run, Readiness-gated zero-downtime deploys

Preview environments per pull request

Levelrail Yes. Stable on GitHub, beta on GitLab and Bitbucket Source for Levelrail, Preview environments per pull request

Cloud Run Partly. Revision tags give separate URLs without traffic; no PR previews Source for Cloud Run, Preview environments per pull request

Docker Compose apps

Levelrail Partly. Pre-built images from the dashboard; git deploys can build Source for Levelrail, Docker Compose apps

Cloud Run Partly. Compose file deploys as one multi container service; alpha or preview Source for Cloud Run, Docker Compose apps

Git push deploys from GitHub, GitLab, Bitbucket

Levelrail Partly. All four documented; GitLab and Bitbucket previews are beta, synthetic-webhook tested Source for Levelrail, Git push deploys from GitHub, GitLab, Bitbucket

Cloud Run Yes. Developer Connect covers GitHub, GitLab, Bitbucket; Cloud Build covers GitHub Source for Cloud Run, Git push deploys from GitHub, GitLab, Bitbucket

Builds from source without a Dockerfile

Levelrail Partly. Railpack detects Node, Python, Go and more; Ruby is rejected Source for Levelrail, Builds from source without a Dockerfile

Cloud Run Yes. Google Cloud buildpacks detect the language; no Dockerfile needed Source for Cloud Run, Builds from source without a Dockerfile

Scheduled jobs

Levelrail Yes. Per-app cron jobs with run history, logs, retries and alerts Source for Levelrail, Scheduled jobs

Cloud Run Partly. Scheduled job runs need Cloud Scheduler calling the job endpoint Source for Cloud Run, Scheduled jobs

Data

Managed databases with scheduled backups

Levelrail Partly. Many engines, scheduled S3 backups; Postgres restores tested live Source for Levelrail, Managed databases with scheduled backups

Cloud Run Not stated in their docs

Encrypted secrets for env vars

Levelrail Yes. Envelope-encrypted, masked in UI, injected at container create Source for Levelrail, Encrypted secrets for env vars

Cloud Run Yes. Secret Manager values injected as env vars or mounted volumes Source for Cloud Run, Encrypted secrets for env vars

Networking

Private networking between apps or nodes

Levelrail Partly. Named networks and allow rules; cross-server mesh unverified on real hosts Source for Levelrail, Private networking between apps or nodes

Cloud Run Partly. Direct VPC egress reaches private IPs; internal DNS not documented Source for Cloud Run, Private networking between apps or nodes

Load balancing across replicas

Levelrail Partly. Experimental and flag gated; not tried across real hosts Source for Levelrail, Load balancing across replicas

Cloud Run Yes. Requests balanced across regional instances automatically; multi region needs load balancer Source for Cloud Run, Load balancing across replicas

Request firewall, rate limits, bot protection

Levelrail Yes. Ordered rules, IP bans, bot handling, challenges and rate limits Source for Levelrail, Request firewall, rate limits, bot protection

Cloud Run Partly. Cloud Armor filters traffic only through an external load balancer Source for Cloud Run, Request firewall, rate limits, bot protection

Automatic TLS certificates

Levelrail Partly. Internal issuer by default; public ACME verified once live Source for Levelrail, Automatic TLS certificates

Cloud Run Partly. Managed certificates on custom domain mappings, which are in Preview Source for Cloud Run, Automatic TLS certificates

Platform

Multi-node

Levelrail Partly. Enrollment verified locally; WireGuard mesh still unverified Source for Levelrail, Multi-node

Cloud Run Not applicable

One-click service templates

Levelrail Yes. 358 templates; a sample is live-deployed in e2e Source for Levelrail, One-click service templates

Cloud Run Not stated in their docs

Autoscaling

Levelrail Partly. Beta: CPU, memory or request-rate scaling with cooldowns and reasons Source for Levelrail, Autoscaling

Cloud Run Yes. Scales instances on request volume, with configurable maximums Source for Cloud Run, Autoscaling

CLI and HTTP API

Levelrail Yes. CLI and REST API documented; MCP server is beta Source for Levelrail, CLI and HTTP API

Cloud Run Yes. gcloud CLI and Admin API manage services and jobs Source for Cloud Run, CLI and HTTP API

Deploy and alert notifications

Levelrail Partly. 18 channel kinds in beta, tested only against mocks Source for Levelrail, Deploy and alert notifications

Cloud Run Partly. Cloud Monitoring alerts to email, Slack, webhooks, Pub/Sub Source for Cloud Run, Deploy and alert notifications

MCP / AI assistant integration

Levelrail Yes. MCP server: 145 read-only tools, 186 in full mode Source for Levelrail, MCP / AI assistant integration

Cloud Run Partly. Managed remote MCP server deploys and inspects services Source for Cloud Run, MCP / AI assistant integration

Runs on servers you own

Levelrail Yes. Runs on Linux servers you provide Source for Levelrail, Runs on servers you own

Cloud Run Not applicable

Open source license

Levelrail Yes. Apache 2.0, one edition, no paid tier Source for Levelrail, Open source license

Cloud Run Not stated in their docs

Security

IAM, audit log and 2FA in the free edition

Levelrail Yes. Allow/Deny policies, audit log and TOTP in one edition Source for Levelrail, IAM, audit log and 2FA in the free edition

Cloud Run Partly. Cloud IAM and audit logs; 2FA is not a Cloud Run feature Source for Cloud Run, IAM, audit log and 2FA in the free edition

SAML or SCIM single sign-on

Levelrail Partly. SAML and SCIM are experimental and off by default Source for Levelrail, SAML or SCIM single sign-on

Cloud Run Not stated in their docs

As of 2026-10. Statements about other projects come from their own public documentation, linked on each cell, and can be out of date. Product names and logos belong to their owners and are used for identification only.

Where Levelrail is behind or still unproven.

Built from our own cells that are not a plain yes. Each links to the page that states the limit.

  • Docker Compose apps

    Pre-built images from the dashboard; git deploys can build

    Read the docs
  • Git push deploys from GitHub, GitLab, Bitbucket

    All four documented; GitLab and Bitbucket previews are beta, synthetic-webhook tested

    Read the docs
  • Builds from source without a Dockerfile

    Railpack detects Node, Python, Go and more; Ruby is rejected

    Read the docs
  • Managed databases with scheduled backups

    Many engines, scheduled S3 backups; Postgres restores tested live

    Read the docs
  • Private networking between apps or nodes

    Named networks and allow rules; cross-server mesh unverified on real hosts

    Read the docs
  • Load balancing across replicas

    Experimental and flag gated; not tried across real hosts

    Read the docs
  • Automatic TLS certificates

    Internal issuer by default; public ACME verified once live

    Read the docs
  • Multi-node

    Enrollment verified locally; WireGuard mesh still unverified

    Read the docs
  • Autoscaling

    Beta: CPU, memory or request-rate scaling with cooldowns and reasons

    Read the docs
  • Deploy and alert notifications

    18 channel kinds in beta, tested only against mocks

    Read the docs
  • SAML or SCIM single sign-on

    SAML and SCIM are experimental and off by default

    Read the docs

What each one is good at, and where we differ.

Coolify Self-hosted

Coolify

Large catalog of one-click services and a polished dashboard, managing existing servers over plain SSH.

Full Coolify comparison

Good at

  • Broadest one-click template list of the projects compared.
  • Manages servers you already have over plain SSH, with nothing to install beyond Docker.

Where Levelrail differs

  • 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.
  • Metrics, log search and rollback with pinned images ship in the core.

Choose Coolify when you want the broadest template list and SSH-only server management.

Sources (26)

Self-hosted

Dokploy

A polished project built on Docker Swarm, with a modern dashboard on top.

Full Dokploy comparison

Good at

  • Multi-node scheduling and rolling updates come from Docker Swarm, a mature, widely understood mechanism.
  • A modern dashboard, and a natural fit if you already think in Swarm terms.

Where Levelrail differs

  • Plain Docker with a reconciler and a small agent per node, with no Swarm or overlay network.
  • Metrics, full-text logs and crashloop detection ship in the core with no extra stack.
  • One Go binary with embedded SQLite and embedded Caddy, instead of Traefik.

Choose Dokploy when docker Swarm is already your model, and you want multi-node scheduling and rolling updates from a mature mechanism.

Sources (21)

CapRover Self-hosted

CapRover

A long-running, simple, Swarm-based platform with a one-click app store and a CLI.

Full CapRover comparison

Good at

  • Large install base and easy to pick up.
  • A one-click app store, larger than Levelrail's catalog today.

Where Levelrail differs

  • Plain Docker containers with a level-triggered reconciler instead of Swarm services.
  • An agent per node dials out over mTLS, so managed servers need no inbound port.
  • Caddy embedded for ingress instead of nginx, with metrics and logs in the core.

Choose CapRover when docker Swarm is already your model, or you want a long-running platform with a large install base and app store.

Sources (19)

Self-hosted

Dokku

The classic Heroku on your own box: git push to deploy, buildpacks, a rich plugin ecosystem.

Full Dokku comparison

Good at

  • Almost no idle footprint, because there is no long-running control service.
  • Hard to beat for simplicity on a single server.

Where Levelrail differs

  • A dashboard with deploy history and one-click rollback to a pinned previous image.
  • Metrics and log search in the core, where Dokku suggests adding your own stack.
  • More servers join with a one-time token and an agent that dials out.

Choose Dokku when you run one server and want the simplest possible thing.

Sources (20)

Self-hosted

Kamal

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

Full Kamal comparison

Good at

  • As few moving parts as possible.
  • Pairs with kamal-proxy for zero-downtime cutover.
  • No dashboard needed, which suits some teams.

Where 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 when you want the fewest possible moving parts and do not need a dashboard.

Sources (15)

Hosted

Vercel

A managed cloud with a global edge network, git integration, previews and instant rollback.

Full Vercel comparison

Good at

  • A global edge network, which Levelrail does not provide.
  • Git integration, previews and instant rollback on a managed cloud.

Where Levelrail differs

  • Runs on Linux servers you own, so secrets, metrics and logs stay on your nodes.
  • Cost is the servers you rent, not per request or per seat.
  • Long-lived containers built from a Dockerfile, with no serverless functions or edge network.

Choose Vercel when you need a global edge network or serverless functions; Levelrail offers neither and suggests a CDN in front.

Sources (19)

Hosted

Heroku

A managed platform: git push, buildpacks and release phase, billed per dyno and per add-on.

Full Heroku comparison

Good at

  • Operations are handled by the vendor, so nobody maintains servers.
  • Add-ons cover databases and third-party services.

Where Levelrail differs

  • Runs on Linux boxes you own, with no per-dyno or per-app fee.
  • Eight managed database engines with scheduled, verified backups instead of add-ons.
  • Dockerfile builds with readiness-gated cutover, not buildpacks.

Choose Heroku when you want the vendor to handle operations, since with Levelrail you are the one on call for the servers.

Sources (19)

Hosted

Railway

A vendor-managed cloud with usage-based pricing and environments per pull request.

Full Railway comparison

Good at

  • A simple flow from connecting a repo to a running service with domain and database.
  • Environments per pull request, on a vendor-managed cloud.

Where Levelrail differs

  • Runs on your Linux servers, so pricing is your own server cost.
  • Secrets, metrics and logs stay on your nodes unless you configure an export.
  • Self-hosted software only; there is no managed cloud version.

Choose Railway when you want a vendor-managed cloud rather than operating your own servers; Levelrail has no managed version.

Sources (22)

Hosted

Cloud Run

A good fit for bursty traffic, with scale to zero and per-request billing.

Full Cloud Run comparison

Good at

  • Scale to zero and per-request billing are hard to beat for spiky or rare traffic.
  • Capacity can appear in seconds under load and span zones or regions.
  • Google identity and networking features such as workload identity.

Where Levelrail differs

  • A fixed-price server you run, so cost does not move with traffic.
  • Replicas are fixed with no autoscaling, and wake from sleep is slower than a cold start.
  • Logs, metrics and data stay on machines you control, with nothing billed by volume.

Choose Cloud Run when traffic is spiky or rare, you need capacity in seconds, or you depend on Google identity and networking features.

Sources (19)

What Levelrail does not do yet.

  1. 01

    SAML and SCIM are experimental

    OAuth and OIDC are supported. SAML and SCIM sit behind a beta flag and are not tested against a live provider.

  2. 02

    The largest template catalog

    Levelrail ships 358 templates, but other projects may list more, and only a sample of ours is live-deployed in the end-to-end suite.

  3. 03

    Track record

    Fewer real-world deployments and less community knowledge than projects that have existed for years.

  4. 04

    Public ACME has had one live run

    TLS defaults to an internal issuer. The public issuer was verified once against Let’s Encrypt. Renewal and DNS-01 wildcards are not yet exercised live.

  5. 05

    Windows and Kubernetes

    No Windows or non-Linux nodes and no Kubernetes compatibility layer. These are deliberate non-goals.

The full list of limits, with status badges, lives on the open source page.

Pick the one that fits your situation.

  • One server, the simplest possible thing, a bare CLI Dokku or Kamal
  • One server, with a dashboard, TLS, logs and rollback already included Levelrail (a single node is its well-tested path)
  • Broadest template list and SSH-only management Coolify
  • Docker Swarm is already your model Dokploy or CapRover
  • An agent-based control plane with built-in observability, IAM and audit on one binary Levelrail

Questions people ask when they compare.

Built from the sourced matrix above, so the answers stay as honest as the table.

What is the best self-hosted alternative to Coolify?

It depends on what you want. Dokploy and CapRover fit a Docker Swarm model, Dokku and Kamal fit one server with the fewest moving parts, and Levelrail fits teams that want an agent-based control plane with metrics, logs, IAM and audit in one binary. Levelrail is pre-release and Coolify has the larger template catalog and track record, so read the sourced comparison before choosing.

What is a self-hosted alternative to Vercel, Heroku or Railway?

Levelrail gives you git push deploys, preview environments, TLS, logs, metrics and rollback on servers you own. It does not offer a global edge network, serverless functions or a managed cloud, so if you need those, a hosted platform is the better fit. Dokku is the closest minimal option for a single server.

Can I migrate from Coolify, Dokploy or CapRover to Levelrail?

Yes. Levelrail has a read-only importer with a dry-run mode, so you can keep the old platform running while you try the new one, then move DNS when you trust it. The migration guide in the docs walks through it.

Which self-hosted deployment platform is the lightest?

Levelrail is one Go binary for the control plane and one for the agent. On a development build it idled at 68 MB of memory with no apps and 91 MB with 500 suspended apps. Those are pre-release numbers from one machine, and the method and limits are published in the docs.

Is Levelrail a good alternative to Coolify?

Large catalog of one-click services and a polished dashboard, managing existing servers over plain SSH. How Levelrail differs: 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. Metrics, log search and rollback with pinned images ship in the core. Choose Coolify instead when you want the broadest template list and SSH-only server management. Levelrail is pre-release, so check the comparison for what it does not do yet.

Is Levelrail a good alternative to Dokploy?

A polished project built on Docker Swarm, with a modern dashboard on top. How Levelrail differs: Plain Docker with a reconciler and a small agent per node, with no Swarm or overlay network. Metrics, full-text logs and crashloop detection ship in the core with no extra stack. One Go binary with embedded SQLite and embedded Caddy, instead of Traefik. Choose Dokploy instead when docker Swarm is already your model, and you want multi-node scheduling and rolling updates from a mature mechanism. Levelrail is pre-release, so check the comparison for what it does not do yet.

Is Levelrail a good alternative to CapRover?

A long-running, simple, Swarm-based platform with a one-click app store and a CLI. How Levelrail differs: Plain Docker containers with a level-triggered reconciler instead of Swarm services. An agent per node dials out over mTLS, so managed servers need no inbound port. Caddy embedded for ingress instead of nginx, with metrics and logs in the core. Choose CapRover instead when docker Swarm is already your model, or you want a long-running platform with a large install base and app store. Levelrail is pre-release, so check the comparison for what it does not do yet.

Is Levelrail a good alternative to Dokku?

The classic Heroku on your own box: git push to deploy, buildpacks, a rich plugin ecosystem. How Levelrail differs: A dashboard with deploy history and one-click rollback to a pinned previous image. Metrics and log search in the core, where Dokku suggests adding your own stack. More servers join with a one-time token and an agent that dials out. Choose Dokku instead when you run one server and want the simplest possible thing. Levelrail is pre-release, so check the comparison for what it does not do yet.

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 is pre-release, so check the comparison for what it does not do yet.

Is Levelrail a good alternative to Vercel?

A managed cloud with a global edge network, git integration, previews and instant rollback. How Levelrail differs: Runs on Linux servers you own, so secrets, metrics and logs stay on your nodes. Cost is the servers you rent, not per request or per seat. Long-lived containers built from a Dockerfile, with no serverless functions or edge network. Choose Vercel instead when you need a global edge network or serverless functions; Levelrail offers neither and suggests a CDN in front. Levelrail is pre-release, so check the comparison for what it does not do yet.

Is Levelrail a good alternative to Heroku?

A managed platform: git push, buildpacks and release phase, billed per dyno and per add-on. How Levelrail differs: Runs on Linux boxes you own, with no per-dyno or per-app fee. Eight managed database engines with scheduled, verified backups instead of add-ons. Dockerfile builds with readiness-gated cutover, not buildpacks. Choose Heroku instead when you want the vendor to handle operations, since with Levelrail you are the one on call for the servers. Levelrail is pre-release, so check the comparison for what it does not do yet.

Is Levelrail a good alternative to Railway?

A vendor-managed cloud with usage-based pricing and environments per pull request. How Levelrail differs: Runs on your Linux servers, so pricing is your own server cost. Secrets, metrics and logs stay on your nodes unless you configure an export. Self-hosted software only; there is no managed cloud version. Choose Railway instead when you want a vendor-managed cloud rather than operating your own servers; Levelrail has no managed version. Levelrail is pre-release, so check the comparison for what it does not do yet.

Is Levelrail a good alternative to Cloud Run?

A good fit for bursty traffic, with scale to zero and per-request billing. How Levelrail differs: A fixed-price server you run, so cost does not move with traffic. Replicas are fixed with no autoscaling, and wake from sleep is slower than a cold start. Logs, metrics and data stay on machines you control, with nothing billed by volume. Choose Cloud Run instead when traffic is spiky or rare, you need capacity in seconds, or you depend on Google identity and networking features. Levelrail is pre-release, so check the comparison for what it does not do yet.