AWS Acquires DuckLabs, the Team Behind DuckDB — What It Means

Amazon has signed a definitive agreement to acquire DuckLabs, the Amsterdam company behind DuckDB, the open-source analytical database now recording more than one million downloads a day. The price wasn't disclosed, and the deal is expected to close in early September. But the story worth telling isn't the money — it's that one of the most-loved open-source data projects now sits inside a cloud giant.

To understand why the community split into two camps overnight, you have to look at DuckDB's position and the people behind it.

The deal: who, when, and for how much

DuckLabs was founded a little over five years ago by Hannes Mühleisen and Mark Raasveldt — the two creators of DuckDB — to give the project a stable, long-term home. Unlike most database startups, DuckLabs took no venture capital: it is bootstrapped and fully owned by its founders and team. From a small group, it grew to more than 30 people in Amsterdam, all still focused on DuckDB and its community.

The agreement was announced on August 26, 2026. The team stays together in Amsterdam, and Mühleisen and Raasveldt continue leading the project. Financial terms were not disclosed — common in deals where the buyer is after technology and people rather than revenue.

Andy Warfield, Distinguished Engineer and VP at AWS, called the DuckLabs team "one of the most technically deep, humble, and high-velocity teams" he's worked with. That praise carries weight, because Warfield is no outsider — AWS and DuckLabs have been working together for more than a year.

Why AWS wants DuckDB

DuckDB is a rare kind of project: an embedded OLAP engine that runs inside your application's process and queries data in Parquet or S3 using SQL, shipped under the MIT license. No server, no cluster, no ops burden — drop in a library and start querying.

What AWS sees is the "Duck Stack" — DuckDB (the embedded engine), DuckLake (an ACID lakehouse format), and Quack (a client-server protocol). DuckDB 2.0, released in August, marks the shift from embedded library to a full server analytics platform. For AWS, this slots directly into its data strategy: DuckDB is the natural gateway for querying data that lives on S3, and AWS wants the Duck Stack to underpin a new generation of analytics services competing with Snowflake and Databricks.

This relationship isn't new. In March 2025, AWS and DuckDB shipped the Amazon S3 Tables preview — an early sign of the deep integration the two teams had been exploring for a while.

The open-source question: is this time different?

This is where the community worries, and the worry has basis. AWS has a history of forking open-source projects when vendors change licenses: OpenSearch was born after Elasticsearch moved from Apache 2.0 to SSPL/Elastic, and Valkey after Redis dropped BSD. The "Amazon buys it and closes it" scenario gets debated every time a popular database project lands in the hands of a big vendor.

DuckDB is different in two ways. First, MIT is a permissive license — once released, the code can't be clawed back; the community can always fork. Second, and more importantly, all the intellectual property of open-source DuckDB sits with the DuckDB Foundation, an independent nonprofit — not with DuckLabs. Peter Boncz, who leads the database architectures group at CWI Amsterdam and sits on the foundation board, confirmed this explicitly.

In other words, the real risk isn't "will DuckDB be closed." That answer is almost certainly no. The risk is roadmap and resources: when the core team draws salaries from AWS, development priorities will naturally tilt toward AWS integration rather than strict neutrality toward every vendor.

The awkward part: MotherDuck and other vendors

One detail that's easy to miss: MotherDuck — the commercial cloud company built on DuckDB, founded by former Google BigQuery engineer Jordan Tigani — now competes directly with the new owner of its own upstream.

Tigani responded positively, calling it "great news for those of us who believe in DuckDB as the platform on which the future of analytics is being built." The strategic reality is more complicated. MotherDuck builds its product on DuckDB. Meanwhile AWS now both employs the DuckDB team and sells competing analytics services. Vendor neutrality — the core value that made DuckDB the foundation of choice for so many companies — is now in question at the exact moment the project is growing fastest.

DuckLabs offered two commitments to reassure the community: a technical advisory board for the foundation, and opening the extension stack so third-party developers can sign and publish extensions. Those are signals in the right direction, but whether they hold depends on how they're executed once AWS's priorities surface.

What it means for developers

The good news first: if you use DuckDB, nothing changes in the short term. Your code keeps running, the license stays MIT, the foundation keeps the IP. If anything, AWS's resources could accelerate S3-native features and speed up development — something a 30-person company struggles to do alone.

But there are three things to watch:

• Where the roadmap leans. If features prioritizing AWS integration (Athena, Glue, Redshift) arrive in rapid succession while support for non-AWS storage slows down, that's the clearest signal.
• Whether the advisory board is actually independent. Its composition and veto power will determine whether community voices are preserved or merely ceremonial.
• How other vendors react. MotherDuck, Databricks, and other companies building on DuckDB will adjust strategy — potentially a fork, potentially a pivot.

If you're evaluating DuckDB for your stack, this isn't a reason to stay away. It's a reason to understand the license and ownership structure before committing long-term — a lesson that repeats with every piece of critical infrastructure.

What to know

• Amazon signed a deal to acquire DuckLabs on August 26, 2026, expected to close in early September; terms undisclosed.
• DuckDB sees over one million downloads a day and stays MIT-licensed; the independent DuckDB Foundation holds all open-source IP.
• AWS wants the "Duck Stack" (DuckDB + DuckLake + Quack) to power analytics that competes with Snowflake and Databricks.
• The real risk isn't the license — it's the roadmap and vendor neutrality once the core team joins AWS.
• MotherDuck and other DuckDB vendors now compete with their own upstream.

The remaining question isn't whether DuckDB stays open source. It will. The question is whether a foundational project funded by a single cloud vendor can, over the long run, stay neutral for everyone — or only neutral on paper.

---

Content assisted by AI (Amy 🌸). Reviewed by the author.