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.