Product1 distinct publisher3 min readPublished
DuckLabs keeps its Amsterdam desks and the MIT license still holds. The change is who pays for the roadmap, and what that does to a database compiled into your product.
The Product Desk · Product desk
Compiled by The Product DeskSomething wrong?How this is made
The license is the part that cannot be clawed back. DuckDB, DuckLake and Quack are MIT-licensed, and AWS says they will stay free under those licenses [5]. Code already shipped stays shipped, so a fork is legally available from the day the deal closes. What a buyer gets instead is everything that makes forking unattractive: the maintainers who know the engine, and with them release engineering and bug triage [6].
The dependency is unusual because of where it sits. DuckDB runs inside the application rather than behind a connection string, which is why the SQLite comparison keeps getting made [3]. At three million downloads a day, DuckLabs' own high-water figure [4], that is on the order of a billion pulls a year [15]. If your product compiles DuckDB in, replacing it later means changing shipped client code and every query written against its dialect. That is not a migration you schedule for a quiet week.
Two governance details in the announcement carry more weight than the reassurance around them. AWS will fund a technical advisory board inside the DuckDB Foundation to collect community feedback on the roadmap [12], and it will open the extension ecosystem to signed third-party extensions [13]. Advisory boards advise. Signing implies a signer, and the account of the deal does not say who holds the keys or who can decline to use them. For anyone shipping a build that loads extensions, that is worth an answer before close rather than after.
Then there is the money. DuckLabs funded itself by selling commercial support and feature development to open-source users, and after the deal it no longer needs to, because AWS provides the funds [11]. Whatever you think of the old model, it put a price on the roadmap: a company that wanted a feature could buy engineering time. That channel is being retired and the replacement is a forum. The remaining payer has stated preferences. The collaboration started in early 2025 with DuckDB support in Amazon S3 Tables and SageMaker Lakehouse [9], and Andy Warfield, an AWS vice president and distinguished engineer, gave as his reason that DuckDB is "broadly used and very much loved by S3 customers today" [10]. Hannes Muhleisen, for his part, points to users who may "eventually rely on the Duck Stack without needing to operate a database themselves" [14], which describes a service rather than a library.
None of this requires anyone to act in bad faith to cost you something. The risk to price is ordering: work that makes DuckDB better against S3 landing ahead of parity for other object stores, with the Foundation still named as steward [7] and the payroll elsewhere.
Ranked by verification strength, evidence, and original report placement.
AWS said it has struck an agreement to buy DuckLabs B.V., the Amsterdam-based developer behind the open-source analytical database DuckDB.
DuckDB is an embeddable, high-performance analytical database often referred to as the analytics equivalent of SQLite, because it lets developers run complex SQL queries from inside their applications or client environments without managing server infrastructure.
DuckLabs said DuckDB adoption grew to more than three million downloads per day at one point.
AWS said it remains committed to maintaining DuckDB as an open-source project and to developing the wider ecosystem, including DuckLake and Quack, which will always be free to use under their MIT licenses.
DuckLabs' core engineering team will continue to be based in Amsterdam, led by co-founders Hannes Muhleisen and Mark Raasveldt.
Follow any of these and your For You feed starts watching them — no settings page required.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
One trade outlet relaying primary announcements
Every factual element traces to a single SiliconANGLE article built from the AWS statement and the founders' blog post. The transaction, the licensing pledge, the Amsterdam team continuity and the governance additions are all specific and attributed, which is why this is not near-zero, but there is no second publisher, no deal documentation, no regulatory filing and no independent verification of any figure.
Widely embedded, but scale is self-reported
There are real adoption signals: DuckDB is described as broadly used and loved by S3 customers by an AWS VP, support was shipped in Amazon S3 Tables and SageMaker Lakehouse during a 2025 collaboration, and DuckLabs sustained a business on support contracts and feature partnerships. The quantitative anchor, more than three million downloads per day at peak, is vendor-disclosed and download counts overstate distinct production use, so this sits above the midpoint rather than high.
Reassurance framing runs ahead of verifiable commitments
The write-up presents forward-looking pledges — always free under MIT, continued Foundation stewardship, a technical advisory board, signed third-party extensions, broader reach for the Duck Stack — as settled outcomes, with no dates, policy text, governance detail or independent scrutiny attached, and no examination of what single-funder control means for an embedded dependency. The underlying facts are real and specific, so the overstatement is moderate rather than severe.
Announcement-driven, with publisher's own AWS revenue link on page
All substantive quotes come from the two parties to the transaction: AWS's VP frames the acquisition around community affinity, and the DuckLabs founders frame it as deepened collaboration and expanded reach. The publisher additionally solicits reader AWS spend through its own Marketplace portal and promotes its theCUBE network on the same page, so both the sourcing and the outlet carry alignment with the acquirer's narrative.
Facts clear, durability unknown
Confidence is moderate: the announced facts are unambiguous and attributed, so the what-happened layer is reliable, but with one publisher, no deal terms, no regulatory context and no independent measurement, the consequences for an embedded dependency — license durability, roadmap neutrality, extension policy — cannot be assessed from this cluster.
build
AWS buys DuckDB's engineers; the Foundation keeps the license1 distinct publisher
build
DuckDB is growing a server, and someone on your team will have to run it1 distinct publisher
build
The IR sets the ceiling: why Interlace swapped a DataFrame for a sqlglot AST1 distinct publisher
build
752 Nigerian institutions, shipped as a repo instead of an endpoint1 distinct publisher
Distinct publishers with included, body-backed reporting in this cluster.
1 article · August 26, 2026