← Back to feed

DuckLabs, the 30-person Amsterdam company behind DuckDB, will join Amazon Web Services in early September. Founders Mark Raasveldt and Hannes Mühleisen announced the deal on Wednesday alongside a firm commitment: DuckDB, DuckLake, and the Quack ecosystem will stay MIT-licensed, with the DuckDB Foundation continuing stewardship of the open-source projects.

DuckDB now sees more than 1 million downloads per day. The team built it as a bootstrapped, founder-owned company since 2021, deliberately avoiding venture capital to keep the technology-first focus intact. That decision shaped what DuckDB became: an in-process OLAP engine that runs in browsers, Python notebooks, production ETL, and embedded analytics without requiring a server.

Why the Deal

The announcement was candid about the limits of the existing model. DuckLabs was becoming a bottleneck for a project that had grown beyond what a 30-person team could support. Scaling into a larger sales and support organisation would have pulled engineering attention away from the open-source core. AWS offers the resources and distribution reach to pursue that scale without forcing the team to become something else.

For AWS, the acquisition brings in the team that built the most widely used in-process analytical database in the industry. DuckDB sits at an increasingly important intersection: data pipelines feeding AI training workloads, analytics stacks running inside Jupyter and SageMaker environments, and embedded analytics that do not need a managed database service. Amazon gets the core engineering team and the architectural knowledge behind DuckDB’s columnar vectorised execution engine.

What Changes, What Stays

The Amsterdam office stays. The team stays together. The DuckDB Foundation holds the intellectual property and continues to govern the open-source projects. DuckDB, DuckLake, and Quack remain free under the MIT license — not a source-available licence, not a commons clause, not a delayed open-core. MIT.

Raasveldt and Mühleisen framed the deal as the end of one chapter and the beginning of another. The language tracks with similar open-source acquisitions where the acquiring company promises no change to the licence and keeps the team intact. The DuckDB Foundation structure provides more structural protection than most such promises, since the IP sits outside AWS’s direct control.

Context

DuckDB’s growth into AI-adjacent data infrastructure has been consistent and largely quiet. It is not a frontier model and does not appear in benchmark headlines. But it handles the data movement and transformation layer that sits upstream of most AI training and evaluation pipelines. An AWS-backed DuckLabs with more resources to invest in integrations, cloud storage formats, and enterprise support is a meaningful shift in who controls that layer.

The deal also closes a peculiar chapter in open-source history: a project with 1 million daily downloads, backed by a company that never took outside capital, being acquired without anyone having held the threat of commercialisation over the community. The foundation structure made that cleaner than most.