DuckDB has become one of those rare developer tools that people actually talk about with enthusiasm. The embedded analytical database runs inside your process, queries Parquet files directly from S3, handles gigabytes of data without a server, and generally does what SQL databases wish they could. It has over 26,000 GitHub stars and is embedded in everything from data science notebooks to production pipelines.
Now its creators are working at Amazon. DuckLabs, the Amsterdam-based company behind DuckDB, announced on August 26 that it signed a definitive agreement to be acquired by AWS. The deal closed August 31, and the 30-person team — including DuckDB's original authors, Hannes Mühleisen and Mark Raasveldt — officially joined Amazon on September 1.
What AWS Actually Bought
Here's the important distinction: AWS acquired DuckLabs the company, not the DuckDB project. The database itself remains under the nonprofit DuckDB Foundation, distributed under the MIT license, with no change to its roadmap, governance, or licensing. DuckDB, DuckLake, and Quack all stay free and open source.
AWS is explicit about why it wanted the team: DuckDB has become the "connective tissue" across the data estate, the thing that stitches together S3 storage, analytics queries, and downstream tools. The company sees DuckDB as infrastructure, and it wants the people who built it working on making that infrastructure better — particularly in how it integrates with AWS services like S3, Glue, and Athena.
The Foundation Gets Stronger
The acquisition is actually creating structural improvements to the open source project's governance. The DuckDB Foundation is adding a technical advisory board so that organizations building on DuckDB can participate in its direction. The extension ecosystem is also opening up — third-party developers and organizations will be able to sign extensions that run in DuckDB, which was previously restricted.
Mühleisen framed it as giving DuckDB's biggest stakeholders a seat at the table: "whoever is betting on DuckDB can come together in the Board and have a communication channel through the Foundation, which stays independent."
The Community's Concern
Developer reaction has been cautious. The open source community has seen this pattern before — a beloved project's company gets acquired, the project stays open source in the announcement, and then slowly drifts toward cloud-lock-in. MotherDuck, the managed DuckDB cloud service and one of DuckDB's largest commercial adopters, has published a measured response noting both the opportunity and the governance stakes.
The structural safeguards here are stronger than in many prior acquisitions: separate legal entity (the Foundation), MIT license, technical advisory board, and a stated policy that the DuckDB project's roadmap stays independent. That's a more robust firewall than most projects in similar situations have had.
What Changes
In the near term: probably not much. The DuckDB team will continue shipping the project they've been shipping, just with Amazon's resources behind them. AWS integrations will likely improve faster. The extension ecosystem will open. The foundation's advisory board will take shape over the coming months.
What shouldn't change: the core embed-anywhere, no-server-needed design philosophy that made DuckDB worth acquiring in the first place. You don't spend that much to buy something and then immediately make it worse.
The community will be watching closely.