DuckLabs joins AWS, keeps DuckDB open source

DuckLabs joins AWS in early September

DuckLabs announced on August 26 that it plans to join Amazon Web Services (AWS) in early September 2026. The company built DuckDB, the open-source engine for data analytics, and for more than five years it reportedly ran without venture funding, with equity held by its founders and employees. A company like that joining the world's largest cloud provider raises an obvious question: why now?

What DuckDB actually is

According to DuckDB's official homepage, DuckDB is an analytical database that runs directly inside a laptop or application without spinning up a separate server. It can query large volumes of data quickly, which has earned it the nickname "SQLite for analytics" among data scientists and engineers. DuckLabs says the project sees more than a million downloads a day, and the team has also been developing two related projects, DuckLake and Quack.

Five years of independence, then a scale problem

DuckLabs was founded more than five years ago by a team that spun out of CWI Amsterdam (the Dutch national research institute for mathematics and computer science) to give the project a stable home. As DuckDB gained traction, both commercial partnership offers and venture capital interest followed, but the founders say they chose to bootstrap rather than give up equity to outside investors. That choice bought them the freedom to grow slowly and stay focused on the technology, and the team grew to more than 30 people in Amsterdam.

The problem was the pace of growth. The company said it worried that its own small size could become the bottleneck holding back the project's growth, and that forcing rapid expansion of sales and support functions would pull energy away from the technology and the open-source community. Its partnerships so far had mostly been with technical organizations that already had their own database expertise. But reaching a broader user base, the company concluded, would mean solving industry-specific problems and investing far more heavily in infrastructure than it could manage alone.

More than a year of working with Amazon

This wasn't a sudden decision. DuckLabs says it has been collaborating with AWS for more than a year, starting with a preview post on Amazon S3 Tables integration published last March. During that period, the two organizations tested how well they could work together and what each could bring to the table, and that experience gave DuckLabs confidence in the decision. In Amazon's official announcement, Andy Warfield, AWS Vice President and Distinguished Engineer, said, "DuckDB is a widely used and much-loved open-source project among S3 customers."

Open source stays open, governance stays the same

The point DuckLabs emphasized most is license and governance. The open-source components of the "duck stack" — DuckDB, DuckLake, and Quack — will continue to be released under the MIT license, and the intellectual property will keep being managed by the nonprofit DuckDB Foundation. That foundation was created alongside DuckLabs when it spun out of CWI, and it has held all the intellectual property for open-source DuckDB ever since. Peter Boncz, head of the Database Architectures group at CWI Amsterdam and a member of the foundation's board, said AWS's commitment to continuing to develop open-source DuckDB would actually accelerate innovation.

Going forward, the foundation plans to set up a new technical advisory committee so that key figures in the community can weigh in on the project's technical direction. DuckLabs also said it plans to open up its extension stack so that extensions signed by other developers and organizations can run on DuckDB.

Before and after, at a glance

Item	Before joining	After joining
Ownership	Bootstrapped, owned by founders and employees	Part of AWS
Team location	Amsterdam, 30+ people	Stays in Amsterdam
License	MIT open source	Stays MIT open source
IP management	DuckDB Foundation	DuckDB Foundation continues, new technical advisory committee
Extension policy	Managed in-house	Plans to open up to signed third-party extensions

Industry reaction leans supportive

Reaction from partners and researchers has been largely positive. Torsten Grust, a professor at the University of Tübingen, said DuckDB's openness and approachable design have made it a major platform for database research and education, and welcomed the news that it will remain open source under AWS. George Fraser, co-founder and CEO of data integration company Fivetran, said Amazon is the best possible home to keep growing DuckDB, calling it central to a vendor-neutral, open data stack.

Editor's view

The most striking thing about this move is that DuckLabs' reasons for turning down venture capital and its reasons for joining AWS now trace back to the same root. Five years ago, it bootstrapped to avoid capital that would push growth speed ahead of the technology. Now, it's joining a hyperscaler because it concluded it couldn't build the infrastructure, sales, and support functions the technology needs on its own. The direction is opposite, but the motive is identical: staying technology-first meant independence five years ago, and it means dependence now.

Anyone who's watched open-source infrastructure companies get acquired will recognize this pattern. A high-value open-source project eventually gets absorbed by a single major cloud provider, and each time, "the foundation holds the IP" gets deployed as the standard reassurance for the community. DuckLabs is using the same playbook, but this announcement alone doesn't tell us how many AWS people will sit on the foundation's board, or whether the technical advisory committee's decisions will actually carry the power to change the roadmap.

For teams here at home already plugging DuckDB into data pipelines or internal analytics tools, nothing changes immediately — the license is unchanged and so is the API. But once the extension stack opens up, a new practical question emerges: who's responsible for vetting the quality and security of third-party extensions? That will be the first real test of what happens when a project built on vendor neutrality lands inside a specific cloud provider. Expect AWS to announce deeper integrations tying its own services to DuckDB within the next few weeks — and that will be the first signal of whether this was simply an acquisition or the start of a broader platform strategy.