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

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