Antfly learned to stop worrying and love Apache 2.0

The software company Antfly has transitioned its licensing model from the restrictive Elastic License 2.0 to the open-source Apache 2.0. The company concluded that restrictive licensing was no longer an effective defense against cloud competitors in an era of AI-assisted coding.
Why it matters
This shift reflects a broader trend in the software industry where companies are re-evaluating the efficacy of 'source-available' licenses against rapid AI-driven development.
Back to Thoughts November 16, 2026 How Antfly learned to stop worrying and love Apache 2.0 Antfly moved from the Elastic License 2.0 to Apache 2.0. Why we hedged, and why the hedge stopped making sense.
This post goes out with Antfly 0.3 , our first release since the move to Apache 2.0.
Until October, Antfly was only source-available. It was available under the Elastic License 2.0 , and we were excited about how permissive we thought it was: you could read the code, change it, and run it, you just couldn't build your own business reselling it. But in October we decided to move all of it to Apache 2.0 . Now you can use it, modify it, ship it inside your own product, and build a business on it, including one that competes with ours.
It turns out that software is different now. Here's our thinking.
Get smarter about the news
Sign up free for a feed built around what you actually care about, Dive Deeper research on any story, and the full text of every article.
Create free accountAlready have an account? Sign in