The self-hosted Heroku alternative

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

Levelrail control plane memory, idle, measured

~200 MB

Install
1 binaryplus one agent per extra node
License
Apache 2.0one edition, no license key
Ahead on
10 of 38capabilities, per Heroku's docs

The memory figure is one idle measurement of the Levelrail control plane (method). As of 2026-11-18.

01

What you gain over Heroku

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

Capabilities where Levelrail is ahead of Heroku
Capability Levelrail Heroku
Metrics and log search built in Node-local metrics at 15s and full-text log search Partly Dyno metrics and events shown
Crashloop diagnosis with last log lines Crashloop detection surfaces the last log lines Partly Error codes explain crashes in logs
Readiness-gated deploys (zero-downtime on one node) Cutover only after the readiness probe passes Partly Preboot is opt-in, standard and performance dynos
Scheduled jobs Per-app cron jobs with run history, logs, retries and alerts Partly Heroku Scheduler is a free add-on running every 10 minutes, hourly or daily
One-click service templates 592 catalog entries, 583 active Partly app.json and Deploy button
Sleep idle apps, wake on request Opt in per app Partly Eco web dynos sleep after 30 minutes without web traffic
CLI and HTTP API CLI and REST API documented Partly CLI and Platform API for apps and config
IAM, audit log and 2FA in the free edition Allow/Deny IAM policies, passkeys and TOTP, and an audit log Partly Four team roles and mandatory MFA
Audit log of every action Every mutating request recorded Partly Audit trail export for Enterprise accounts only, needs manage permission
Deploy freezes and policies Cron-defined freeze windows per app with an audited override reason Partly 'Wait for CI to pass before deploy' holds GitHub auto-deploys until commit statuses succeed
02

All 38 capabilities

Statuses for Heroku are what its own documentation states; "Not stated" means its docs do not say. For Levelrail, "Active" means the feature ships today, with beta and stable tags from the feature status page and the exact scope in each note.

Levelrail
YesActive
Heroku
YesPartlyNo

A rule marks the 10 rows where Levelrail is ahead.

