On Second Thought ■ Episode 3
In February 2011, US Chief Information Officer Vivek Kundra published the Federal Cloud Computing Strategy under the Obama administration's 25-Point IT Reform Plan. The mandate was explicit: agencies must evaluate a cloud computing option first, and come up with a damn good reason not to use it.
By 2014, Gartner's Magic Quadrant showed AWS with more than five times the cloud IaaS compute capacity of the next fourteen providers combined. By 2018, "on-premise" had become a dirty word in enterprise IT. The axiom was established.
Not discovered. Not proven. Established. By a government memo, an analyst report, and three poster-child migrations from companies (Netflix, Spotify, Airbnb) whose elastic-demand requirements bear no resemblance to the vast majority of software running in production today.
The Axiom
"Of course we use the cloud. Everyone does." Nobody questions this in a board meeting. Nobody loses a promotion for recommending AWS. CTOs choose it not because it is optimal, but because it is defensible. If something goes wrong with AWS, it is AWS's fault. If something goes wrong with your own infrastructure, it is your fault. This is not engineering. This is career insurance.
AWS Activate offers startups $1,000 to $100,000 in free credits. Incubators distribute them as standard onboarding. The credits expire after twelve to twenty-four months. By then, your architecture is built on AWS services, your team knows AWS tooling, your monitoring assumes CloudWatch, and your deployment pipeline assumes CodeDeploy. Migration cost exceeds staying cost. The business model is identical to the IBM mainframe playbook of the 1970s: make switching costs higher than the cost of staying. The technology changed. The economics did not.
Harvard Business School research documented the effect: after AWS launched in 2006, first-round VC funding for cloud-benefiting startups dropped 20 per cent because infrastructure costs fell dramatically. VCs responded by funding more startups with less diligence. The cloud did not just change infrastructure. It changed who gets funded. And it locked in AWS as the default for an entire generation of companies that never evaluated the alternative.
The Cost
Flexera's 2025 State of the Cloud Report found that 27 per cent of all cloud spend is wasted. At $675 billion in global cloud infrastructure spending, that is $182 billion per year evaporating into unused resources, over-provisioned instances, and forgotten development environments.
37signals, the company behind Basecamp and HEY, left AWS in 2023. The hardware investment: approximately $700,000 in Dell servers, fully recouped during the first year. Storage: 10 petabytes moved from S3 to Pure Storage. Annual savings: $2 million. Five-year projection, revised upward from $7 million: over $10 million. With faster hardware and considerably more storage. AWS reportedly comped a quarter-million-dollar egress bill on the way out. One does appreciate the parting gift.
Dropbox moved 90 per cent of its customer data off AWS to custom colocation in 2015 and 2016. Investment: $53 million. Savings: $75 million over two years. The return on investment was achieved before the infrastructure was fully operational.
Ahrefs, the SEO analytics company, never went to cloud. They run 850 servers in a Singapore colocation. Monthly cost per server: $1,550 on-premises versus $17,557 for the AWS equivalent. AWS would cost 11.3 times more. Ahrefs' total revenue for 2020 to 2022 was $257.5 million. The cloud would not have reduced their margin. It would have eliminated their company.
GEICO, Warren Buffett's insurance subsidiary, spent a decade migrating over 600 applications to Microsoft Azure. Costs ballooned to 2.5 times expectations. In 2024, they announced repatriation of at least 50 per cent of workloads. A decade to get in, half a decade to get out.
The Sovereignty Problem
The CLOUD Act, signed into US federal law in March 2018, allows US law enforcement to compel American technology companies to hand over data stored anywhere in the world. If your data is hosted in Frankfurt or Paris, and the infrastructure is managed by AWS, Azure, or Google Cloud, it can legally be accessed by US authorities. Your Frankfurt data centre is legally a US data centre if AWS runs it. This directly conflicts with GDPR Article 48.
Europe's response was Gaia-X, a federated cloud initiative launched six years ago. US hyperscalers lobbied to be included. Once inside, they, in the words of Nextcloud founder Frank Karlitschek, "flooded it with documents and regulations." Founding member Scaleway withdrew. Karlitschek called it a "paper monster." The initiative failed. The data stayed American.
The NIS2 Directive and DORA now require critical-sector organisations to assess cloud dependency risk. France's "Doctrine Cloud" mandates government data stays in French-controlled facilities. The regulatory environment is turning. The infrastructure, however, remains American.
The $1,000 Test
For $1,000 per month on AWS, you get approximately four mid-tier instances (8 vCPU, 16 GB each) with no bandwidth budget. Egress costs extra. Storage costs extra. Monitoring costs extra.
For $1,000 per month on Hetzner, you get seven dedicated servers. 16 cores each. 128 GB RAM each. 20 TB bandwidth included per server. Totals: 112 cores, 896 GB RAM, 140 TB bandwidth. Independent benchmarks show 76 per cent better multi-core performance and 11 times more IOPS.
The price difference is not a rounding error. It is a factor of seven to ten. For workloads that do not require elastic scaling (which is most of them), the cloud is not a premium for convenience. It is a tax on the assumption that you had no other choice.
The Question
86 per cent of CIOs now plan to move some workloads back from public cloud. The highest figure ever recorded, up from 43 per cent in late 2020. The axiom is cracking.
Modern servers handle 500,000 HTTP requests per second. PostgreSQL delivers 70,000 IOPS. A single well-configured machine handles 50,000 concurrent users with proper caching. The vast majority of software in production does not need elastic scale. It needs reliability, predictable costs, and control over its own data.
The cloud was never the only answer. It was the only answer nobody got fired for choosing. The career insurance premium was paid by every company that did not question the default.
On second thought: what if the default is wrong?
27% of cloud spend wasted ($182B/year). Median EC2: 7-12% CPU. 37signals saved $10M+ leaving AWS. Ahrefs: 11.3x cheaper on-prem. GEICO: 2.5x over budget, repatriating. 86% of CIOs plan workload repatriation. The CLOUD Act makes your Frankfurt data centre legally American. The cloud was the only answer nobody got fired for choosing. What if the default is wrong?