Part 1 - Vercel to VPS

Vercel, it feels like magic.

You push to Git, and suddenly your site is live and globally available. No servers. No configs. No stress.

But at some point, you decided to move out of Vercel. Not because Vercel is bad or more pricey, but because production means more than “it works”.

But first, why move from a managed platform to a VPS?

Managed platforms like Vercel and Netlify manage all the behind infra setup, so developers can ship faster, but a VPS optimizes for control.

Here are a few things that might trigger the shift:

Cost:

Managed platforms are cheap at low traffic, and expensive at scale.

A VPS has a fixed monthly cost, regardless of traffic patterns.
Infrastructure Control:

On managed platforms:
- You don’t control the server
- You don’t control process lifecycles
- You don’t control the network
On a VPS:
- You choose how requests flow
- You decide how apps restart
- You define how failures are handled

All this is a fine reason. But we're moving for the love of the game. Game? yes to learn a thing or two about the production system.

So how the production setup is done in VPS?

A VPS-based production app usually follows this this request flow:

User → DNS → Nginx → Node / Next.js → PM2

User → DNS:

When a user sends a request, the first stop is DNS (Domain Name System).

DNS is responsible for:

DNS → Nginx

Once DNS resolves the domain, the request reaches your server and is handled by Nginx.

Think of Nginx as the front door of your application.

It handles:

Nginx sits in front of your app to absorb traffic, handle networking efficiently, and protect your Node process from direct exposure.

Nginx → Node / Next.js

Nginx forwards the request to your Node.js / Next.js application via a reverse proxy.

It handles:

Node / Next.js → PM2

Your application is managed by a process manager such as PM2.

PM2 ensures that:

Without a process manager:

TL;DR:

Get in touch