Every app does the same nine jobs. What changes is whether you rent the tool, own it, or get forced off it. Here are all three answers side by side, in the same order as the reels, and the honest note on each one about why it moves.
If you commented STACKS, this is the page: the full answer on when a self hosted stack is worth it and when it quietly costs you more than it saves. Start with Part I.
Part I. The short answer
Should you self host?
If any single line on the right is true, stop there. It does not matter how many on the left are also true.
Self host the ones where the bill hurts and the blast radius is small. Rent anything that touches money, deliverability, or a pager you do not carry.
Yes, if
+One line item is now costing more per month than a server would.
+The data legally cannot sit on someone else's infrastructure. Health, government, EU residency.
+You already run a box and you have actually restored a backup, not just taken one.
+The tool is open source AND ships a maintained Docker image. Both, not either.
+Your usage is steady. Self hosting punishes spiky traffic, which is exactly what managed autoscaling is for.
+You are moving one or two services. Not nine.
No, if
×You have not shipped yet. Nothing here matters until people are using it.
×You have never restored a backup. Taking one is not the same skill.
×The saving is under about fifty dollars a month. Your evening is worth more.
×It is payments. Never. Not once. Not ever.
×It is email deliverability. Your domain reputation is not worth the experiment.
×It is on your critical path and nobody is on call at 2am. That includes you, asleep.
Part II. Before you touch anything
Which stack are you on?
Three answers, and you almost certainly want the first one. Read the catch before the cost.
Part 1
The starter stack
When: You have shipped something and it has users you can count.
Mostly free tiers
The catch: Nothing. Stay here far longer than you think. Every swap below is something you do because you were forced to, not because it is better.
Part 2
At 10,000 users
When: A limit or an invoice forced your hand. Not before.
Whatever the invoice says
The catch: Six of the nine move and three do not. Migrating early costs you the thing you were trying to save.
Part 3
Self hosted
When: One bill has started to sting, or the data cannot leave your box.
About $15 a month
The catch: You just became your own DevOps team. Nine services are yours to patch, back up and restore at 2am. Self host one or two, not nine.
Part III. The table
The nine jobs
The job numbers never change. Only the answer under them does. Where a cell says stays, that is the answer, not a gap.
01
Database
Part 1Starter
Supabase
Part 2At 10,000
Neon
Part 3Self hosted
Supabase, self hosted
It's open source, so owning it is a Docker command. Four people told me Neon at scale and they were right.
02
Coding
Part 1Starter
Claude
Part 2At 10,000
Claude stays
Part 3Self hosted
Ollama + an open model
Open models are free, private and close enough now. At scale nothing beats it, whatever the comments say about Codex.
03
Front end
Part 1Starter
Vercel
Part 2At 10,000
Cloudflare
Part 3Self hosted
Coolify on a $10 box
The one swap everybody agrees on. Seven people asked for Cloudflare by name.
04
Back end
Part 1Starter
Railway
Part 2At 10,000
AWS
Part 3Self hosted
The same box
Self hosted, two subscriptions collapse into one server. At scale you don't swap it for Render, you swap it for a bill.
05
Getting paid
Part 1Starter
Stripe
Part 2At 10,000
Stripe stays
Part 3Self hosted
don’t
Nobody self hosts card processing. You'll IPO before you outgrow it.
06
Voice AI
Part 1Starter
ElevenLabs
Part 2At 10,000
ElevenLabs stays
Part 3Self hosted
Kokoro
Kokoro is 82M params, Apache 2.0, runs on a CPU. It's also the only tool nobody argued with.
07
Phone lines
Part 1Starter
Twilio
Part 2At 10,000
Telnyx
Part 3Self hosted
Asterisk
You can self host it. You probably won't. At volume Telnyx is the same job for roughly half.
08
Bugs
Part 1Starter
Sentry
Part 2At 10,000
Datadog
Part 3Self hosted
GlitchTip
GlitchTip is Sentry compatible, so you just swap the DSN. At scale one dashboard eats the whole monitoring stack.
09
Session replay
Part 1Starter
PostHog
Part 2At 10,000
Amplitude
Part 3Self hosted
OpenReplay
PostHog themselves say the self hosting maths rarely works. Believe them.
Three rows never move: Stripe, and at scale Claude and ElevenLabs. Nobody self hosts card processing, and the two tools people argue hardest about are the two nobody actually leaves.
This page is what you run it on. The other one is how to build it.
Picking the right stack will not save an app with secrets in the repo, a 2,500-line file and one commit called “updates”. That is the other page: the five mistakes, the two repos side by side, and the six stages.
A skill that places you in a column, names the swaps with a real forcing function behind them, and talks you out of the rest. Most people should be in column one and are being argued out of it by comment sections.
Every stack gets the same treatment: what it costs at ten users, what it costs at ten thousand, and the one that forces the swap. One email per drop, nothing between.