DuckLabs to Join AWS: What It Means for the DuckDB Ecosystem

DuckLabs (formerly DuckDB Labs) announced on August 26, 2026 that it will join Amazon Web Services, with the acquisition expected to take effect in early September 2026. Founders Mark Raasveldt and Hannes Mühleisen authored the announcement DuckLabs.

After the acquisition closes, the DuckLabs team of more than 30 will remain together in Amsterdam and continue development on DuckDB, DuckLake, and Quack. The DuckDB Foundation, a nonprofit, will continue its stewardship of the DuckDB projects. DuckDB and the other open-source components of what DuckLabs calls the "Duck Stack" will remain free and open source under the MIT license DuckLabs. The MIT license is permissive and irrevocable, meaning anyone can use, modify, and distribute the code regardless of future corporate decisions.

DuckLabs was founded a little over five years before the August 2026 announcement as a bootstrapped company, fully owned by its founders and development team. The company was renamed from DuckDB Labs to DuckLabs on May 27, 2026, offering services around the DuckDB in-process analytics system directly from its core developers DuckLabs.

DuckDB currently sees more than one million downloads per day DuckLabs. The system has become a standard embeddable analytics engine, meaning it runs inside an application rather than as a separate server. Developers use it for local analytical queries, processing data in formats like Parquet and Apache Arrow, and integrating with lakehouse architectures, which combine the flexibility of data lakes with the management features of traditional data warehouses. DuckLake extends DuckDB's reach into catalog and table-format management, while Quack is the newest component in the stack.

The two organizations have been collaborating for more than a year. In March 2025, DuckLabs and AWS jointly previewed Amazon S3 Tables, a managed tabular storage offering built on Apache Iceberg. AWS subsequently published a blog post demonstrating how to use DuckDB over AWS CloudShell CLI to read tables from an S3 bucket, making the integration concrete for practitioners AWS.

That prior collaboration is the relevant backdrop for the acquisition. AWS has been investing in open table formats and lakehouse infrastructure, and DuckDB is the de facto query engine for local analytics on data stored in those formats. Bringing the DuckLabs team in-house gives AWS direct access to the engineering talent behind that engine.

Several structural commitments in the announcement are designed to address the immediate concern any open-source acquisition raises: whether the acquiring company will maintain licensing and community governance. The DuckDB Foundation's continued stewardship provides an organizational firewall between AWS's commercial interests and the project's governance. Whether that firewall holds in practice will depend on where commit access, roadmap decisions, and contributor dynamics actually land over time.

The decision to keep the team in Amsterdam rather than relocating to Seattle or another AWS hub is worth noting. DuckLabs drew its talent from the CWI (the Dutch national research institute for mathematics and computer science) ecosystem, where Raasveldt and Mühleisen conducted the original research behind DuckDB. Preserving that location maintains the hiring pipeline and team cohesion that produced the project. Amazon has accommodated distributed teams for acquired engineering groups before, so the Amsterdam arrangement is consistent with prior practice.

For DuckDB users, the practical near-term question is whether release cadence, API stability, and community contribution patterns change under AWS ownership. The announcement explicitly commits to continued development of DuckDB, DuckLake, and Quack, and the MIT license guarantees downstream availability. But integration into a hyperscaler's product roadmap can shift priorities in ways that only become visible over multiple release cycles.

The broader context here is a pattern of cloud providers acquiring or deeply aligning with open-source data infrastructure projects. The motivations are straightforward: open-source engines that achieve widespread adoption become strategic integration points, and cloud providers want to own the engineering teams behind them. DuckDB's million-plus daily downloads make it one of the most widely deployed analytical engines in the data ecosystem, which is precisely the kind of footprint a cloud provider values.

The announcement does not disclose financial terms. The acquisition is expected to be effective in early September 2026.