# Self-hosted Vercel alternative: what you keep, lose and pay

> A self-hosted Vercel alternative compared: previews, CDN, functions and images, when Vercel pricing hurts, and Coolify, Dokploy, CapRover or a panel.

Source: https://zopanel.net/blog/self-hosted-vercel-alternative  
Updated: 2026-11-09

## Key takeaways

- A self-hosted Vercel alternative keeps push-to-deploy, HTTPS and server rendering, but you lose Vercel's global CDN, automatic preview deployments and scale-to-zero functions unless you rebuild them.
- Vercel's Hobby plan is for personal, non-commercial use only, and Pro costs $20 per developer seat per month plus usage above the included amounts at the time of writing (November 2026).
- Coolify and Dokploy are self-hosted PaaS tools with pull request previews; CapRover is a simpler PaaS; a hosting panel such as ZoPanel adds PHP sites, email and DNS but no previews.
- On a VPS the bill is fixed by the server size, so traffic spikes slow the app down instead of raising the invoice.

A self-hosted Vercel alternative is a tool that gives you Vercel's "push to Git, it goes live" workflow on a server you rent yourself: Coolify, Dokploy or CapRover if you want a self-hosted PaaS, or a hosting panel with Git deploy such as ZoPanel. You keep push-to-deploy, HTTPS and server-side rendering at a fixed monthly price; you give up Vercel's global CDN, automatic preview deployments and functions that scale to zero, and you become the person who runs the server.

This guide is for people who built an app with Cursor, Claude Code, Lovable, Bolt or v0, put it on Vercel because that was the default, and now wonder whether to move. Next.js specifics are in [deploying Next.js to a VPS](/blog/deploy-nextjs-to-vps), and the PaaS-versus-panel question in [Coolify vs a hosting control panel](/blog/coolify-vs-hosting-control-panel). Facts about other products come from their own docs at the time of writing (November 2026).

## What does Vercel actually give you?

From Vercel's own documentation, this is what you are paying for:

