DuckLabs, the company behind DuckDB, joins AWS as the database stays open source

DuckLabs is joining AWS

DuckLabs, the Amsterdam company behind the DuckDB analytics database, has announced it is joining Amazon Web Services, with the move expected to become effective in early September. According to the company's announcement, which reached the front page of Hacker News, the whole team will stay together in Amsterdam and continue working on DuckDB, DuckLake, Quack, and the community around them.

The central commitment in the announcement is continuity on the open-source side: DuckDB and the other open-source components of the "Duck Stack" will remain free and open source under the MIT license, with the nonprofit DuckDB Foundation continuing to steward the projects and hold their intellectual property.

Why the founders sold

DuckLabs frames the acquisition as the answer to a scaling problem. The company was founded a little over five years ago as a bootstrapped home for the DuckDB team, deliberately avoiding venture capital, and grew to more than 30 people while the database took off. It now logs more than one million downloads per day, according to the announcement.

That success created the strain. The founders write that they worried DuckDB's growth would eventually outpace their ability to support it, and that turning DuckLabs into a much larger sales, support, and operations organization would pull attention away from the engineering and community work that made the project successful. Their commercial partnerships, they note, worked best with highly technical customers; reaching a broader audience would require infrastructure and reach the company did not have.

AWS offered that reach. DuckLabs says the two companies have been working closely together for more than a year, while Andy Warfield, Distinguished Engineer and Vice President at AWS, puts the collaboration at about two years in a quoted statement. Warfield calls the DuckLabs team one of the most technically deep, humble, and high-velocity groups he has worked with, and notes that DuckDB is already broadly used and loved by S3 customers.

Together, the companies plan to build what the announcement calls a new generation of data services on top of DuckDB, DuckLake, and Quack, aiming at users who may never actively choose an analytical database but encounter the technology inside other products. The founders argue DuckDB's adoption can still grow by orders of magnitude.

What stays the same

Several structural guarantees are spelled out. The DuckDB Foundation, which according to board member Peter Boncz of CWI Amsterdam holds all of the intellectual property of open-source DuckDB, continues in its stewardship role. Boncz says he expects AWS's involvement to accelerate the project's innovation, and that the foundation will ensure community voices keep being heard. The team remains in Amsterdam, and the projects will keep serving a broad ecosystem of users, contributors, platforms, and vendors.

Academic users also weighed in via the announcement. Torsten Grust of the Universität Tübingen notes that being able to inspect and tinker with DuckDB's kernel is essential for database research and teaching, and welcomed the project remaining open source under AWS.

What changes

Two concrete governance changes are planned. The DuckDB Foundation will add a technical advisory board, giving leading community members formal input into the project's technical direction. The extension stack is also set to be opened up so that extensions signed by other developers and organizations can run inside DuckDB, loosening what has been a more centrally controlled extension ecosystem. Details, the announcement concedes, are still to be worked out.

Why it matters

DuckDB has become a default tool for embedded analytics, the in-process approach to analytical queries that SQLite represents for transactional workloads. AWS bringing the core team in-house gives it both deep database engineering talent and a technology tightly coupled to the Parquet-and-object-storage workflows that S3 already anchors, which Warfield's comment about S3 customers underlines.

For users, the immediate practical risk looks limited: the license is unchanged, the foundation holds the IP, and the team is intact. The longer-term questions are about governance in practice, how much real influence the community advisory structures carry, and what AWS-built services on the Duck Stack mean for the neutral, vendor-agnostic position that helped DuckDB spread in the first place. Acquisitions of popular open-source projects by hyperscalers have historically invited exactly this kind of scrutiny, and this one will be watched closely by the database community.