Summary: DuckLabs, the developer of DuckDB, announced on August 26, 2026 that it would join AWS as a subsidiary, with an expected close in early September and no disclosed price. The article stresses that DuckDB-related projects remain MIT open source, the nonprofit foundation keeps the IP, and AWS gains the team behind a widely used embedded analytics engine.
On August 26, 2026, DuckLabs — the company behind DuckDB — announced that it is joining AWS. The founder-owned shop in Amsterdam, staffed by thirty-plus people, is the development force behind the open-source analytical database DuckDB, which is downloaded more than a million times a day, along with DuckLake, Quack, and the surrounding extension stack. Under the deal DuckLabs becomes an AWS subsidiary; it is expected to take effect in early September, and no price was disclosed. 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.
What the Deal Covers
The company was called DuckDB Labs until the rename, which happened only in May. It is small but load-bearing: DuckDB is a single-file, in-process columnar database that runs SQL on Parquet and CSV wherever the data already lives — there is no server to install and no cluster to size. That design is what 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 looks just as clear 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 turns up 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. All intellectual property continues to sit with the nonprofit DuckDB Foundation, which also keeps stewarding 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 DuckDB’s Parent Company
From AWS’s side, the acquisition buys the hottest usage pattern in databases right now: embedded analytics. Running SQL directly against Parquet files on a laptop became routine thanks to DuckDB, and it has turned into 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. License changes and source-available forks were how the industry answered that friction before; DuckDB’s reply is a clean MIT license plus a foundation holding the IP, and that is what makes neutrality and acquisition compatible. AWS taking the team while leaving the license untouched is the kind of outcome that structure was built to allow.
What Changes for Users and the Ecosystem
Three things are worth watching. First, the heart of the arrangement is the governance split: the foundation holds the IP while the company ships the releases, and that division is exactly what allows “acquired by a cloud giant” and “project stays neutral” to sit side by side. Because the license is MIT and the foundation endures, the community keeps the option to fork should trust ever break.
Second, the pace of development is unlikely to slow. Two weeks ahead of this announcement, the team gave a preview of the v2.0 “Cyanoptera” release — server mode, a new storage format, a rewritten parser — and having a well-funded owner makes long-term maintenance more secure rather than less so. The DuckDB blog is already promoting a community meetup in Boston on September 3, another public sign that business continues as usual.
Third, keep an eye on whether the extension ecosystem stays neutral. Opening signed extensions to third parties is a welcome plan, but the real test of how far this deal honors its community promises is whether AWS reserves a privileged lane for its own cloud integrations.