The deal marks another step in the cloud industry's quiet accumulation of open-source data tooling. DuckDB, which DuckLabs built over the past five years, runs at more than three million downloads a day, a scale that makes it one of the most-used analytical databases currently in active development.
DuckLabs was set up specifically to give the DuckDB development team a durable operating home without the pressure to convert open-source users into paying support customers. That model, bootstrapped and fully founder-owned, funded the growth to more than 30 employees in Amsterdam. Joining AWS ends the bootstrap arrangement but, by DuckLabs' account, removes a different kind of pressure: the need to reshape the business to reach a larger audience.
What AWS brings to the table is distribution. DuckDB is already popular among S3 users and has existing integrations with Amazon SageMaker Lakehouse and S3 Tables, built during two years of direct collaboration between the two companies. The acquisition deepens that relationship rather than starting from scratch.
The DuckDB Foundation continues to hold stewardship of the open-source projects. DuckLabs plans to expand the Foundation's role, including establishing an advisory board through which commercial users can influence the project roadmap. The company also intends to make the extension ecosystem more open, allowing extensions signed by developers outside the DuckLabs team.
Hannes Mühleisen, co-founder and chief executive at DuckLabs, said: "Over the past five years, DuckDB has grown from an ambitious open-source project into technology used by developers and organisations around the world. Joining AWS gives our team the opportunity to build for a much larger audience while continuing to invest in the open-source ecosystem around and including DuckDB."
Andy Warfield, vice president and distinguished engineer at AWS, said: "DuckDB is an incredible open source project with an amazing community; it is broadly used and very much loved by S3 customers today. After about two years of working closely with Mark, Hannes and the team at DuckLabs, I’m excited at the opportunity to help the project have an even broader impact."
The Amsterdam team stays in place. DuckDB, DuckLake, Quack, and the wider ecosystem projects carry forward under the same licences they have always used.
To stay across the latest in cloud, AI and enterprise tech analysis from Compare the Cloud, subscribe to our weekly newsletter at https://www.comparethecloud.net/newsletter