- **Preview deployments.** By default Vercel creates a preview deployment when you push to a branch that is not your production branch, open a pull request, or run the CLI without `--prod`. Each one gets its own URL, linked from the pull request ([Environments docs](https://vercel.com/docs/deployments/environments)).
- **A global CDN.** Vercel says its CDN runs 126 points of presence across 51 countries, with 19 compute regions behind them, DDoS mitigation on every deployment and caching rules generated from your framework's build output ([CDN overview](https://vercel.com/docs/cdn)).
- **Serverless functions.** Vercel Functions handle each request as an invocation, scale automatically and scale down to zero when there is no traffic. Node.js functions run in Washington, D.C. (`iad1`) by default unless you choose another region ([Functions docs](https://vercel.com/docs/functions)).
- **Image optimisation.** Images rendered with a framework's `Image` component are transformed on demand and cached on the CDN, billed per transformation and cache read or write ([Image Optimization docs](https://vercel.com/docs/image-optimization)).

## What do you keep and what do you lose on a VPS?

| Vercel feature | On one self-hosted VPS | How much it matters |
| --- | --- | --- |
| Push to deploy | Kept. Every option below deploys on a Git push. | High: this is the workflow people actually want |
| HTTPS | Kept, with free Let's Encrypt certificates | High |
| Server rendering, API routes, streaming | Kept: the app runs as a normal long-lived server | High |
| Image optimisation | Kept for Next.js: `next start` uses `sharp` on your server ([details](/blog/deploy-nextjs-to-vps)) | Medium: it costs your CPU instead of a per-image fee |
| Preview deployment per branch or pull request | Lost, unless you use a PaaS that has them (Coolify, Dokploy) or keep a separate staging site | Medium for teams, low for one person |
| Global CDN and edge caching | Lost. Content is served from one location unless you add a CDN in front | Depends on where your visitors are |
| Functions that scale to zero and out | Lost. One server has a fixed size; a spike slows it down | Low for most small apps, high for spiky traffic |
| No servers to patch | Lost. OS updates, backups and monitoring are yours | High if nobody on the team wants the job |

For a single app with steady traffic in one region, you lose little that users notice. For a team that reviews every pull request on a preview URL, or an app with very spiky traffic, Vercel's model is genuinely better. A [Cloudflare plan in front of a VPS](/blog/cloudflare-with-vps) closes part of the CDN gap for static assets.

## When does Vercel's pricing become the reason to move?

At the time of writing (November 2026), [Vercel's pricing page](https://vercel.com/pricing) lists three plans:

| | Hobby | Pro | Enterprise |
| --- | --- | --- | --- |
| Price | $0 | $20 per developer seat per month, including $20 of usage credit | Custom |
| Allowed use | "Personal, non-commercial use" | Commercial | Commercial |
| Fast Data Transfer | 100 GB per month | 1 TB per month, then from $0.15 per GB | Custom |
| CDN requests | 1M per month | 10M per month, then from $2 per million | Custom |
| Function invocations | 1M per month | From $0.60 per million | Custom |
| Image transformations | 5K per month | From $0.05 per thousand | Custom |
| Above the limits | Not possible; Hobby cannot buy more usage | Billed, with a default $200 on-demand budget you can change, and an optional hard limit that pauses projects | Custom |

Three situations make people look for a self-hosted Vercel alternative:

1. **The app starts making money.** Hobby is for personal, non-commercial use, so a client project, a SaaS with paying users or a shop needs Pro.
2. **The team grows.** Pro is priced per developer seat. Four developers is $80 a month before any usage.
3. **Traffic or images grow.** Usage above the included amounts is billed per GB, per million requests and per thousand image transformations, so the bill follows your traffic.

### Vercel vs VPS cost: a worked example

Take one commercial app serving 3 TB a month to visitors. On Vercel Pro, the first 1 TB of Fast Data Transfer is included and the other 2 TB cost from $0.15 per GB, so at least about $300 a month for data transfer alone, plus $20 per seat, plus any requests, functions and images above the included amounts. For comparison, Hetzner lists its CX23 cloud server (2 vCPU, 4 GB RAM, 40 GB NVMe, 20 TB of traffic) at €5.99 a month excluding VAT on its [Cost-Optimized plans page](https://www.hetzner.com/cloud/cost-optimized/), though the page also marked it as currently unavailable when we checked.

That comparison is unfair to Vercel: the VPS has no CDN, no previews and no one on call. But it shows the shape of the decision. On Vercel the bill grows with traffic; on a VPS the bill is fixed by the server size, and what grows is the load and the work of keeping the server healthy.

### And Netlify?

[Netlify's pricing](https://www.netlify.com/pricing/) moved to credits at the time of writing: Free has 300 credits a month with a hard limit, Personal costs $9 a month for 1,000 credits, and Pro costs $20 a month for 3,000 credits with unlimited members. Its [credit table](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/credit-based-pricing-plans/) charges 15 credits per production deploy, 20 credits per GB of bandwidth and 10 credits per GB-hour of function compute, while deploy previews and branch deploys are not metered. For a vibe coder who ships often, that matters: 20 production deploys a month use the whole Free allowance before a single visitor arrives.

## Which self-hosted Vercel alternative should you choose?

Four common choices, described from their own documentation:

| | Coolify | Dokploy | CapRover | ZoPanel (hosting panel) |
| --- | --- | --- | --- | --- |
| What it is | Self-hosted PaaS for apps, databases and services in Docker ([intro](https://coolify.io/docs/get-started/introduction)) | Self-hosted PaaS, Docker Compose and Swarm ([GitHub](https://github.com/Dokploy/dokploy)) | PaaS on Docker Swarm with nginx and Let's Encrypt ([README](https://github.com/caprover/caprover)) | Hosting control panel with Git deploy, PHP sites, email and DNS ([Git deploy](/docs/git-deploy)) |
| Deploy on Git push | Yes | Yes | GitLab push webhook or a GitHub Action ([CI/CD docs](https://caprover.com/docs/deployments/ci-cd)) | Yes, signed webhook from GitHub, GitLab or Gitea |
| Pull request previews | Yes ([preview deploys](https://coolify.io/docs/applications/ci-cd/github/preview-deploy)) | Yes ([preview deployments](https://docs.dokploy.com/docs/core/applications/preview-deployments)) | Not in its docs | No |
| Needs a Dockerfile | No; also Dockerfile, Compose or image | No: Nixpacks by default, also Dockerfile or buildpacks ([build types](https://docs.dokploy.com/docs/core/applications/build-type)) | A `captain-definition` file | No: framework detection; Dockerfile or public image optional |
| How the app runs | Container | Container | Container | Process of a hosting account under systemd limits, or one container per site |
| Mailboxes, DNS, PHP hosting | Not among documented features | Not among documented features | Not among documented features | Built in |
| Minimum server | 2 cores, 2 GB RAM, 10 GB disk ([install](https://coolify.io/docs/get-started/installation)) | 2 GB RAM, 30 GB disk ([install](https://docs.dokploy.com/docs/core/installation)) | Docs warn 512 MB may not be enough for builds ([get started](https://caprover.com/docs/get-started.html)) | 1 GB RAM ([requirements](/docs/requirements)) |
| Price | Self-hosted free; Cloud $5 a month for 2 servers + $3 per extra ([pricing](https://coolify.io/pricing/)) | Open source; Cloud from $4.50 per server a month ([pricing](https://dokploy.com/pricing)) | Free, Apache 2.0 | Free for 10 websites; unlimited from $49 a year ([pricing](/pricing)) |

In short: Coolify or Dokploy if you want the Vercel experience with previews and everything is a container; CapRover for a few simple Docker apps; a hosting panel if the app sits next to WordPress, a PHP shop, mailboxes or other people's sites. Do not install a PaaS and a panel on the same server: both want ports 80 and 443.

## Is self-hosting a good idea for vibe coders?

It depends on what you are willing to own. The deploy is no longer the hard part; the server is: security updates, backups, a firewall and an eye on disk and memory. Our [Ubuntu VPS security guide](/blog/secure-ubuntu-vps) covers the first hour of that work.

AI-written code adds one more point: you have probably not read every line, so it should run with limited rights (its own Linux user, CPU and memory limits, no writes outside its folder). Vercel isolates that for you; on a VPS, check that your tool does too. The [vibe coding security checklist](/blog/vibe-coding-security-checklist) lists what to look for.

[Deploying a vibe-coded app](/blog/deploy-vibe-coded-app) walks through the options from the app's side.

## How does push-to-deploy work on ZoPanel?

ZoPanel's Git deploy does the parts of Vercel that a single server can do well. From the [Git deploy docs](/docs/git-deploy):

1. **Create a website of type Git deploy** with the repository URL, branch and, for a monorepo, the root directory. For a private repository, add the panel's **deploy key** to the repository as a read-only key and use the `git@…` URL.
2. **Framework detection.** ZoPanel reads the repository and fills in install, build and start commands for Next.js, Nuxt, Remix, SvelteKit, Astro, Vite, NestJS, Express, Django, FastAPI, Flask, Laravel, Rails, Go and others. The package manager comes from the lock file and the Node.js version from `.nvmrc`, `.node-version` or `engines.node`. Static exports are served as static sites.
3. **Environment variables.** Paste your `.env` once; the variables are available at build time and at runtime, and `PORT` is set automatically.
4. **A sandboxed build.** Each deploy builds in a new release folder as the hosting account, inside its CPU and memory limits, unable to write outside its home.
5. **A health-checked switch.** A server app starts in the idle slot and must answer the health check path with a status below 500 within 90 seconds. Only then does nginx switch to it. If it fails, the previous release keeps serving and the owner is notified.
6. **Deploy on push.** Turn on **Deploy when main is pushed**, copy the payload URL and secret, and add the webhook in GitHub, GitLab or Gitea. ZoPanel verifies GitHub's `X-Hub-Signature-256` signature or the GitLab and Gitea token header and never accepts the secret in the URL. Only the configured branch deploys.
7. **Rollback.** The last 5 releases are kept; a rollback goes through the same health-checked switch, so there is no downtime.

What it does not do, plainly: there are no preview deployments, no global CDN and no autoscaling. The closest thing to a preview is a second website that tracks a `staging` branch. You run the server, and each website counts toward the plan's limit. Databases (MariaDB, PostgreSQL, MongoDB, Redis) and free SSL live in the same panel; more on the vibe coding workflow is on [the vibe coding page](/vibe-coding).

## Conclusion

A self-hosted Vercel alternative makes sense when the app is commercial, the team is growing or the traffic bill keeps rising, and when you are happy to own a server in exchange for a fixed price. If you rely on preview deployments, pick Coolify or Dokploy. If the app lives next to PHP sites, email or customers, pick a hosting panel. If you rely on a global CDN and instant scaling, stay on Vercel; it is good at exactly that.

To try the panel route, install [ZoPanel's Free plan](/pricing) (10 websites, 10 databases, 3 hosting accounts, no time limit) on a test VPS, point it at your repository and push. The [auto deploy from GitHub guide](/blog/git-auto-deploy) explains the webhook side in more depth.

## FAQ

### What is the best self-hosted alternative to Vercel?

It depends on what else runs on the server. Coolify and Dokploy are the closest to Vercel because they have pull request previews and run everything as containers. CapRover is simpler. A hosting panel such as ZoPanel fits when the app shares a server with PHP sites, email or customers, but it has no preview deployments.

### Can I use Vercel's free plan for a commercial project?

No. Vercel's pricing page describes Hobby as being for personal, non-commercial use, with fixed limits and no option to buy more. A commercial project needs Pro, which at the time of writing (November 2026) costs $20 per developer seat per month plus usage above the included amounts.

### Is a VPS cheaper than Vercel?

For steady traffic, usually yes, because a VPS has a fixed price and includes far more bandwidth than Vercel Pro's 1 TB. It is not a like-for-like comparison: Vercel includes a CDN, previews, autoscaling and operations, while on a VPS you do the operations yourself.

### Do preview deployments work when I self-host?

Not by default. Coolify and Dokploy document pull request previews. CapRover's docs do not mention them, and ZoPanel does not have them; with ZoPanel you can run a separate staging website from another branch instead.

### Does ZoPanel have a global CDN?

No. ZoPanel serves sites from your server. You can put a CDN such as Cloudflare in front of it for static assets and DDoS protection.
