Why Traditional Open Source Licensing Is Breaking Under Modern Cloud Hosting
From Redis to Terraform, independent developers are fleeing the MIT license. Reflections on keeping code free while preventing trillion-dollar cloud arbitrage.
When the MIT and BSD licenses were drafted decades ago, software distribution meant shipping source tarballs or CD-ROMs. If someone modified your code, they distributed the binary, and community norms generally protected original creators.
Today, cloud hyperscalers can fork an independent engineer’s open-source database, wrap it in a proprietary managed dashboard, resell it to millions of enterprise customers, and give zero dollars back to the creator who wrote the code.
This has triggered a wave of license changes across Redis, CockroachDB, and HashiCorp.
As an independent software builder running Ryla Labs, I want my code to be inspected, learned from, and modified freely by students and builders. But we must acknowledge reality: if independent developers cannot earn a sustainable living from the software they create, the entire ecosystem suffers.
Written by Daniel Dano
danieldano.com ↗15-year-old software developer, founder of Ryla Labs (50,000+ monthly users across 12 countries), author of Built Young, and high school student leader.