Build and deploy
Connect GitHub, GitLab, Bitbucket or Gitea. Pushes build a Dockerfile with BuildKit and cut traffic over only when the readiness probe passes.
Self-host Next.js
Build from your Dockerfile, get HTTPS, preview environments per pull request, a managed database and one-click rollback, all from a git push.
curl -fsSL https://levelrail.com/install.sh | sudo sh
Connect GitHub, GitLab, Bitbucket or Gitea. Pushes build a Dockerfile with BuildKit and cut traffic over only when the readiness probe passes.
Env vars are encrypted per app. NEXT_PUBLIC_* values are inlined at build time, so set them before the build, which the migration runbook covers.
Create Postgres or Redis as a managed resource with scheduled, verified backups and link it to the app.
What changes when you leave a managed platform.
A standard multi-stage Next.js Dockerfile with output set to standalone keeps the image small.
Set build-time variables first, then runtime secrets.
Point DNS at the server and Caddy issues and renews the certificate.
A preview environment deploys and is torn down when the pull request closes.
It runs your container, so anything that runs in a Node container works. Levelrail does not run a separate Next.js-specific runtime.
A pull request opened or updated deploys a preview. Closing the pull request tears it down, whether or not it merged.
Yes. A single node is the best tested path.
Yes, a runbook for moving a Vercel-hosted Next.js app, with an inventory, a cutover plan and the gaps.
Start with a side project and move the rest when you trust it.