“DuckDB is joining AWS” is quick shorthand, but it mixes a company, a project and a foundation.
What is expected to become part of Amazon Web Services in early September 2026 is DuckLabs, the Amsterdam company employing the development team.12 DuckDB, DuckLake and Quack remain under the stewardship of the nonprofit DuckDB Foundation, which says it holds the projects' core intellectual property and trademarks.3
The separation does not manufacture independence by itself. It does give the community more concrete things to inspect than a press-release promise.
Four levers will be more useful than the logo on anyone's payslip: IP ownership, fork rights, roadmap arbitration and extension distribution.
The IP stays outside
The DuckDB Foundation states that it holds the core IP and trademarks for DuckDB, DuckLake and Quack.3
The LICENSE file in the DuckDB repository names “Stichting DuckDB Foundation” as copyright holder and grants the MIT license.4
Peter Boncz, the third Foundation board member, makes the same point in the transaction announcement. The foundation was created when DuckLabs spun out of CWI and will continue to hold the IP of open-source DuckDB.1
AWS therefore gets the operating company and team. Rights over already released code and project trademarks follow a different ownership chain.
The license protects the fork
DuckDB is distributed under MIT, which permits use, copying, modification, distribution, sublicensing and sale of copies as long as the license notice remains.4
DuckLake states the same license for its specification and DuckDB extension.5 The Foundation summarizes its position as “MIT, irrevocably” for DuckDB, DuckLake and Quack.3
For versions already released, the exit route is real: a community may keep, modify and redistribute what it received.
That is materially different from a source-available license that restricts particular commercial uses or competing cloud services.
Fork rights still provide no maintainers, time or infrastructure. Legal permission is not a maintenance team.
That is what the DuckLabs team's move to AWS changes materially.
The board overlaps
The Foundation is currently run by three people: Hannes Mühleisen, Mark Raasveldt and Peter Boncz.3
Mühleisen and Raasveldt are DuckDB's co-creators and the authors of the DuckLabs announcement.1 Their team is expected to become part of AWS.2
Company and foundation are separate entities. Their people, priorities and expertise still overlap heavily.
For a young project, that overlap is unsurprising. It simply makes the next governance change more important than the change of employer.
DuckLabs says the Foundation will add a technical advisory board so leading community members can provide input on technical direction.1 The press release also describes an advisory board through which commercial users can provide roadmap input.2
Its future membership, powers and arbitration mechanisms have not yet been detailed.12
Extensions are the practical test
Extensions may become the most concrete test of the new governance.
DuckLabs says it plans to open the stack so extensions signed by other developers and organizations can run in DuckDB.1 This is still a plan in the announcement, not a shipped feature.1
A project can stay readable and forkable while concentrating substantial power in official distribution: signing, catalog inclusion, default installation paths and extension documentation.
Opening that path would reduce dependence on a single maintainer or employer without asking users to fork all of DuckDB.
For everyday ecosystem pluralism, that will say more than counting MIT-licensed lines.
AWS brings a useful bias too
The announcement does not hide AWS's industrial interest.
DuckLabs and AWS have collaborated since early 2025, including work on DuckDB support for Amazon S3 Tables and Amazon SageMaker Lakehouse.2 The founders want the Duck Stack inside a new generation of analytics services, backed by AWS infrastructure, customer reach and resources.12
That bias can be productive. A large user paying maintainers often accelerates an open-source project.
The risk appears when one large user's needs become the common roadmap without a visible decision process.
The Foundation already sells supporter tiers that explicitly give organizations a voice in development, with Silver membership from €10,000 per year and Gold from €100,000.3 Commercial influence is therefore not hidden from the model. The useful question is whether several actors can exercise it in practice or whether the core team's employer inevitably dominates.
Four tests instead of trust
When the main development company behind an open-source project joins a giant vendor, asking only “is it still open source?” misses part of the problem.
For DuckDB, the legal answer currently looks straightforward: the announced projects remain MIT-licensed and their IP sits in a separate foundation.134
The more interesting questions begin afterwards:
- can the Foundation decide against an AWS priority?
- does the new advisory board gain a concrete role?
- can third-party extensions be signed and distributed without depending on AWS?
- do outside contributors continue gaining influence over core components?
A license file cannot answer any of those day-to-day power questions.
That is exactly why DuckDB's structure is worth watching. It creates several places where independence can be measured instead of asking the community to trust one sentence in a press release.