DuckDB's Makers Are Joining AWS

The little database that got a very big roommate

Roughly a million times a day, a developer downloads a piece of free software called DuckDB and uses it to slice through data on a laptop. It is fast, it is free, and it is beloved by the sort of people who argue about databases at parties. Now the small Amsterdam company behind it, DuckLabs, is joining Amazon Web Services, the cloud arm of Amazon. The move is expected to take effect in early September 2026.

If you have never heard of DuckDB, here is the short version. It is an analytical database, which means it is built for asking big questions of large piles of data rather than for running a live shopping cart. Its trick is that it runs inside whatever you are already using, with no server to set up and no infrastructure to babysit. That simplicity is why it spread so quickly.

What is actually happening

DuckLabs is a bootstrapped company, meaning the founders and developers own it themselves rather than answering to venture capital investors. That was a deliberate choice five years ago, and the team grew to more than 30 people in Amsterdam. The whole crew is staying together in Amsterdam and continuing work on DuckDB and its sibling projects, DuckLake and Quack.

The headline reassurance is this. DuckDB and the other open-source parts of what the team calls the Duck Stack will stay free and open source under the MIT license, a permissive license that lets anyone use and modify the code. Stewardship stays with the nonprofit DuckDB Foundation, which holds the intellectual property and was set up when DuckLabs spun out of the Dutch research institute CWI.

Why the founders made the move

The team is candid about the reasoning. As DuckDB kept growing, they worried their small company would become a bottleneck. Their partnerships worked best with highly technical organizations, often ones with deep database expertise of their own. Reaching everyone else means solving more specialized problems, serving different industries, and pouring far more money into infrastructure than a bootstrapped shop comfortably can.

Scaling into a large sales and support operation also risked pulling attention away from the technical and community work that made DuckDB popular in the first place. DuckLabs and AWS had already been working closely together for more than a year, which gave both sides confidence. AWS has committed to supporting DuckDB and its community for the long term, and plans to use the Duck Stack to help power a new generation of data services.

Why it matters, and the fair caveats

Big companies acquiring beloved open-source projects makes communities nervous, and rightly so. Promises are easy on announcement day. The credible signals here are structural rather than sentimental. The DuckDB Foundation, not AWS, holds the code, and Peter Boncz of CWI, a foundation board member, says the foundation will keep doing so and will make sure the community's voice is heard.

There is also support from people who compete in this space. Jordan Tigani, CEO of MotherDuck, and George Fraser, CEO of Fivetran, both welcomed the move, with Fraser calling Amazon's track record of working across the whole cloud ecosystem a reason to expect DuckDB to keep thriving as a neutral tool. That vendor neutrality is the thing worth watching, because a database everyone trusts is only useful if it stays usable by everyone.

What is coming next

The team plans to expand rather than lock down. The DuckDB Foundation will add a technical advisory board so leading community members can weigh in on direction. The team also plans to open the extension stack, meaning add-ons signed by other developers and organizations will be able to run inside DuckDB. Many details are still being shaped, and the team says it will share more as plans firm up.

The real test will play out over the next couple of years, in commit histories and community forums rather than press releases. If AWS resources genuinely accelerate the open-source project without quietly steering it toward Amazon's paid services, this becomes a template worth copying. If not, the community holds the code and can say so. For now, the duck keeps swimming, just in a much bigger pond.