Cloud Cost Optimization and the Shift Back to On-Premises Hardware: Insights from 37signals and Industry Leaders
The article examines how 37signals' cloud repatriation initiative, along with broader industry trends at companies like Snap, Twitter, and major cloud providers, is driving significant cost savings, prompting a resurgence of on‑premises hardware and reshaping cloud cost‑optimization strategies across the sector.
David Heinemeier Hansson, CTO of 37signals and creator of Ruby on Rails, reports that moving many services from public cloud to in‑house hardware has already cut the company’s cloud spend by 60%, saving roughly $1 million per year and projecting up to $10 million in savings over five years.
The company’s “down‑cloud” effort involved a $500 k hardware purchase amortized over five years, and Hansson estimates that similar firms could achieve even larger savings, citing Snap’s $3 billion cloud spend over five years as a benchmark.
Other tech giants are also tightening cloud budgets: Snap, Twitter, and Amazon Web Services (AWS) are all actively reducing cloud expenditures, with Twitter aiming to cut $1‑3 million daily and AWS acknowledging slowed growth as customers optimize spend.
Cloud providers themselves note a slowdown in revenue growth—Azure’s YoY growth around 30%, Google Cloud 32%, and AWS down to 20%—as enterprises adopt multi‑cloud strategies, on‑premises solutions, and utility‑pricing models to control costs.
Hardware vendors such as Lenovo and Dell are benefiting from this shift, reporting double‑digit revenue growth in server and storage segments, while new initiatives like Lenovo’s ODM+ model and Dell’s infrastructure solutions target large enterprises seeking on‑premises alternatives.
In conclusion, the push to reduce cloud spend is reshaping the industry: cloud providers are offering optimization assistance, while hardware manufacturers emerge as winners in the evolving cost‑efficiency landscape.
Continuous Delivery 2.0
Tech and case studies on organizational management, team management, and engineering efficiency
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.