Install
Markdown
Ask AI
Share

Best Self-Hosted Vercel Alternatives in 2026

Five self-hosted Vercel alternatives ranked for git deploys, previews and TLS on your own servers with no per-seat pricing: Levelrail, Coolify, Dokploy, CapRover, Dokku.

Markdown
Ask AI
Share

The best self-hosted Vercel alternative for most teams is Levelrail, followed by Coolify, Dokploy, CapRover and Dokku. All five give you git deploys and automatic TLS on a server you control. They differ on previews, rollback, observability and how much you run next to them. None of them gives you a global edge network, and this post says so up front.

A disclosure: Levelrail is our product, so the ranking is ours. We kept every claim about the other four to facts from their own documentation, each linked, and we note where a documented gap exists rather than inferring one. The data behind the tables was last checked on 2026-11-18.

Why people leave Vercel for their own servers#

The usual reason is the bill. According to Vercel’s pricing page, Hobby is free with one developer seat and usage caps. Pro is $20 per month plus $20 for each developer seat, and it includes a $20 usage credit, 10M CDN requests and 1 TB of transfer. The price grows with the size of your team and with traffic.

On your own server the cost is the server. A small VPS can run several apps with previews, and adding a teammate costs nothing. The tradeoff is that you own updates, backups and uptime, and you give up the edge network, edge runtime and image optimization that Vercel provides. If you need those, keep Vercel for the front end and self-host the rest.

Quick pick#

RankProjectBest forStated min RAMLicense
1LevelrailPreviews, rollback and observability in one binary1 GB (about 200 MB idle, measured once)Apache 2.0
2CoolifyA large one-click catalog over SSH2 GBApache 2.0
3DokployDocker Swarm users who want a dashboard2 GBApache 2.0 plus a source-available folder
4CapRoverA long-running Swarm panel with an app store1 GiBApache 2.0, some Pro features reserved
5DokkuHeroku-style git push on one box1 GB (docker scheduler)MIT

A note on the RAM column: the stated minimums are what each project’s install guide asks for. The Levelrail “about 200 MB” figure is one measurement of the idle control plane, shown on the measured page. They are different kinds of numbers, so do not subtract one from the other.

1. Levelrail#

Levelrail is a single Go binary that runs your apps in Docker, with no Kubernetes. It deploys on push from GitHub, GitLab and Bitbucket, creates a preview environment for each pull request, and serves HTTPS through an embedded Caddy ingress. Install it with curl -fsSL https://levelrail.com/install.sh | sudo sh, or follow the install guide and the installation docs.

Where its documented rows differ from the other four, they are these:

  • Previews are labeled stable on GitHub and beta on GitLab and Bitbucket, per the previews docs.
  • Readiness-gated deploys. Traffic cuts over only after the readiness probe passes. This is live-tested on one node, and multi-node is beta (deploying apps).
  • Rollback is labeled stable. Prior images are pinned so cleanup cannot remove them, and a 5xx spike or crashloop after cutover rolls back automatically (live-tested). The latency signal is beta (rollback docs).
  • Observability in the core. Node-local metrics at 15 seconds, full-text log search and crashloop diagnosis that surfaces the last log lines, with no extra stack to install (observability docs).
  • Access control in the one edition. Allow and Deny IAM policies (stable, live end-to-end tested), passkeys, TOTP and an audit log with a verifiable hash chain (access control).
  • A template catalog. 592 entries, 583 active, of which 346 are proven on a real engine and 246 are previews without that pass yet (templates status, browse them at /templates/).

The honest gaps: TLS is Active. Certificates are self-signed by default, and public ACME (HTTP-01) has one recorded run on a live VPS. Renewal near expiry and DNS-01 wildcards are not exercised live, and CAs that need EAB are unsupported (domains and ingress). Multi-node is also Active: join, cordon and drain are verified across two local Docker daemons, while the WireGuard mesh and cross-host transport are still unverified. There is no edge network or edge runtime. The feature status page tracks every label.

Moving from another platform is covered by read-only importers for Coolify, Dokploy and CapRover. See /migrate/coolify/, /migrate/dokploy/ and /migrate/caprover/. The page Levelrail vs Vercel maps each Vercel concept to its equivalent and lists the gaps.

Verdict: the pick if you want previews, rollback, logs and metrics from one install on one server.

2. Coolify#

Coolify is built around a large one-click service catalog and a polished dashboard, and it manages servers you already have over plain SSH.

  • It asks for 2 GB of RAM, 2 CPU cores and 10 GB of disk, per its installation guide.
  • The license is Apache 2.0 with no paywalled features when self-hosted. Cloud starts at $5 per month with 2 servers, plus $3 per additional server.
  • Previews exist per pull request, and the full UI needs a GitHub App (preview docs).
  • Rollback redeploys a retained older image, with configurable retention (rollback docs).
  • Metrics are historical charts from Sentinel. The docs say log queries and dashboards need an external system (monitoring overview). Its rolling-update page says there is no zero-downtime guarantee (rolling updates).

