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.
Why we hedged
We started on ELv2 because we were worried that one of the clouds would take Antfly and run it as a hosted service before we'd built a business of our own. We weren't the first. Elastic moved away from Apache 2.0 in 2021, HashiCorp moved Terraform to the Business Source License in 2023, and Redis went source-available in 2024. I've built and run infrastructure companies, and I understand the reasoning: it's hard to watch someone else make money from years of your work.
But a license like that only protects you if the code is the hard part to copy. If a cloud provider can't host your code, it has to write its own, and that used to take years.
I don't think it takes years anymore. Everyone on our team writes code with agents now, and I'd be surprised if the same weren't true at every single cloud provider. A well-funded team that wants a database like ours can get to one much faster than it could in 2021, with or without our license. So the license was protecting less than we'd thought, and meanwhile users kept telling us they wanted open source.
They have good reason. Under Apache 2.0, every version we've released stays under those terms whatever we do later. We intend to keep Antfly on Apache 2.0.
How Antfly makes money
We designed Antfly and are its active maintainers, so we still think we're the best people to host it at scale. That's Antfly Cloud: if you'd rather not operate the database, we'll run it for you, and that's what we charge for. You won't pay Antfly for running it yourself, whether that's on your laptop, inside your application, or on your own infrastructure.
But we don't want our Cloud business to limit what projects you can build on an inference-native database.
What's in Antfly 0.3
0.3 is out, and it's all Apache 2.0. You can query Antfly tables in SQL, including from psql over the Postgres wire protocol. Iceberg and Parquet tables in object storage can be queried where they sit. Antfly can build a knowledge graph for you from the documents you load, and a new research agent turns a question into a cited report. The full list is in the release notes. The code is at github.com/antflydb/antfly.
I still worry about plenty of things, but what you do with the code isn't one of them anymore.
