On August 26, 2026, DuckLabs — the company behind DuckDB — announced it is joining AWS. The Amsterdam-based, founder-owned shop of thirty-plus people is the development force behind the open-source analytical database DuckDB, which now sees more than a million downloads a day, plus DuckLake, Quack, and the surrounding extension stack. The deal makes DuckLabs an AWS subsidiary, is expected to be effective in early September, and carries no disclosed price. The announcement is signed by DuckDB founders Mark Raasveldt and Hannes Mühleisen themselves, and the news cleared 1,100 points on Hacker News within hours.
The Deal
DuckLabs used to be called DuckDB Labs; the rename happened only in May. The company is small but load-bearing: DuckDB is a single-file, in-process columnar database that runs SQL against Parquet and CSV wherever the data already lives — no server to install, no cluster to size. That design made it the de facto standard for embedded analytics, running on data scientists’ laptops and inside other vendors’ products alike. According to the announcement, the team had been working with AWS for over a year, so the acquisition formalizes an existing collaboration rather than starting one. AWS VP Andy Warfield called the DuckLabs team one of the most “technically deep, humble, and high-velocity” he has ever worked with.
For a bootstrapped company, the logic is also easy to see from the other side of the table. DuckDB’s download curve has been climbing for years, and the project just previewed its largest structural release — backing a growing team and a flagship rewrite takes money at exactly the moment a buyer arrives with an open checkbook and a promise to leave the license alone.
The Foundation Keeps the IP
The open-source community’s first question — what happens to the license — gets a direct answer: DuckDB, DuckLake, Quack, and the extensions remain free and open source under MIT, with no changes to roadmap, licensing, or governance model. The nonprofit DuckDB Foundation continues to hold all intellectual property and steward the projects. Peter Boncz of CWI, a foundation board member, was blunt about it: “we created this foundation, which holds all IP of open-source DuckDB, and will continue to do so.” Two concrete changes follow: the foundation will set up a stakeholder advisory board that can influence project direction, and limits on community support are being lifted, with third-party signed extensions planned.
Why AWS Bought the Company Behind DuckDB
From AWS’s side, the acquisition buys the hottest usage pattern in databases right now: embedded analytics. DuckDB made it routine to run SQL directly against Parquet files on a laptop, and it has become the component that data tools compete to embed. Pulling the team in connects that growth curve to AWS’s data services portfolio. Ecosystem partners reacted positively — Jordan Tigani of MotherDuck said “Amazon putting its weight behind DuckDB is going to add a ton of momentum and strengthen the ecosystem,” and Fivetran CEO George Fraser called Amazon “the ideal home for DuckLabs.”
The deal also reads as a quiet answer to a decade of open-source friction between database companies and cloud providers. The industry’s previous responses to that friction were license changes and source-available forks; DuckDB’s answer is a clean MIT license plus a foundation holding the IP, which makes acquisition-compatible neutrality possible. AWS buying the team without touching the license is the kind of outcome that structure was built to allow.
What Changes for Users and the Ecosystem
Three things to watch. First, the governance split is the core of the arrangement: the foundation owns the IP, the company ships the releases, and that division is what lets “acquired by a cloud giant” and “project stays neutral” coexist. MIT plus the foundation means the community can always fork if trust ever breaks.
Second, development pace will most likely not slow. Two weeks before this announcement the team previewed the v2.0 “Cyanoptera” release — server mode, a new storage format, a rewritten parser — and a well-funded owner makes long-term maintenance more secure, not less. The DuckDB blog is already advertising a community meetup in Boston for September 3, which signals business as usual in public too.
Third, watch the neutrality of the extension ecosystem. The plan to open signed extensions to third parties is welcome, but whether AWS gives its own cloud integrations any privileged lane will be the real test of how much this deal honors its community promises.
Sources
- DuckLabs to Join AWS — DuckLabs announcement
- DuckLabs to Join AWS, Projects to Remain Open Source — DuckDB blog
- AWS and DuckLabs: Building the Future of Analytics Together — AWS Blog
- AWS Acquires DuckLabs — Hacker News discussion
AI-assisted summary compiled from the sources above, reviewed by a human before publishing.