Get started
How-to guides
Reference
Concepts
Self-host gallery
AppendixThe parts of Vercel people miss when they leave
Preview environments per PR
GitHub, GitLab and Bitbucket webhooks create a preview for each pull request and tear it down automatically when it closes.
One-click rollback
Prior images stay pinned, so going back means switching to an image that is still there, not rebuilding from an old commit.
Predictable cost
You pay for the servers you already rent, not per request or per seat. Metrics and logs stay on your own nodes.
Where the trade-offs are
Vercel is a managed cloud with a global edge network. Levelrail is the other model: your servers, your data, your bill.
Read the Vercel migration runbook
From Vercel to your own server
1
Inventory what Vercel holds
Env vars per environment, domains, redirects and cron jobs live in the dashboard, not your repo. The runbook has the checklist.
2
Deploy to Levelrail
Connect the repo, set env vars, and deploy a Dockerfile build. Check it on a temporary domain.
3
Cut DNS over
Lower TTLs first, switch, and keep Vercel as a fallback until you trust the new setup.
Frequently asked questions
Can Levelrail host Next.js?
Can Levelrail host Next.js?
Yes, as a container built from your Dockerfile. Build-time variables such as NEXT_PUBLIC_* are inlined at build, which the migration runbook covers.
Does it have serverless functions or an edge network?
Does it have serverless functions or an edge network?
No. It runs long-lived containers on your servers. If you need a global edge network, put a CDN in front.
Is there an importer for Vercel?
Is there an importer for Vercel?
No, migration from Vercel is manual. The runbook maps each Vercel concept to its Levelrail equivalent and lists the gaps.
What does it cost?
What does it cost?
The software is free under Apache 2.0. Your cost is the servers you run it on.