What Drives the Bill

A real cloud invoice can show dozens of line items. But most of the money almost always comes from the same handful. Knowing which three categories dominate — and which one people most often overlook — turns a bewildering bill into something manageable.

Think of a mobile phone bill. The base plan — your "minutes and data allowance" — takes up most of it. Storage on the phone's cloud backup adds a smaller, fairly predictable line. And then there are roaming charges from that one trip abroad: not huge in absolute terms, but surprising if you forgot to watch them. Cloud bills follow the same pattern: the plan (compute) is most of it, the storage is steady and predictable, and the egress — data sent out to the internet — is the roaming charge that catches people off guard.

Compute — Often One of the Largest Lines

Cloud compute means virtual machines — rented computers — running your software. Their cost is charged per hour (sometimes per second), and it accumulates fast when you run many machines for many days. A company with twenty servers running around the clock pays for 20 × 24 × 30 = 14,400 machine-hours per month, before anything else is on the bill.

Compute is often one of the largest and most controllable lines, especially for typical app workloads — you choose how many machines run and for how long, which is where the biggest savings opportunities usually live. In data-heavy, analytics, AI, or high-traffic media systems, though, storage, egress, managed databases, or logs can dominate instead.

Storage — Cheap per Unit, Large in Total

Object storage (files, backups, media), block storage (the "hard drives" attached to machines), and database storage are all metered by the gigabyte per month. The per-gigabyte rate is low — often fractions of a cent — but organizations accumulate data over years, and totals in the terabytes are common. At that scale, even a small per-GB rate becomes a substantial monthly line.

Storage rarely shocks a beginner the way compute can, but it is steady and grows over time. Keeping it under control means occasionally reviewing what is stored and deleting what is no longer needed.

Data Transfer Out — The Sneaky One

When data moves from the cloud to the open internet — for example, when your app sends a response to a user's browser, or when you download a file — that outbound movement is called egress. Egress costs money. The typical rate is a few cents per gigabyte, but a popular app serving millions of users can transfer many terabytes per month, making egress a meaningful bill item.

The counterpart, ingress — data arriving into the cloud from outside — is free on all three major providers. You are not charged for uploading files, for users sending data to your app, or for data coming in from elsewhere. The charge is one-directional: out, not in.

For small projects, egress is negligible. But for anything at scale — video streaming, large file downloads, high-traffic APIs — it can be the line item that surprises. AWS and Azure both include the first 100 GB of data transfer out per month free. Google Cloud goes further: its Standard network tier gives 200 GB per month of free internet egress per region (in place since 2023); the always-free tier also separately includes small per-service amounts. All three providers give a generous free egress allowance that comfortably covers most exploratory and small-scale work.

Everything Else

Beyond the three big drivers, cloud bills include charges for managed services (a managed database, a message queue, a load balancer each have their own meters), individual API requests, and dozens of smaller line items. Each is typically small, but across a large organization with many services, they total up. The most important habit is not memorizing every rate, but knowing that every service has its own meter and that the sum of small things can surprise you at scale.