Most business owners I meet treat their hosting invoice like an electricity bill from a house they have never visited. The vendor "handles it", the number arrives every month, and as long as the website stays up, nobody asks questions. If you want cloud hosting costs explained in plain language, this article is for you, because that invoice is one of the few tech expenses you can actually audit yourself.
Here is the uncomfortable part: in my experience reviewing infrastructure for Indonesian SMEs, roughly a quarter to a third of a typical monthly cloud bill is waste. Not fraud, not incompetence, just accumulated laziness that nobody was assigned to clean up.
You do not need to become an engineer to fix this. You need to understand three words and ask four questions.
The Three Things You Are Actually Paying For
Every cloud bill, whether it comes from AWS, Google Cloud, Alibaba Cloud, or a local provider like Biznet Gio, breaks down into the same three categories.
Compute is the rented computer that runs your application. It is priced by size (CPU and memory) and by time. A small server might cost Rp400.000 per month, a large one Rp4.000.000 or more. The key insight: you pay for the size you reserved, not the size you use. A server running at 8% capacity costs exactly the same as one running at 80%.
Storage is where your files and database live. It is cheap per gigabyte but grows silently. Old backups, log files nobody reads, and uploaded images from a campaign three years ago all sit there billing you monthly.
Bandwidth (sometimes called data transfer or egress) is what you pay when data leaves the server and travels to your customers' phones. Every image, every page load, every API response counts. This is the sneakiest line item because it scales with traffic and with sloppiness at the same time.
Where the Waste Actually Hides
After looking at dozens of these bills, the same patterns show up almost every time.
Oversized servers
Vendors size servers for the worst imaginable day, then never revisit. I reviewed a setup for a distributor in Tangerang whose main server was provisioned for traffic they hit exactly twice a year. The rest of the year it idled at under 10% usage. Downsizing one instance saved them around Rp2,1 juta per month, about Rp25 juta a year, for one hour of work.
Forgotten test environments
Developers spin up a "staging" or "demo" server for a project, the project ships, and the server keeps running. Forever. I have found test environments that had been billing quietly for two years after the feature they were testing went live. Nobody remembered they existed because nobody was reading the bill line by line.
Unoptimized images eating bandwidth
This one connects your marketing team to your finance team. If your product photos are uploaded straight from a camera at 4MB each, every visitor downloads 4MB per photo. Compress those images to 200KB, which loses no visible quality on a phone screen, and your bandwidth cost drops by 95% for that traffic. As a bonus, your pages load faster, which is a revenue issue in its own right. I wrote more about that in Website Speed Is a Revenue Number, Not a Tech Number.
Orphaned storage
Disks that belonged to deleted servers, database snapshots on an "every day, keep forever" schedule, and duplicate backups in two regions. Individually small, collectively real money.
How to Read the Bill Without an Engineering Degree
Ask your vendor or your internal team for the detailed invoice, not the summary. Then do this:
- Sort line items by cost, largest first. The top five lines usually explain 80% of the bill.
- For each of the top five, ask: what is this, and what happens if it disappears? If the answer takes more than two sentences or includes "let me check", flag it.
- Count the servers. Then count your actual environments: production, maybe one staging. If the server count is higher than that, ask why.
- Compare this month to six months ago. Growth should track your business. If revenue is flat but the bill grew 40%, something is drifting.
You are not trying to catch anyone. You are creating the expectation that someone reads this bill, which by itself changes behavior.
The Quarterly Questions to Ask Your Vendor
Put a recurring calendar event every three months and ask these four questions in writing:
| Question | What a good answer sounds like |
|---|---|
| What was our average server utilization this quarter? | A number, e.g. "35% CPU on average, 70% at peak" |
| Which resources can we downsize or delete? | A specific list, even if short |
| What is our largest bandwidth consumer? | A concrete answer like "product images on the catalog page" |
| If traffic doubled next month, what breaks first and what would it cost? | A named bottleneck and a rough figure |
A vendor who cannot answer these is not managing your infrastructure, they are just forwarding invoices with a markup. A vendor who answers them well is worth keeping and probably worth paying more.
Note what is not on the list: "can you make it cheaper?" That question invites corner-cutting. The questions above surface waste without pressuring anyone to under-provision the systems your business runs on. There is a floor here. Reliability, backups, and security cost real money, and the goal is to stop paying for nothing, not to stop paying for protection. Cutting the wrong Rp500.000 can cost you a weekend of downtime during a promo, which brings its own bill.
When Cheap Becomes Expensive
One warning from the other direction. Some SMEs respond to a scary bill by moving everything to the cheapest possible VPS with no backups and no monitoring. Then a disk fails, there is no snapshot, and three years of transaction data is gone. The Rp300.000 per month they saved cost them a business.
Sensible cost optimization keeps redundancy and monitoring and cuts idle capacity, orphaned resources, and inefficiency. If a proposed saving reduces your ability to recover from failure, it is not a saving, it is a loan with terrible terms. This is the same logic as managing technical debt: short-term relief, long-term interest.
The Takeaway
Your cloud bill is readable. Compute is the rented computer, storage is the filing cabinet, bandwidth is the delivery cost. The waste hides in oversized servers, forgotten test environments, heavy images, and orphaned storage, and it is usually 20 to 30% of the total.
This month: get the detailed bill, sort by cost, question the top five lines, and count your servers. Then set the quarterly review. One hour every three months keeps the bill honest, and for most SMEs that hour is worth several juta per month, every month, for as long as you run the business. That is a better return than almost anything else you will do with an hour this week.