Amazon AWS announced on August 26, 2026 that it has signed a definitive agreement to acquire DuckLabs, the thirty-person Amsterdam team behind the open-source analytical database DuckDB. The deal is expected to close in early September, with founders Hannes Mühleisen and Mark Raasveldt continuing to lead the team and the project's technical direction, and the team remaining in Amsterdam. The news landed almost simultaneously across the AWS Big Data blog, the DuckLabs announcement, and outlets like GeekWire and The Register, signaling that the deal is no longer rumor-stage.
The reason the word "team" is called out separately is that the agreement explicitly states: DuckDB, DuckLake, Quack, and the broader Duck Stack remain open source under the MIT license and continue to be governed by the independent nonprofit DuckDB Foundation, with AWS not taking over project governance. In its official announcement, DuckLabs emphasized two concrete moves to safeguard the open-source posture: the foundation will add a technical advisory board, and the extension stack will be opened so that third-party signed extensions can run inside DuckDB. AWS Distinguished Engineer Andy Warfield is quoted on both blogs, with his line "after about two years of working closely with Mark, Hannes and the whole DuckLabs team... one of the most technically deep, humble, and high-velocity teams that I've ever had a chance to work with" making it very clear that AWS wants to retain these people.
Why DuckDB
DuckDB was born at Centrum Wiskunde & Informatica (CWI) in the Netherlands, the same national research institute that also invented Python. While at CWI, the two founders realized that older engines like Spark focused on performance for very large data processing while ignoring the reality that 90% or more of real SQL queries actually run on datasets of 1TB or less. The AWS Big Data blog reiterates this judgment: DuckDB's vectorized execution, running in-process inside the host application, eliminates network hops and serialization costs, which is exactly the property low-latency data exploration needs.
More notably, DuckDB's design philosophy is a natural fit for how AI agents work with data. The AWS blog puts it bluntly: "agents behave a lot like people when interacting with data. They poke. They experiment. They run exploratory analysis on small data sets before figuring out what they really want to do." This pattern of small-data, fast, iterative exploration sits precisely in DuckDB's sweet spot for sub-second returns. AWS has already validated this path internally inside Amazon Quick — since launching in October 2025, the DuckDB-backed engine has processed more than 2.5 billion queries and reduced average latency by roughly 30%.
Customer and Ecosystem Endorsements
The AWS blog directly quotes David Feng, Executive Director of Scientific Computing at the Allen Institute, who explained that since 2025 the Allen Institute has used DuckDB for real-time quality control over neurophysiology and behavior data, compressing queries that previously took minutes down to seconds, and that this interactive tempo has changed how research proceeds. The DuckLabs announcement secures public endorsement from two critical ecosystem players: MotherDuck CEO Jordan Tigani called it "Amazon putting its weight behind DuckDB is going to add a ton of momentum," and Fivetran co-founder George Fraser emphasized that "DuckDB is the center of the vendor-neutral open data stack, and Amazon has the commitment to openness... to enable the DuckDB project to continue to thrive in this role."
The academic side lined up as well. Peter Boncz, head of the Database Architectures group at CWI and a DuckDB Foundation board member, stressed that the foundation continues to hold all open-source IP of DuckDB. Torsten Grust, professor and head of the Database Systems research group at the University of Tübingen, added an academic note: DuckDB's "hackability" made it a top platform for database research and teaching, and with the open-source posture preserved, those use cases are now on a more durable footing.
My Take
Bringing the DuckLabs team inside AWS is, at its core, the cloud vendor tying together "the most popular open-source OLAP engine for the analytics layer" and "the de facto standard for the data lake" at the organizational level. In a landscape where Snowflake and Databricks dominate the lakehouse discourse, AWS used a sub-thirty-person team to lock the experience chain of "sub-second local analytics on the data lake" inside its own ecosystem. For DuckDB users, the biggest risk is not in the agreement text but in execution cadence: governance committee makeup, technical roadmaps, and community distribution channels — once those start moving at cloud-vendor pace, it hurts more than any license change. Conversely, if the foundation's expanded authority, the opening of the signed-extension ecosystem, and AWS feeding back the Quick product's DuckDB optimizations into the open-source version all land within a year, DuckDB's engineering density will move up another notch.
Closing from a regular developer perspective: DuckDB already sees more than one million downloads per day. The acquisition does not change the license in the short term; the long-term watchpoints should be the membership of the foundation's technical advisory board and the pace at which the extension ecosystem opens up — those two tell us far more than any press release whether "open source" on DuckDB is written for investors or for users.
Sources: AWS Big Data Blog "AWS and DuckLabs: Building the future of analytics together"; DuckLabs official announcement "DuckLabs to Join AWS, Projects to Remain Open Source"; All Things Distributed "DuckDB and the Changing Physics of Analytics" by Andy Warfield; Amazon Newsroom "AWS to acquire DuckLabs."