Cloud Infrastructure, 2021 to 2026: A Timeline of What Changed
Archi4 min read
Contents
- A Five-Year Span That Rewrote the Defaults
- 2021: Hourly Instances and Free Egress That Fit on a Napkin
- 2022: The Grid Becomes a Gatekeeper
- 2023: GPU Scarcity Moves the Queue
- 2024: Egress Fees Become a Policy Question
- 2025: The Metered Kilowatt and the Sovereign Region
- 2026: Three Bills and a Reservation Calendar
- The Next Two Items on the Calendar
A Five-Year Span That Rewrote the Defaults#
A cloud bill in 2021 was mostly a compute bill. A cloud bill in 2026 is a compute bill, a power bill, and an exit bill, and the three are negotiated separately. The timeline below follows the changes in the order they landed, with one caveat: regional rollouts never move at the same speed. What reached Frankfurt in March often reached Sao Paulo a year later.
Prices below are indicative. Treat them as shapes, not quotes.
2021: Hourly Instances and Free Egress That Fit on a Napkin#
The default purchase was an on-demand x86 instance billed by the second with a one-minute minimum. Reserved capacity meant a one-year or three-year commitment in exchange for a discount somewhere between 30 and 60 percent, and most teams bought one year because finance would not sign longer.
Outbound transfer was an afterthought. Providers included roughly 100 GB a month in their free tiers and charged around 8 to 12 cents a GB after that. Few teams measured it. The first invoice shock usually came from a cross-region replication job, not from a customer.
Arm was on the roadmap. Graviton2 had shipped the year before, and the migration work was mostly hunting down vendor libraries that had never built for ARM64.
2022: The Grid Becomes a Gatekeeper#
The constraint that arrived first was not silicon. It was the substation. Regulators in a handful of dense markets started asking data centre operators to justify new grid connections, and a few stopped granting them outright. Dublin tightened its rules. Amsterdam had already paused new builds.
Inside the cloud, this showed up as something less dramatic: fewer region launches, longer lead times on dedicated capacity, and a price floor on instances in constrained metros. Spot capacity, once treated as a hobby, became a line item in production plans. Teams that had never tested interruption handling wrote their first checkpoint logic.
2023: GPU Scarcity Moves the Queue#
Training capacity went to contract. Multi-year reservations, prepayment, and allocation by relationship replaced the self-serve console for the largest accelerators. Spot markets for GPUs quoted prices that moved weekly.
The knock-on effects were ordinary. Memory prices rose. Colocation providers with spare megawatts found buyers. Internal platform teams got a quota process, which meant the data science group started competing with the web group for the same budget line.
2024: Egress Fees Become a Policy Question#
Competition moved from price per hour to price per exit. One large provider dropped charges for customers migrating away. Others followed with free transfer allowances for leaving, and the phrasing in those announcements was careful.
The regulatory side moved in parallel. The EU Data Act entered into force in January 2024, with obligations on switching and on the charges providers may apply. The deadlines were set years out, but the direction was clear: the cost of leaving a cloud was going to be visible, and eventually capped.
Confidential computing also crossed from demo to purchasable. Memory encryption on the instance stopped being a research feature.
2025: The Metered Kilowatt and the Sovereign Region#
Providers started publishing more than price: power usage effectiveness, water consumption, carbon intensity by region. Buyers in regulated industries began asking for those numbers during procurement, and a few wrote them into contracts.
Sovereign cloud offerings multiplied, built on the same hardware with separate operations and separate legal entities. For a bank or a health insurer, the question stopped being which region and became which operator, under which jurisdiction, with which staff able to touch the disks.
The Data Act's main obligations applied from September 2025. Contract clauses on switching, notice periods, and export formats started appearing in standard terms.
2026: Three Bills and a Reservation Calendar#
The current purchase looks different. Capacity is reserved in blocks measured in months, with power and cooling reflected in the rate. Arm instances carry a large share of general-purpose web traffic. Egress is still charged, but it is forecast, tracked, and often negotiated with a floor.
FinOps spreadsheets have columns for carbon and for exit cost. The migration test, once an annual exercise, now runs quarterly in teams that got burned.
The Next Two Items on the Calendar#
Switching charges under the Data Act phase out for most categories from January 2027, which gives every contract signed this year a hard review date. Energy reporting requirements for larger data centres in Europe land in the same window.
The practical consequence is a contract calendar. Legal owns the deadlines. Platform teams own the export formats. Those two groups rarely sit in the same room, and the timeline above suggests that is the gap worth closing before the next renewal.
More articles