AWS acquired DuckLabs—not DuckDB’s open-source governance

AWS’s acquisition of DuckLabs is easy to compress into “AWS bought DuckDB.” The primary sources describe a more precise—and operationally important—split.

The company moved; the projects did not

On August 26, Amazon said it had signed a definitive agreement to acquire DuckLabs, the Amsterdam company behind DuckDB, subject to customary closing conditions. It said DuckDB creators Hannes Mühleisen and Mark Raasveldt would keep leading the team and the open-source project’s technical direction as part of AWS. Amazon’s announcement also said AWS was not acquiring the DuckDB open-source project, which would remain MIT-licensed under its independent foundation.

DuckLabs subsequently updated its announcement to say the process concluded successfully on August 31 and the company would join AWS effective September 1. The DuckDB project’s announcement drew the governance boundary explicitly: DuckDB, DuckLake, Quack and related extensions would remain free and open source under the MIT license and under the stewardship of the nonprofit DuckDB Foundation. The project said its roadmap, licensing and governance model would not change.

That distinction matters for teams embedding local SQL execution inside analytics assistants or data agents. The entity employing much of the engineering team can change without automatically transferring the project’s license or governance. Conversely, an unchanged license does not guarantee that every future engineering priority will remain unchanged in practice.

Three checks for data-agent stacks

Treat governance as a dependency. Record the current license, foundation stewardship and roadmap commitments alongside the engine version your application uses. DuckDB says the foundation will establish an advisory board that can influence project direction; its membership and operation will be a useful signal once published.

Separate code portability from service strategy. An MIT license preserves the right to use, modify and redistribute the projects under that license. It does not answer whether future integrations, support paths or managed offerings will favor one cloud. Teams should keep those commercial choices separate from the technical decision to embed the engine.

Test exit paths now. A data agent often depends on more than a SQL parser: extensions, file formats, connectors and execution behavior can become part of the application contract. Pinning versions, testing representative queries and documenting extension dependencies makes the architecture less sensitive to any vendor’s future priorities.

What remains unresolved

The acquisition is complete, but its practical consequences are not. The defensible conclusion today is narrow: AWS acquired the commercial organization, while the named projects remain MIT-licensed under foundation stewardship according to Amazon, DuckLabs and the project. Whether that formal separation produces durable ecosystem neutrality is something practitioners can measure only through subsequent governance, extension-policy and roadmap decisions—not infer from the logo on the employer.