Decent Newsroom
Sign In

Open source Vercel alternatives, compared by what they actually deploy

By Peon October 28, 2026
A look at self-hostable alternatives to Vercel, grouped by the kind of workloads they handle well.

“Open source Vercel alternative” gets used for very different tools. Some focus on static sites and frontends, some on any Docker container, some on Kubernetes. Grouping them by what they deploy makes the choice much easier.

What Vercel actually gives you

Before replacing it, list what you use:

  • Git push deploys with preview URLs per pull request
  • Framework aware builds, especially for Next.js
  • Serverless and edge functions
  • A global CDN
  • Environment variables per environment
  • Analytics and image optimization

Self-hosted tools cover the first, second and fifth points well. Edge functions and a global CDN are harder to replicate on your own servers, though putting a CDN in front of a VPS covers most needs.

Group 1: Docker based self-hosted PaaS

These run any containerized app on your servers, including Next.js in standalone mode, APIs, workers and databases.

  • Coolify: large community, many one click services
  • Dokploy: Compose and Swarm focused, clean UI
  • CapRover: mature and simple, Swarm based
  • Dokku: Heroku style CLI, single server
  • Peon: Git deploys, previews, team roles, audit logs and an MCP server

Good fit if you have more than frontends: backends, queues and databases on the same servers.

Group 2: Kubernetes based platforms

Tools that build a PaaS layer on Kubernetes. Powerful, but they assume you want to run a cluster. Good fit for platform teams, heavy for small teams.

Group 3: Static and frontend focused

Static site servers and tools that build and serve frontends with previews. Good fit when your backend is elsewhere and you mostly ship static or prerendered sites.

Next.js specifics

Next.js features like ISR, middleware and image optimization run fine in a Node server container. What you lose compared to Vercel is the automatic edge distribution. For most apps serving one region, a single well located server plus a CDN is faster than you would expect.

Questions to decide

  1. Do you need backends and databases, or only frontends?
  2. How many people need access, and with what permissions?
  3. Do you need preview deployments per pull request?
  4. Single server or multiple?
  5. How much do you care about a UI versus a CLI?

Migration path

Most teams move one project at a time. Start with an internal tool or a marketing site, set up previews and domains, and only then move the main app. Keep the Vercel project around until DNS has been switched and verified.

A longer comparison of each tool, with pros and cons, is in this roundup of open source Vercel alternatives.

Disclosure: I work on Peon, one of the tools listed, so I have tried to describe the others fairly.

#vercel #opensource #selfhosting
Write a comment