The real bill for keeping something online
Four things cost money continuously once something is live: the machine serving the pages, the database, the files being sent to visitors, and the domain. Everything else is one-off. Understanding which is which is most of understanding a hosting bill.
Where the money actually goes
| Thing | Billed by | Usually the biggest surprise |
|---|---|---|
| Serving pages | Requests or time spent computing | A crawler or a bot hitting you constantly |
| Database | Time awake, and storage | One that never sleeps, doing nothing, all month |
| Bandwidth | Gigabytes sent to visitors | Large uncompressed images |
| Domain | Per year | The renewal price differing from the first-year price |
The one that catches everybody
A database billed for being awake rather than for being used. A quiet app with nobody visiting can still run up a real monthly cost purely because something is keeping the database from going to sleep. It is the most common unexplained line on a small project's bill.
What to do about it
Set a spending limit on the provider's dashboard before you need one. Compress images. Let databases sleep. And know what happens when you exceed your plan: some services keep billing, some pause. Both are defensible; being surprised by which one you have is not.
Ura pauses. Going over the allowance switches off what is live rather than quietly running up a bill, and there is a warning at 80% so it is never a shock. Nothing is deleted, and paying puts everything back immediately.