I still had three apps: Certifstudio (online certificates), CVMalin (a CV builder) and Blockforge (licensed UI components). All of them have a database, accounts, payments and e-mail. They needed a real server. But I didn't want to go back to SSH-ing in and doing everything by hand.
My constraint was simple: keep the Vercel experience, the git push that goes live, without a bill that grows with every project.
A VPS is an EC2 instance
A VPS (Virtual Private Server) is a virtual computer rented in a data centre: always on, with a fixed IP address. If you've used an EC2 instance on AWS, it's exactly the same idea: a Linux machine of your own that you reach over SSH.
I took a plan with 2 virtual CPUs, 8 GB of memory and 100 GB of disk, in France, for a little over €20 a month. A fixed price: one more project costs nothing as long as the machine copes. Today, with three apps, it uses barely a quarter of its memory.
What I used to do on EC2
To put an app online on a bare machine, I did everything myself:
- SSH in,
git pull; npm install,npm run build;- restart the process with pm2;
- configure nginx for the domain;
- run certbot for the HTTPS certificate;
- and start again on every update, for every project.
It works, but it's manual, repetitive and fragile: a wrong Node version, a port already taken, an expired certificate, and it's down.
Docker in one sentence
A Docker container is a box that holds an app with everything it needs: the right Node version, Chromium to generate PDFs, and so on. Several boxes run on the same machine without stepping on each other. One can use Node 22 while another uses something else.
Coolify, a Vercel you install yourself
Coolify is free, open-source software you install on the VPS. It's a web interface (and an API) that does automatically everything I used to do by hand:
| Task | By hand | With Coolify |
|---|---|---|
| Get the code | git pull over SSH | linked to GitHub, automatic on every push |
| Build | npm run build | a Docker image, built for me |
| Run | pm2 or systemd | one container per app, restarted if it crashes |
| Domain and HTTPS | nginx + certbot | I type the domain, the certificate follows |
| Update | downtime during the restart | the new container is ready before the old one stops |
Here's what happens now when I push code:
One server, dozens of sites
It's the question I get the most: how can three sites live on a single IP address? The answer is a reverse proxy. On my server it's Traefik, installed by Coolify.
Every app listens on the same port, but each inside its own box. Only one door is open to the world. Behind it, Traefik plays switchboard: it reads the name the visitor asked for and hands the request to the right box. Here's the full path of a request, from your browser to the outside services:
A few details in that diagram are worth a pause:
- nobody talks to the server directly: everything goes through Cloudflare first (in part 4 we'll see why that matters so much);
- the databases aren't on the VPS. They live with a managed Postgres provider, in Europe. If the server disappears, no data is lost: you just restart the apps elsewhere;
- data leaves encrypted towards specialised services: e-mail sending, payments, error tracking, backup storage.
Moving three apps without downtime
The method, the same for each app:
- create it on the VPS with a test address;
- copy its secrets (database, service keys) without ever printing them;
- test everything, then have a human test too;
- first point DNS at the server, then add the real domain in Coolify. In that order, the HTTPS certificate comes on the first try;
- keep the old version a few days, while old DNS answers expire;
- delete the test address.
Since the databases live elsewhere, the old and new versions saw the same data during the switch. Nothing to copy, nothing lost.
One app was sending its login e-mails with a test key, which only sends to the account owner's address. On the server everything seemed fine… because I was testing with my own address. A real user would have been locked out. Lesson: before a switch, always test with an address that isn't yours.
What I gained, what I lost
Gained: a fixed cost, no request limits, any language, and databases or services installable in one click.
Lost: peace of mind. On Vercel, someone else handled security, updates, backups and monitoring. Now that's me. Which is where the last two parts of this series begin: securing the server, then keeping it standing.
