Amazon is buying DuckLabs—not the DuckDB project

Amazon has signed a definitive agreement to acquire DuckLabs, the Amsterdam company behind DuckDB. The transaction is expected to close shortly; DuckLabs says its team will join AWS in early September, subject to closing. The distinction that matters is what Amazon is not buying: the DuckDB open-source project. Amazon says the project will remain under the independent DuckDB Foundation and keep its MIT license.

That split should frame every enterprise response to the deal. AWS gains the people who created and maintain much of the technology, including co-founders Hannes Mühleisen and Mark Raasveldt. The foundation keeps the project’s open-source intellectual property and stewardship. DuckLabs says its more than 30-person team will remain together in Amsterdam and continue work on DuckDB, DuckLake, Quack and the wider “Duck Stack.”

Why analytics teams should care

DuckDB is increasingly encountered as an embedded analytical engine rather than as a separately procured database. DuckLabs reports more than one million downloads per day, and says the AWS combination is intended to use DuckDB, DuckLake and Quack to power a new generation of data services. Neither party has announced a product integration, migration requirement or pricing change, however. Amazon’s immediate message is that nothing changes for DuckDB users.

That makes this a governance event before it becomes an architecture event. Teams using DuckDB inside analytics applications, local data workflows or agent tooling should separate four questions:

1. Who owns the code? The DuckDB Foundation continues to hold the open-source project’s intellectual property, according to DuckLabs and a foundation board member quoted in its announcement.
2. Who employs the maintainers? After closing, the DuckLabs team will be part of AWS while Mühleisen and Raasveldt continue leading the team and the project’s technical direction.
3. What is promised versus shipped? DuckLabs says AWS has committed to long-term support for the project. It also plans a foundation technical advisory board and an extension stack that permits code signed by other developers and organizations. Those are roadmap commitments, not completed controls.
4. What changes in production today? Nothing announced. There is no stated forced move to an AWS service, no license change and no published integration schedule.

The practical next step

Do not rewrite an architecture because of the acquisition announcement. Instead, record where DuckDB enters your stack, which extensions you trust, and whether support comes from DuckLabs, another vendor or your own team. Then watch three concrete signals after closing: the composition and authority of the foundation’s advisory board, the design of third-party extension signing, and any AWS service that embeds the Duck Stack.

The deal can add engineering capacity and distribution without closing the project—but that outcome depends on the governance boundary working in practice. For now, the safest reading is precise: AWS is acquiring DuckLabs and its team; the independent foundation retains DuckDB.