# AWS is acquiring DuckLabs while DuckDB stays under independent foundation stewardship Amazon has signed a definitive agreement to acquire DuckLabs, the company behind DuckDB, while DuckDB, DuckLake, Quack and related projects remain MIT-licensed under the nonprofit DuckDB Foundation. The ownership change puts the commercial team inside AWS without formally transferring the open-source projects themselves. The DuckLabs deal separates company ownership from project governance: AWS gets the team behind DuckDB, while the DuckDB Foundation keeps stewardship and the MIT license stays in place. Builders should watch whether that separation remains meaningful as AWS integrates the Duck Stack into its analytics services. - Status: Active - Published: 2026-09-01T06:27:30+12:00 - Updated: 2026-09-01T06:27:30+12:00 - Categories: Web Development, Cloud & Infrastructure, Cloud Platforms, Developer Tools, Databases & Storage - Tags: AWS, DuckDB, DuckLabs, M&A, open source - Canonical HTML: https://beyondthe.news/dossiers/aws-acquires-ducklabs-duckdb-foundation-open-source-governance ## What changed On August 26, Amazon announced a definitive agreement to acquire DuckLabs, the Amsterdam company formed by DuckDB creators Hannes Mühleisen and Mark Raasveldt. The transaction is expected to become effective in early September, subject to customary closing conditions. DuckLabs says its team will remain together in Amsterdam and continue work on DuckDB, DuckLake, Quack and the wider ecosystem. Both AWS and the DuckDB project say the open-source projects will remain under the MIT license and continue under the stewardship of the independent nonprofit DuckDB Foundation. AWS says it plans to combine the team and technology with its scale and analytics services. ## Why it matters DuckDB has become infrastructure used well beyond a single commercial product, so the acquisition creates two distinct dependencies for builders: the company developing much of the software will be owned by a hyperscaler, while the code and formal project governance remain outside that company under an open-source foundation. That structure reduces immediate licensing risk but does not eliminate strategic influence. AWS can fund development, hire the core team and create deeper integrations with services such as S3, Athena and Redshift. Builders relying on DuckDB should therefore distinguish legal openness from practical project concentration and watch how roadmap, interoperability and commercial packaging evolve after closing. ## AWS is buying the company, not the open-source foundation AWS has signed an agreement to acquire DuckLabs, whose founders created DuckDB and whose team performs substantial development work across the Duck Stack. The nonprofit DuckDB Foundation remains separate. DuckDB, DuckLake, Quack and related open-source components are expected to remain MIT-licensed under that foundation’s stewardship. ## The core team is staying together DuckLabs says the Amsterdam team will remain intact and continue developing the same projects. AWS says Mühleisen and Raasveldt will continue leading the team and the open-source project’s technical direction. That continuity reduces near-term maintenance risk, while also concentrating the core development team inside AWS. ## AWS has an obvious integration path AWS already provides the object storage and analytics services around which many DuckDB workloads operate. Its announcement points toward deeper use of DuckDB technology alongside AWS data services. For builders, the likely upside is better integration and investment; the corresponding platform-risk question is whether optimization increasingly favors AWS-native workflows over competing clouds and storage systems. ## Open licensing is a strong safeguard, but not the whole governance story The MIT license means existing code cannot simply be made proprietary retroactively, and the Foundation remains an independent steward. However, open-source projects can still be shaped by where maintainers spend time, which integrations receive first-class attention and how commercial services are packaged. Teams with critical DuckDB dependencies should monitor contribution diversity and foundation governance rather than looking only at the license text. ## Key details - Amazon announced on August 26, 2026 that it signed a definitive agreement to acquire DuckLabs. - DuckLabs expects the transaction to become effective in early September, subject to customary closing conditions. - DuckLabs says its team will remain together in Amsterdam. - DuckDB, DuckLake, Quack and related open-source components are expected to remain under the MIT license. - The nonprofit DuckDB Foundation will continue stewardship of the open-source projects. - AWS says DuckDB’s creators will continue leading the team and technical direction. - DuckLabs says DuckDB is running at more than three million downloads per day, underscoring the ecosystem scope affected by the ownership change. ## Builder takeaways - Do not treat the acquisition as an immediate licensing migration: the projects remain MIT-licensed and Foundation-governed according to both parties. - If DuckDB is a critical dependency, track foundation governance, maintainer diversity and cross-cloud compatibility after the deal closes. - Keep data and deployment architecture portable enough that tighter AWS integrations remain optional rather than mandatory. - Evaluate any new AWS-managed DuckDB services separately from the open-source engine; commercial packaging can create different lock-in economics even when the underlying code remains open. - For extension authors, watch whether roadmap priorities or distribution mechanisms change as the core team moves inside AWS. ## What to watch - Formal closing of the acquisition and any disclosed structural terms. - The DuckDB Foundation’s planned stakeholder advisory board and evidence of continued independent governance. - New AWS integrations or managed services built around DuckDB, DuckLake or Quack. - Whether non-AWS cloud integrations and community contributions continue receiving comparable attention. - Changes in commercial support, hosting or enterprise packaging around the Duck Stack. ## Uncertainties - The transaction had not yet closed at the time of this research pass and remains subject to customary closing conditions. - Neither party disclosed the acquisition price or detailed corporate structure. - The MIT license and Foundation governance protect the open-source codebase, but they do not guarantee future engineering priorities will remain cloud-neutral. - AWS has described integration ambitions broadly; specific S3, Athena, Redshift or other product changes are not yet fully defined. ## Sources - [DuckLabs to Join AWS, Projects to Remain Open Source](https://ducklabs.com/news/2026/08/26/ducklabs-to-join-aws) — DuckLabs · primary announcement · 2026-08-26T00:00:00+12:00. DuckLabs announcement covering expected closing, team continuity, licensing and Foundation stewardship. - [AWS and DuckLabs: Building the future of analytics together](https://aws.amazon.com/blogs/big-data/aws-and-ducklabs-building-the-future-of-analytics-together/) — Amazon Web Services · primary announcement · 2026-08-26T00:00:00+12:00. AWS confirmation of the definitive acquisition agreement and its integration rationale. - [DuckLabs to Join AWS, Projects to Remain Open Source](https://duckdb.org/2026/08/26/ducklabs-to-join-aws) — DuckDB · primary project statement · 2026-08-26T00:00:00+12:00. DuckDB project statement that roadmap, licensing and governance remain under the independent Foundation.