The architecture is three base containers (app, PostgreSQL and Redis), per how Coolify works. See the Levelrail vs Coolify comparison for each row with its source.

Fit: built around a very large template catalog and SSH-only server management.

3. Dokploy#

Dokploy is a Docker Swarm based platform with a modern dashboard and an official MCP server.

  • It lists 2 GB of RAM and 30 GB of disk, with no CPU minimum stated (installation).
  • The license is Apache 2.0 plus a source-available /proprietary folder, so read it before relying on the code.
  • Previews per pull request are documented for GitHub only (preview docs).
  • It has metrics with threshold alerts, real-time logs and Vector shipping to external providers. Log search is not stated (features).
  • Pricing: self-hosted is free. Cloud Hobby is $4.50 per month per server, and Enterprise adds SSO, SCIM and audit logs. Audit logs are Enterprise only (enterprise docs).

Importing an existing setup is covered at /migrate/dokploy/, and the Dokploy comparison has the full table.

Fit: built around Docker Swarm, with multi-node scheduling and rolling updates coming from Swarm itself.

4. CapRover#

CapRover is a long-running, Swarm-based platform with a one-click app store and a CLI.

  • It states 1 GiB of RAM and 5 GiB of free disk, with no CPU minimum (get started).
  • The license is Apache 2.0 with some Pro features reserved. The core is free and Pro features are paid.
  • Metrics come from optional NetData. App and build logs can be viewed, and no log search is documented (NetData docs).
  • Stateless apps default to start-first updates, and apps with mounted data default to stop-first, so it does not promise interruption-free updates (scaling docs).
  • 2FA and login alerts are Pro, and no roles or audit log are documented (CapRover Pro).

An importer for it is at /migrate/caprover/, and the CapRover comparison lists the rest.

Fit: built around a simple Swarm panel with a large install base and an app store.

5. Dokku#

Dokku is the classic Heroku-style platform for one machine: you git push and it builds with buildpacks.

  • It states 1 GB of RAM for the docker scheduler and 2 GB per node for the optional k3s scheduler, with no CPU minimum (installation).
  • The license is MIT. Dokku Pro is a paid add-on with a web UI and JSON API, listed at $849 one time (early bird pricing).
  • GitHub push webhook deploys exist only in paid Dokku Pro 1.4.0, and no GitLab or Bitbucket webhooks are documented (Pro release notes).
  • Compose files are not a documented deploy input. The listed methods are git push, Dockerfile, Docker image and buildpacks (application deployment).
  • Database plugins create databases, but backups are a manual export with no scheduling (backup and recovery).

There is no Dokku importer. Deploy the same repositories and recreate environment variables and domains. The Dokku comparison covers the details.

Fit: built around the simplest possible Heroku workflow on a single server.

How to try it#

Start with a throwaway VPS and the default install. Connect a repository, open a pull request and check that the preview URL appears and gets a certificate. Then break a deploy on purpose and see what each platform does. That test shows more than any table.

If you want the full per-feature breakdown, see the alternatives page. For the broader field including hosted platforms, read Self-hosted Vercel and Heroku alternatives, compared.

Frequently asked questions#

What is the best self-hosted Vercel alternative?

For git deploys, pull request previews and automatic TLS on your own server, we rank Levelrail first. It is our product, so check the claims against the sources linked in this post. Coolify, Dokploy, CapRover and Dokku are the established alternatives, and each is listed with its own documented facts. None of them includes Vercel's global edge network.

How much does Vercel cost compared with self-hosting?

Vercel's pricing page lists Hobby as free with one developer seat and usage caps. Pro is $20 per month plus $20 per developer seat, with a $20 usage credit, 10M CDN requests and 1 TB of transfer included. A self-hosted platform replaces that with the cost of the server you rent, and all five projects here have a free self-hosted edition.

Can I run these on a small VPS?

Stated minimums are 1 GiB for CapRover, 1 GB for Dokku with the docker scheduler, and 2 GB for Coolify and Dokploy. Levelrail's documented minimum is 1 vCPU and 1 GB of RAM. Those are installation requirements. Levelrail's idle control plane measured about 200 MB in one run, which is a different kind of number.

Do self-hosted platforms replace Vercel's edge network?

No. A single server serves from one location, and none of these projects ship an edge runtime or CDN. Put a CDN in front of your server if you need global caching. What you get instead is a flat server cost, data on hardware you control, and any container workload.

Next steps

Keep reading

Leaving Vercel? Self-host it instead Leaving Vercel? Self-host it instead

comparison 6 min read

Self-Hosted Vercel and Heroku Alternatives, Compared

Coolify, Dokploy, CapRover, Dokku and Levelrail next to Vercel, Heroku and Railway: what each does well, where it fits, and which to pick for your setup.

  • Self-hosting
  • Comparison
  • PaaS