Are you looking for Vercel alternatives not charging per seat? Find out how Peon compares with self-hosting your Next.js and front-end apps in terms of cost, features, and drawbacks.
Reasons for switching from Vercel
Vercel provides an excellent developer experience, and for a single developer using the Hobby tier, it would be difficult to match it. But it gets tricky once the project grows to become a team, and the hobby becomes a product. At $20 per seat per month for the Pro tier, the price for a team of five developers would be $100 before handling even a single request. There are other expenses associated with overage in bandwidth costs at $40 for every 100 GB over the allotted limit.
In addition, there is another cost that occurs after some time. Vercel applications tend to become filled with platform-specific behaviors: serverless function timeout affects your API routes writing style, edge middleware bears the burden of work, and the database is placed in another hosting provider because Vercel does not have database hosting at all. When the time comes to move out of Vercel, you will not be moving just one application – you will be untangling three service providers.
The actual workloads that your team runs, such as a Next.js frontend, API routes, and a Postgres database, run smoothly on a simple VPS. The thing that you actually need from Vercel is not its infrastructure, but its workflow: git push, build, deploy, HTTPS, and immediate rollback. This workflow can be replicated using your own hardware resources.
What a self-hosted alternative needs to offer
There are many who would say, “Just use nginx with a systemd unit.” That fails to grasp the very reason for picking Vercel in the first place. The alternative should replicate the workflow, not just the execution. Be sure that the alternative you implement offers all the following:
Deployment through git push via webhooks from GitHub/GitLab, with live logs
Automatic HTTPS through Let’s Encrypt on custom domains, and also automatic renewals you don’t even have to think about
Zero downtime deployment, whereby the old deployment serves the traffic while the new one passes a health check
Rollback to any previous deployment with a click
Managing environment variables and secrets with encryption at rest
Logs during building and running available to the whole team, and not just those who have SSH access to the machine
Access management for the whole team, allowing a designer to check deploy status without having root access to the machine
Peon vs Vercel: how the numbers work out
Peon is $2 per project per month, with unlimited people on the team. You get your own server. Hetzner CX22 (2 cores, 4 GB RAM, 40 GB NVMe) goes for $4 a month and has plenty of headroom to host three to five production Next.js projects with a shared Postgres instance.
Walk through an example: a five-member team with three projects. At $100 a month on Vercel Pro, maybe another $20 to $50 on usage, and something like $25 on managed Postgres somewhere from Neon or Supabase Pro – you end up paying $150 a month, or $1,800 a year. The same setup on Peon? Three projects at $2 each, $8 VPS for some extra headroom, database on the same machine with nightly S3 backups – $14 a month, or $168 a year. The difference pays for an awesome team retreat.
Not just the amount but also the structure of the bills matters. With self-hosting, the monthly bill is fixed. No one worries if some big marketing campaign results in overage in bandwidth costs, and adding a sixth person is free.
Performance: serverless is not necessarily faster
The marketing of Vercel relies on the edge network, which is indeed very fast when dealing with static assets. However, most dynamic applications spend their latency budget doing round trips to the database, where the approach of using a single server usually beats the others: because your Next.js server and your Postgres run on the same server, a query that takes 15-40 ms across providers on serverless takes a fraction of a millisecond locally.
Moreover, you have no cold start issues at all. Your long-running Node process with an already established connection pool will answer the first request of the morning as quickly as the thousandth one. If you need edge caching for your static assets, setting up Cloudflare on your VPS will give you almost everything for free.
What you lose?
Honesty is key when making such comparisons, and thus the actual list follows below. You lose automatic multi-region failover; if your VPS service experiences an outage, your application will be down until it’s resolved or until you’ve restored your services using a different infrastructure (restore times with image-based deployment and external database backups are just under an hour). You lose preview deployments based on pull requests unless you use branch-based environments. You lose the ability to not care about the size of your disk or OS upgrades because a good platform does most of that for you.
In case you’re heavily using edge middleware, ISR revalidation at scale, or proprietary tools from Vercel (e.g. their KV and blobs), set aside a couple of days to implement them using Redis and compatible S3 storage. Most applications use much less proprietary functionality than the average developer thinks.
Migration Process Step by Step
Migrating Next.js from Vercel to a self-hosted Peon system can take half a day:
Add output "standalone" to next.config.js and a multi-stage Dockerfile (about 20 lines, copy-paste from any tutorial)
Get a VPS and set it up using Peon with Docker and a reverse proxy over SSH
Configure a Git-app service for your repo, copy environment variables
Deploy, test using a temporary subdomain, update DNS for the main domain
Database migration is done at last: use pg_dump on your old host and restore into Postgres on a server
When Vercel is still the right choice
In case your product truly targets interactive traffic from all around the world and needs sub-50 milliseconds response times around the globe, it becomes difficult to match that with one single VPS. In case your company is completely unwilling to handle any kind of server, even an extremely automated one, paying the price of management might seem like a fair deal. For a weekend project, the Hobby plan is free anyway.
Otherwise, for any other purpose, whether it's the dashboard, SaaS product, client website, or any other thing you do, self-hosting the platform will give you the same workflow with almost one-tenth of the costs.
Top comments (0)