Amazon has signed a definitive agreement to acquire DuckLabs, the Amsterdam company behind DuckDB, with closing expected in early September. The open-source project is explicitly excluded from the deal: DuckDB and the rest of the Duck Stack stay free and MIT-licensed under the nonprofit DuckDB Foundation, which holds the intellectual property. The company is being bought; the database is not.
Key facts
- DuckLabs, a bootstrapped, founder-owned team of more than 30 people in Amsterdam, joins AWS. Closing expected early September 2026.
- DuckDB, DuckLake and Quack remain MIT-licensed under the nonprofit DuckDB Foundation, which holds the project's IP and was created when DuckLabs spun out of CWI Amsterdam.
- DuckLabs reports more than one million downloads every day.
- Announced August 26, 2026. Primary sources: DuckLabs, duckdb.org, and Amazon.
The hook. Most "open source project acquired" stories are about a licence that is about to change. This one is about a legal structure built five years ago specifically so it could not.
Background. DuckDB is an embedded analytical database -- think of it as SQLite for analysis rather than storage. It runs inside your process with no server to install, and it has quietly become the default tool for local data work, notebooks, and a large share of the tooling that AI teams use to inspect datasets and evaluation results. It came out of the Database Architectures research group at CWI, the Dutch national research institute for mathematics and computer science.
What happened. DuckLabs was founded a little over five years ago "to give the team behind DuckDB a stable, long-term home." The founders describe turning down venture capital deliberately: "We chose a different path: a bootstrapped company, fully owned by its founders and development team." That decision, they write, "gave us the freedom to build patiently, to put the technology first, and to grow without losing sight of why we started."
The reason they are selling is unusually direct. "As founders, we worried that DuckDB's growth would eventually outpace our ability to support it. That our small company could become a bottleneck for the project, the team, and the people building businesses on top of it." And: "We also worried that scaling DuckLabs into a much larger sales, support, and operations organization would pull our attention away from the technical work and open-source community that made DuckDB successful in the first place."
How it works. The protective mechanism is the foundation. When DuckLabs spun out of CWI, a nonprofit was created to hold all intellectual property for open-source DuckDB. The company built products and services on top; the foundation owned the thing itself. That means an acquirer buying the company buys the team, the commercial contracts and the roadmap influence -- but not the right to relicense the code, because the company never held it. It is the difference between buying a restaurant and buying the recipe: you get the kitchen and the chefs, but the cookbook belongs to somebody else.
Governance is widening rather than transferring. DuckLabs describes a new stakeholder advisory board; DuckDB's own community support policy calls it a Technical Advisory Board. The label is still being settled, but the stated direction is more community input into project direction while the foundation keeps IP control.
Why it matters. Andy Warfield, Distinguished Engineer and Vice President at AWS, framed the appeal in the announcement: "DuckDB is an incredible open source project with an amazing community; it is broadly used and very much loved by S3 customers today. After about two years of working closely with Mark, Hannes and the whole team at DuckLabs I'm excited at the opportunity to help the project have an even broader impact." Peter Boncz, the CWI representative on the DuckDB Foundation board, was more pointed about the guarantee: "When DuckLabs spun out of CWI, we created this foundation, which holds all IP of open-source DuckDB, and will continue to do so."
For anyone who works with data, the practical read is that the tool is safe and the support is about to get much better funded. DuckLabs says AWS "has committed to supporting the continued development of DuckDB and its wider community for the long term," and the project's own post frames the deal as room to invest more in documentation, education and contributor support.
The honest caveat. The licence is protected; the roadmap is not. The people who decide what DuckDB works on next now draw AWS salaries, and AWS describes the deal as a way to make its analytics "faster, simpler, and more cost-effective." Foundation ownership prevents relicensing. It does not prevent prioritization drifting toward the features that make S3 queries faster and away from the ones that only matter to someone running DuckDB on a laptop. That is a slower and quieter risk than a licence change, and a harder one to notice.
Originally published on Ground Truth, where every claim is checked against the primary source.
