Push to git and get a running app with logs, metrics and rollback on servers you own. Here are the jobs it is built for, each with its scope and maturity marked.
Seven jobs, one install
-
Next.js and Node apps
Git-driven deploys for containerized web apps on your own server.
- 4git hosts: GitHub, GitLab, Bitbucket, Gitea
- StablePR previews on GitHub
-
Databases with backups
Managed databases with scheduled, verified backups on your own storage.
- 13database engines
- Weeklyrestore drills by default
-
Side projects on one VPS
A handful of projects on one server, without per-service platform fees.
- 2binaries: control plane and agent
- 15 smetrics resolution, kept on the node
-
Internal tools
Dashboards, automation and wikis, with roles and an audit trail.
- 580+templates in the catalog
- TOTPtwo-factor sign-in, plus OAuth and OpenID Connect
-
Agencies and many clients
Scoped access, an audit trail and per-client nodes for client work.
- app:nameIAM policies scoped to one app or database
- Denyan explicit Deny always wins, even over root
-
Homelab and mixed servers
A home server, a VPS and a cloud VM under one control plane.
- Outboundonly: agents open the connection, managed machines accept none
- 0SSH keys stored on managed servers
-
AI agents with MCP
An MCP server over the platform API, with read-only and confirm-gated modes.
- BetaMCP server status
- OffWrite tools until you pass an allow-write flag
When something else fits better
A few jobs sit outside what it covers. If one is yours, here is where to look instead.
For edge functions, ISR or a managed global network, use a hosted platform. Levelrail runs containers on your servers, and a CDN in front of it covers edge caching.
For automatic bin-packing across a large cluster, Kubernetes is the better fit. ${brand.name} places apps on the nodes you pick and has no scheduler.
To resell hosting to customers, you need billing. ${brand.name} has no metering or billing layer, so pair it with a billing system of your own.
Common questions
What is Levelrail used for?
Levelrail turns Linux servers you own into a private cloud. Common uses are self-hosting web apps from git, running databases with verified backups, side projects on one VPS, internal tools, agency client work, a homelab, and reading logs and diagnosing apps from an AI agent over MCP.
Can I run Levelrail in production?
A single node is the most tested path. Multi-node is labelled beta. Each use case page marks what is stable and what is beta, and the docs feature status page has the evidence behind each label.
Start with one server
One command installs the control plane. Apache 2.0, no license key.
curl -fsSL https://levelrail.com/install.sh | sudo sh