Levelrail compared with Heroku, by capability
Capability Levelrail Heroku
Architecture 3
No SSH: agents dial out Yesbeta Agents dial out over mTLS; no inbound ports Source for Levelrail, No SSH: agents dial out Not applicable
Level-triggered reconciler with status reasons Yes Desired state converged, status condition with reason per pass Source for Levelrail, Level-triggered reconciler with status reasons Not applicable
Single control plane binary Yes One control plane binary, plus one agent per extra node Source for Levelrail, Single control plane binary Not applicable
Observability 3
Metrics and log search built in (Levelrail ahead) Yes Node-local metrics at 15s and full-text log search Source for Levelrail, Metrics and log search built in Partly 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 ahead) Yes Crashloop detection surfaces the last log lines Source for Levelrail, Crashloop diagnosis with last log lines Partly Error codes explain crashes in logs; no automatic diagnosis documented Source for Heroku, Crashloop diagnosis with last log lines
Public status page Yesstable Opt-in public page with components, 90 day uptime bars, incidents, maintenance and RSS Source for Levelrail, Public status page Not stated in their docs
Deploys 10
One-click rollback with pinned images Yesstable Prior images pinned so cleanup cannot remove them. A 5xx spike or crashloop after cutover rolls back automatically (live-tested); the latency signal is beta Source for Levelrail, One-click rollback with pinned images Yes heroku rollback creates a release reusing the earlier slug or image Source for Heroku, One-click rollback with pinned images
Readiness-gated deploys (zero-downtime on one node) (Levelrail ahead) Yes Cutover only after the readiness probe passes. Live-tested on one node; multi-node is beta Source for Levelrail, Readiness-gated deploys (zero-downtime on one node) Partly Preboot is opt-in, standard and performance dynos; not guaranteed Source for Heroku, Readiness-gated deploys (zero-downtime on one node)
Preview environments per pull request Yesstable Stable on GitHub, beta on GitLab and Bitbucket Source for Levelrail, Preview environments per pull request Yes Review apps per GitHub pull request; GitHub only Source for Heroku, Preview environments per pull request
Docker Compose apps Active Pre-built images from the dashboard; git deploys can build Source for Levelrail, Docker Compose apps No Docker Compose is mentioned for local development only; deploy options are container:push and release, or heroku.yml builds (heroku.yml Docker builds are unsupported on Fir) Source for Heroku, Docker Compose apps
Git push deploys from GitHub, GitLab, Bitbucket Active GitHub, GitLab, Bitbucket and Gitea documented; GitLab and Bitbucket previews are beta (synthetic webhooks). A git push remote on your own server (no provider needed) is beta Source for Levelrail, Git push deploys from GitHub, GitLab, Bitbucket Partly GitHub automatic deploys (GitHub Enterprise Server and Cloud for Enterprise customers); GitLab and Bitbucket go through CI with dpl, git hooks, the Platform API or Terraform Source for Heroku, Git push deploys from GitHub, GitLab, Bitbucket
Builds from source without a Dockerfile Active Railpack detects Node, Python, Go and more. Ruby and PHP are accepted but only plan generation is verified, no live build; Rust, Deno and Elixir are rejected Source for Levelrail, Builds from source without a Dockerfile Yes Buildpacks auto-detect language and build source with no Dockerfile Source for Heroku, Builds from source without a Dockerfile
Scheduled jobs (Levelrail ahead) Yes Per-app cron jobs with run history, logs, retries and alerts Source for Levelrail, Scheduled jobs Partly Heroku Scheduler is a free add-on running every 10 minutes, hourly or daily (daily in UTC); jobs bill as one-off dyno hours; Heroku advises a custom clock process for critical jobs because runs can be skipped or duplicated Source for Heroku, Scheduled jobs
Deploy freezes and policies (Levelrail ahead) Yesstable Cron-defined freeze windows per app with an audited override reason; also gate image auto-update and scheduled deploys Source for Levelrail, Deploy freezes and policies Partly 'Wait for CI to pass before deploy' holds GitHub auto-deploys until commit statuses succeed; no freeze windows stated Source for Heroku, Deploy freezes and policies
CI deploys with no stored secret Active GitHub Actions only: a GitHub OIDC token is exchanged for a 15 minute token scoped to one app. Other CI uses an API token Source for Levelrail, CI deploys with no stored secret Not stated in their docs
Static site hosting Yes Static HTML from git served by the embedded ingress with TLS; drag-and-drop folder or zip deploy Source for Levelrail, Static site hosting Not stated in their docs
Data 3
Managed databases with scheduled backups Active Many engines, scheduled S3 backups. Postgres point-in-time restore is tested live; MySQL, MariaDB and MongoDB are beta Source for Levelrail, Managed databases with scheduled backups Partly Postgres Essential-0 $5 (1 GB, 20 connections, no rollback, no fork/follow, 99.5% uptime); daily logical backups; Advanced tier (usage-based, from $150, HA by default) replaces Classic and Heroku PGBackups is not supported on Advanced Source for Heroku, Managed databases with scheduled backups
Point-in-time database restore Active Postgres stable with an S3 compatible bucket; MySQL and MariaDB beta; MongoDB has no point-in-time restore Source for Levelrail, Point-in-time database restore Partly Rollback window by tier: Standard 4 days, Premium/Private/Shield/Advanced 7 days; Essential has no rollback Source for Heroku, Point-in-time database restore
Encrypted secrets for env vars Yes Envelope-encrypted, masked in UI, injected at container create Source for Levelrail, Encrypted secrets for env vars Not stated in their docs
Networking 4
Private networking between apps or nodes Active Named networks and allow rules; cross-server mesh unverified on real hosts Source for Levelrail, Private networking between apps or nodes Partly Private Spaces, Teams or Enterprise only: internal routing and DNS Source for Heroku, Private networking between apps or nodes
Load balancing across replicas Active Apps with more than one replica are round-robin balanced by default, with failed-replica skip and retry. The configurable balancer (health checks, sticky sessions, weights, drain) is experimental, behind a flag, verified on one machine only. HTTP only Source for Levelrail, Load balancing across replicas Yes Router randomly balances requests across web dynos Source for Heroku, Load balancing across replicas
Request firewall, rate limits, bot protection Yes Ordered rules, IP bans, bot handling, challenges and rate limits Source for Levelrail, Request firewall, rate limits, bot protection Not stated in their docs
Automatic TLS certificates Active Self-signed by default; public ACME (HTTP-01) has one recorded run on a live VPS. Renewal near expiry and DNS-01 wildcards are not exercised live; CAs needing EAB are unsupported Source for Levelrail, Automatic TLS certificates Yes Automated Certificate Management: free Let's Encrypt certs for custom domains Source for Heroku, Automatic TLS certificates
Platform 11
Multi-node Activebeta Join, cordon and drain with real container relocation verified across two local Docker daemons; WireGuard mesh and cross-host transport still unverified. Resource-aware placement is beta Source for Levelrail, Multi-node Not applicable
One-click service templates (Levelrail ahead) Yesbeta 592 catalog entries, 583 active; 346 proven on a real engine, 246 previews without that pass yet Source for Levelrail, One-click service templates Partly app.json and Deploy button; no one-click service catalog Source for Heroku, One-click service templates
Autoscaling Active Beta: CPU, memory or request-rate scaling with cooldowns and reasons Source for Levelrail, Autoscaling Partly Web dynos only, Performance, Private or Shield tiers, scaled on a p95 response time target; not available for Fir apps Source for Heroku, Autoscaling
Sleep idle apps, wake on request (Levelrail ahead) Yesstable Opt in per app; stops after 5 minutes to 7 days idle and wakes on the next request. Verified live against a real Docker daemon and the real ingress Source for Levelrail, Sleep idle apps, wake on request Partly Eco web dynos sleep after 30 minutes without web traffic; other dyno types do not Source for Heroku, Sleep idle apps, wake on request
CLI and HTTP API (Levelrail ahead) Yes CLI and REST API documented; MCP server is beta Source for Levelrail, CLI and HTTP API Partly CLI and Platform API for apps and config; full parity not stated Source for Heroku, CLI and HTTP API
Deploy and alert notifications Active Webhook and SMTP email have live e2e; 15 vendor kinds (Slack, Discord, PagerDuty and more) are beta, tested against local fakes Source for Levelrail, Deploy and alert notifications Partly Threshold alerts on p95 response time or 5xx rate by email, PagerDuty or dashboard; Slack through ChatOps; webhooks via Platform API Source for Heroku, Deploy and alert notifications
MCP / AI assistant integration Yesbeta MCP server (beta) with over 240 tools in toolsets an agent enables on demand (256 at last count, 21 in the default session); in-app chat is behind a flag Source for Levelrail, MCP / AI assistant integration Yes Remote MCP server at mcp.heroku.com with OAuth login Source for Heroku, MCP / AI assistant integration
Runs on servers you own Yes Runs on Linux servers you provide Source for Levelrail, Runs on servers you own Not applicable
Open source license Yes Apache 2.0, one edition, no paid tier Source for Levelrail, Open source license Not stated in their docs
Declarative apply of the whole platform Activebeta YAML export, plan and apply from CLI, dashboard, MCP or CI, plus a Terraform and OpenTofu provider. Experimental, behind a flag Source for Levelrail, Declarative apply of the whole platform Partly Terraform listed as a deploy path and app.json for app setup; Platform API manages apps, pipelines, config vars and add-ons; no whole-platform declarative apply stated Source for Heroku, Declarative apply of the whole platform
Functions and one-off jobs Active Node, Python or Go handlers that sleep when idle and wake on the first request; scheduled and background calls with retries Source for Levelrail, Functions and one-off jobs Partly Worker dynos, one-off dynos and the free Scheduler add-on (10 minute, hourly or daily); no function-style runtime stated Source for Heroku, Functions and one-off jobs
Security 4
IAM, audit log and 2FA in the free edition (Levelrail ahead) Yesstable Allow/Deny IAM policies (stable, live e2e), passkeys and TOTP, and an audit log with a verifiable hash chain, CSV export and forwarding, all in the one edition Source for Levelrail, IAM, audit log and 2FA in the free edition Partly 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 Activebeta OIDC sign-in (17 named providers plus generic OpenID Connect) is on by default once configured. SAML and SCIM are beta, behind a toggle and off by default; SAML ran against Keycloak and SimpleSAMLphp in a local lab, not Okta or Entra Source for Levelrail, SAML or SCIM single sign-on Partly SAML SSO for Heroku Teams and Enterprise; accounts auto-provisioned on first IdP login, removal needs Support; SCIM not documented Source for Heroku, SAML or SCIM single sign-on
Audit log of every action (Levelrail ahead) Yes Every mutating request recorded; verifiable hash chain, CSV or NDJSON export, retention, streaming to a webhook or S3 bucket Source for Levelrail, Audit log of every action Partly Audit trail export (JSON archive per month) for Enterprise accounts only, needs manage permission Source for Heroku, Audit log of every action
Two-person deploy approvals Yesstable A different person with the deploy ability must approve; the requester cannot approve their own. Approval also works from Slack or Discord Source for Levelrail, Two-person deploy approvals Not stated in their docs

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

03

Move over from Heroku

Repos with a Dockerfile deploy as-is; managed databases cover common add-ons, but third-party add-ons are not replicated.

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

Questions about Levelrail and Heroku

Is Levelrail a good alternative to Heroku?

Yes. Levelrail does what Heroku does with a lighter footprint and more built in. Runs on Linux boxes you own, with no per-dyno or per-app fee. Eight managed database engines with scheduled, verified backups. Heroku Postgres is first party with backups and rollback; other engines come as add-ons. Dockerfile builds with readiness-gated cutover, not buildpacks. A read-only importer and a dry-run mode let you move without touching Heroku.

Can I move from Heroku to Levelrail?

Repos with a Dockerfile deploy as-is; managed databases cover common add-ons, but third-party add-ons are not replicated.

Is Levelrail ready to replace Heroku in production?

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

05

Keep exploring