"It's basically free to run" is true for about ninety days. Then your app starts costing money — which, oddly, is usually good news. Here's the honest breakdown of what a small production app costs to operate, where the surprises hide, and the one line item every founder forgets to count.
The $0 phase (real, but rented)
Modern free tiers are genuinely generous. Hosting on a hobby plan, a starter database, a monitoring free tier, error tracking under the monthly event cap: a small app with modest traffic can honestly run on $0 plus a $12/year domain for a while.
Two things about that phase, though. First, "hobby" tiers usually prohibit commercial use in the fine print — the moment you charge customers, you're often obliged to upgrade anyway (and getting force-upgraded during a traffic spike is not the moment you'd choose). Second, free tiers are a loan: you're borrowing against the day usage crosses a line you weren't watching.
The realistic monthly bill, small production app
- Hosting: $0–20. The pro-plan jump comes earlier than expected, usually for a boring reason like team seats or usage limits, not traffic glory.
- Database: $0–25. This is typically the first real bill — storage grows monotonically, and row counts don't care about your revenue.
- Email sending: $0–20 once you pass free-tier volumes. Transactional email is cheap; deliverability problems are not, so don't bargain-hunt here.
- Monitoring and error tracking: $0–15. Free tiers carry you surprisingly far if you're one app, one founder.
- AI API calls: the wildcard. $0 if your app doesn't call models; anywhere from $5 to "how did this happen" if it does. This is the line that most needs a spending alert, because it's the only one a bug can multiply overnight.
Call it $10–80/month for a typical small app in honest production, tools included. If you're paying dramatically more, something's misconfigured; dramatically less with real users, and you're probably carrying risk somewhere (usually backups or email).
The invoice ambushes
Three patterns produce almost all cost horror stories. Usage billing without alerts — a loop, a scraper, a viral moment, and a four-digit surprise. Retained backups on storage-priced plans quietly compounding. And per-seat pricing on tools you added "to try" and forgot. The common thread: none of these announce themselves. A monthly ten-minute skim of every invoice — literally reading them — is the whole defense.
The line item nobody books: your evenings
Now the uncomfortable one. Tally what you actually spend on operations in a month: the deploy that needed re-doing, the webhook you investigated, the dependency scare, the customer email that turned out to be a bug hunt, the low-grade checking-the-dashboard anxiety. For most solo founders it's five to fifteen hours a month — invisible, unpaid, and heaviest exactly when the app is succeeding.
Price those hours at anything reasonable and they dwarf the infrastructure bill. This is the real cost of running an AI-built app, and it's the one the $0-hosting narrative never mentions.
What this means for the buy-help question
We obviously have a horse in this race — operations is what we sell, from $149/month with an SLA that pays credits when we miss. So discount our view accordingly. But the framework stands on its own: infrastructure costs are rarely the issue; the decision is about your hours and your risk. Under ~$500/month revenue, do it yourself with the guides on this blog — genuinely. Above that, or at "downtime costs me real money," the math starts favoring handing someone the pager. Run your own numbers. Just run them honestly, evenings included.