Skip to main content
The Heroku workflow on a server you control Git push to deploy, managed databases, automatic HTTPS, logs and rollback, running on Linux boxes you own instead of per-dyno billing. Get started | View on GitHub

​
What carries over from Heroku

Git push to deploy

Connect GitHub, GitLab or Bitbucket and every push to a branch builds and deploys with a readiness-gated cutover.

Managed databases

Postgres, Redis, MySQL, MongoDB, MariaDB, KeyDB, Dragonfly and ClickHouse as first-class resources, with scheduled backups and automatic verification.

Logs, metrics and alerts

Full-text log search, node-local metrics and alerts to Slack, Discord, email, PagerDuty and more, with no add-on subscriptions.

​
Heroku and Levelrail

Heroku is a managed platform. Levelrail is the same workflow on infrastructure you operate. Read the full comparison

​
A first deploy

1

Pick a server

Any Linux box with Docker works, or provision one from Hetzner, DigitalOcean, AWS, Azure or GCP.
2

Install and connect git

Run the install script, open the dashboard, and connect a repository.
3

Add a database and deploy

Create Postgres or Redis, link it to the app, and push.

​
Frequently asked questions

Not deeply. If your repo has a Dockerfile, it deploys. Levelrail handles the runtime, TLS and routing.
Managed databases, built-in metrics and logs, alerting channels and scheduled backups cover the common ones. Third-party add-ons are not replicated.
You are, since you run the servers. Alerts, crashloop detection and a status page are built in to make that manageable.
Yes, Apache 2.0, one edition.

​
Stop paying per dyno

Try it on one small server and move a project across when it feels right. Get started | View on GitHub
Last modified on October 12, 2026