Antfly学会了不再担心并爱上Apache 2.0
Antfly learned to stop worrying and love Apache 2.0

原始链接: https://antfly.io/thoughts/how-antfly-learned-to-stop-worrying-and-love-apache-2

Antfly 0.3 是项目从 Elastic License 2.0 转向 Apache 2.0 后的首个版本。团队做出这一转变,是因为 AI 辅助开发让复制代码更快,源码可用许可提供的保护更少,而用户希望获得真正的开源。Apache 2.0 允许用户使用、修改、分发和基于 Antfly 建立业务,包括竞争对手,且此前发布的版本保持开源。Antfly 将通过其托管服务 Antfly Cloud 获利,而自行托管保持免费。0.3 版本新增了基于 Postgres wire 协议的 SQL 访问、查询对象存储中的 Iceberg 和 Parquet 表、从已加载文档自动创建知识图谱,以及可生成带引用报告的研究智能体。源代码位于 GitHub。

Antfly 是一款开源数据库,结合了搜索与推理(面向 PDF、扫描件、音频和视频的 OCR、转录与嵌入),宣布在 v0.3 中从 Elastic License 2.0 切换到 Apache 2.0。创始人表示,用户要求真正的开源许可证,而 AI 代理现在让构建此类数据库更容易,降低了旧许可证的保护价值。服务器、推理引擎和嵌入式 Antfly Lite 均为 Apache 2.0,无开放核心;收入来自 Antfly Cloud。评论讨论社区/流程价值与代码的关系,将 Antfly 与 Valkey 和 OpenSearch 等 fork 进行比较,指出 Elastic License 对许可证密钥的限制,并质疑已发布代码的重新授权。一位用户计划将 PostgreSQL 视图摄取到 Antfly 中。总体而言,Antfly 正全面拥抱开源,以便用户拥有自己的数据与智能,同时通过托管云服务实现变现。
相关文章

原文

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.

联系我们 contact @ memedata.com