AWS Bought DuckDB's Team. The Database Wasn't for Sale.

TL;DR

On 26 August 2026, AWS announced a definitive agreement to acquire DuckLabs, the Amsterdam company behind DuckDB. Amazon's own announcement includes a sentence most acquisition posts do not: "We are not acquiring the DuckDB open source project." It stays free, MIT-licensed, and owned by the independent DuckDB Foundation. AWS gets a team of roughly 30 people that never took a dollar of venture capital. The interesting part is not the deal. It is the corporate structure that made the deal boring, which is exactly what every other open-source founder should be studying.

What actually moved

The company moved. The code did not.

Amazon's announcement is specific: "The talented DuckLabs team, based in Amsterdam, will join AWS. Hannes Mühleisen and Mark Raasveldt, who created DuckDB and co-founded DuckLabs, will continue leading the team." Then the clause that does the real work: the DuckDB project "will remain free and open source under the independent DuckDB Foundation (the non-profit that oversees DuckDB) and available under the MIT license as it does today."

The founders said the same thing in their own words the same day: "DuckDB, DuckLake, Quack, and all the other extensions will remain free and open source software under the MIT license under the stewardship of the non-profit DuckDB Foundation," and "there are no changes for our projects' roadmap, licensing, and governance model." Terms were not disclosed. The transaction is expected to close in September 2026.

The split that made this a non-event

Most open-source acquisitions are frightening because the company and the code are the same asset. Buy the company, get the copyright, and the next release can be Business Source License 1.1 with a four-year delay. That story has played out often enough that "acquired by a hyperscaler" now reads as a countdown.

DuckDB was structured to make that move unavailable. The DuckDB Foundation is a Dutch non-profit that, in its own words, "holds the core intellectual property and trademarks of DuckDB, DuckLake and Quack projects." The software is distributed under the permissive MIT license. The Foundation is a separate legal entity from the company that employs the maintainers.

Think of a band that owns its own masters through a publishing entity it set up before signing anything. A label can sign every member of the band. It still cannot repackage the back catalogue, because the catalogue was never in the deal. AWS hired the musicians. The Foundation kept the tapes.

This is not a clever retrofit done during due diligence. It has been the arrangement for years, which is why the announcement could be one paragraph instead of a crisis-communications exercise.

Thirty-odd people, zero venture capital

DuckDB started in 2019 as a research project by Mühleisen and Raasveldt at CWI, the Dutch national research institute for mathematics and computer science. The company they built around it turned down repeated venture offers and ran on support and partnership contracts instead, growing past 30 employees without an outside round.

The contrast is sitting right there in the same ecosystem. MotherDuck, founded in 2022 to build a serverless cloud platform on the same MIT-licensed database, raised $47.5 million in combined seed and Series A funding in November 2022 at a $175 million valuation, then $52.5 million in September 2023 at a $400 million valuation. Roughly $100 million of venture capital, with Andreessen Horowitz among the investors.

Neither path is automatically correct, and MotherDuck is a different business selling a different thing. But it is worth noticing which one ended up owning 100% of an asset AWS wanted, with nobody to split the proceeds with.

Why AWS wanted it

Because it was already running on it. Mai-Lan Tomsen Bukovec's post on the AWS Big Data blog gives the number: "Since we launched Quick in October 2025, we have processed over 2.5B queries using our custom Quick query engine with the DuckDB integrations and optimizations." AWS also says it will "look at how we can integrate DuckDB's performance and simplicity in our other AWS services across data and analytics."

That is the honest version of the strategic rationale. A dependency that serves billions of queries inside your own product, maintained by a 30-person shop in Amsterdam, is a supply chain risk on a spreadsheet somewhere. Acquiring the maintainers converts it into a line item.

The adoption curve explains the urgency. DuckDB's own adoption write-up reports almost 25 million monthly downloads on PyPI alone, an estimated 20-plus Fortune 100 companies using it, and a jump in developer usage from 1.4% to 3.3% between the 2024 and 2025 Stack Overflow Developer Surveys.

What changes for you

Today, nothing. The license is MIT, the copyright holder is unchanged, and the version you pinned keeps working exactly as it did. DuckDB 1.5.5 shipped on 22 July 2026 and the release cadence has been roughly monthly all year.

Two things are genuinely new and worth tracking. First, the Foundation says it will establish "a stakeholder advisory board which can influence the direction of the projects," which is a governance body that did not exist before. Second, the founders say they are "lifting the limitations of community support," which is the concrete upside of having Amazon's payroll behind a team that previously had to ration its unpaid help.

The caveats, straight

• The deal has not closed. AWS says it expects to close "shortly, subject to customary closing conditions," with September 2026 the stated window. Everything above is an announcement, not a completed transaction.
• No price. Terms were not disclosed by anyone, so any valuation you read is someone's guess.
• Day-one promises are the cheapest kind. "Nothing changes" is true of nearly every acquisition on the day it is announced. The MIT license and the Foundation's ownership are real structural protections; the roadmap commitments are goodwill.
• Board composition is the question to actually ask. The Foundation's public board is Hannes Mühleisen as chair, Mark Raasveldt, and database researcher Peter Boncz. Two of those three are joining AWS. The entity stays legally independent and the license is irrevocable for shipped code, but "independent non-profit" and "staffed by employees of the acquirer" are both accurate descriptions of the same thing. The promised advisory board is presumably the answer to exactly that objection.
• DuckDB Labs became DuckLabs in May 2026. Three months later it became AWS. Only one of those was a rebrand.

Key Takeaways

• AWS announced on 26 August 2026 that it will acquire DuckLabs, the Amsterdam company behind DuckDB, with the deal expected to close in September 2026 and terms undisclosed.
• Amazon states explicitly that it is not acquiring the DuckDB open source project, which stays MIT-licensed under the independent DuckDB Foundation along with DuckLake and Quack.
• The reason that sentence is possible is a years-old structural split: the Foundation holds the copyright and trademarks, the company holds the payroll. Founders shipping open source should copy the pattern, not the exit.
• DuckLabs never raised venture capital and grew past 30 people on support contracts, while MotherDuck raised roughly $100 million building a cloud product on the same database.
• AWS was already a heavy user: over 2.5 billion queries through its Quick engine with DuckDB integrations since October 2025.
• Nothing breaks for existing users, but watch the new stakeholder advisory board and who sits on the Foundation board, since two of its three members are joining the acquirer.

Sources: About Amazon, "AWS to acquire DuckLabs", AWS Big Data Blog, "AWS and DuckLabs: Building the future of analytics together", DuckDB, "DuckLabs to Join AWS, Projects to Remain Open Source", DuckDB Foundation, DuckDB, "Adoption Metrics and Benchmark Results for DuckDB v1.4 LTS", DuckLake, DuckDB release history, SiliconANGLE, MotherDuck funding history