5 MIN READ
The cloud bill in 2026 has become a line item in the operating budget that is comparable in size to the engineering payroll that runs the cloud, and the budget owners have started to notice. The CFO who used to glance at the bill and approve it is now reading the line items, asking the questions, and pushing engineering to explain why the line items have grown 40 percent year over year without a corresponding 40 percent growth in revenue. The conversation that used to happen between the engineers and the cloud vendor is now happening between the engineers and the CFO, and the CFO is not as easy to fool as the cloud vendor.
The shape of the bill
The shape of the cloud bill in 2026 is roughly the same shape it was in 2022, with the same line items getting bigger.
Compute. Compute is the biggest line item, and compute has grown as the workloads have grown. The unit cost has come down. AWS, Azure, and Google Cloud have all dropped their per vCPU hour pricing, and that per vCPU hour pricing is the metric engineering points to when explaining why the bill is bigger. The unit cost reduction is real.
Storage. Storage runs as the second biggest line item, and storage has grown as the data has grown. The unit cost has come down less than the SREs would like. Object storage prices have dropped, but the data has landed on storage faster than the price has dropped, and the result is a storage bill that keeps growing in absolute terms.
Egress. Egress sits as the third biggest line item, and the line item engineering is most uncomfortable with. Egress has grown as the architectures have grown more distributed, and the unit cost has not come down at all. Cloud providers charge per gigabyte for traffic leaving the cloud, and that per gigabyte charge is what the multi cloud and the hybrid cloud architectures pay the most.
Managed services. Managed services (the databases, the message queues, the Kubernetes, the ML platforms) are the fastest growing line item, and the line item the build team has the least ability to optimise. Managed services charge per hour, per request, per gigabyte, and the per whatever charge is what engineering has the least use on. Managed services look like a service contract and bill like a utility.
What the FinOps movement has produced
The FinOps movement, which started as a niche community in 2019, is now a board level conversation in any firm with a meaningful cloud bill. The FinOps Foundation has a certification, an annual conference, and a vendor market that has grown to match the rest of the cloud market. The FinOps practitioner is a real role, and the role is what most firms hire when the cloud bill has gotten big enough to need its own advocate.
Three things from the movement are worth knowing. Cost attribution: the per team, per product, per environment view of the bill, and the view the cloud cost lead uses to make the optimisation decisions. Cost attribution is what the FinOps function does well, and what makes the rest of the work possible.
Then the reserved instance and savings plan optimisation, where the commitment to spend a certain amount on compute in exchange for a discount of 30 to 60 percent off the on demand price becomes the lever. Matching the commitment to the actual usage is harder than it sounds because the actual usage keeps changing.
Finally the showback and the chargeback. Showback tells engineering what they are spending, chargeback actually charges the team for what they are spending. Showback runs as the carrot, chargeback sits as the stick, and the team responds to one or the other depending on the firm’s culture.
What to do about the bill
If you are running a meaningful cloud bill and the bill is growing faster than the revenue, the right move is to hire a FinOps practitioner. The hire costs more than the work would cost in house, and the hire finds more savings than engineering has the time to find. For a bill that has gotten big enough to need its own advocate, a FinOps practitioner is the right investment.
If you are already running FinOps and the bill is still growing, the right move is to look at the managed services. Managed services are the line item that grows the fastest, the line item that runs as the hardest to optimise, and the line item that sits as the most likely to be where the savings live. Managed services are not always the right answer, and they are sometimes the only answer for the team that does not have the time to run the alternatives.
If you are still arguing that the cloud is cheaper than the data centre, the argument is no longer true for the workloads that have been in the cloud long enough to have accumulated the architectural debt. The cloud is cheaper for the new workloads, more expensive for the old ones, and will keep being more expensive for the old ones until they are migrated or retired. The migration sits as engineering’s migration, and the CFO is going to keep asking about it until it is done.
The bottom line
Hire the FinOps advocate, fund the managed services audit, write down who owns the bill when the engineering lead changes. Cloud spend in 2026 is a salary line, and the firms that treat it like one will outlast the ones that treat it like a utility invoice.
Sources & Further Reading
All claims in this article are sourced from primary documentation, vendor advisories, and reputable security researchers.
Spotted an error? Email the editor. Corrections are issued with a visible correction note.
Editorial standards. Every article on humanrequired.org is reviewed by a human editor before publication. AI may assist with drafting or research; final editorial control is human. Read the full standards.
