DuckLabs joins AWS, keeps DuckDB open source

According to DuckDB's official site, DuckDB is an analytical database that runs directly inside a laptop or an application, with no separate server needed. It can query large datasets fast, which has earned it the nickname "SQLite for analytics" among data scientists and engineers. DuckLabs says the software sees more than a million downloads a day, and the company has also been developing two related projects, DuckLake and Quack.

Five years of independence, then the limits of scale

DuckLabs was founded roughly 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 started drawing attention, both commercial partnership offers and venture capital came calling — but the founders chose to bootstrap rather than hand 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 pace. The company worried that its own small size could become the bottleneck holding back the project's growth, and it judged that forcing rapid expansion of sales and support teams would pull focus 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; reaching a much broader base of users, 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. Over that stretch, the two organizations tested how they'd work together and what each could bring to the table, and that track record is what gave DuckLabs confidence in this decision. In Amazon's official announcement, Andy Warfield, AWS VP and Distinguished Engineer, said, "DuckDB is already widely used and much loved among S3 customers as an open-source project."

Open source stays open, governance stays put

The point DuckLabs hammered home the most was licensing and governance. The open-source components of what it calls the "duck stack" — DuckDB, DuckLake, and Quack — will keep shipping under the MIT license, and the intellectual property will continue to be managed by the nonprofit DuckDB Foundation. That foundation was set up alongside DuckLabs when it spun out of CWI, and it has held all IP 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 rather than slow it down.

Going forward, the foundation plans to stand 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 intends 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 governance	DuckDB Foundation	DuckDB Foundation continues, plus new technical advisory committee
Extension policy	Managed in-house	Third-party signed extensions to be opened up

Industry reaction has leaned 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 teaching, and welcomed the news that it will stay open source under AWS. George Fraser, co-founder and CEO of data integration company Fivetran, said Amazon is the best home to keep growing DuckDB, which he called central to a vendor-neutral, open data stack.

Editor's take

The thing that stands out most about this deal is that DuckLabs' reason for turning down venture capital and its reason for joining AWS now come from the same root. Five years ago, bootstrapping was the way to keep growth-hungry capital from overtaking the technology. Today, the calculation is that the company can't build the infrastructure, sales, and support operations that technology now demands on its own — so it's turning to the biggest cloud provider instead. The directions are opposite, but the motive is identical: staying technology-first meant independence back then, and it means dependence now.

Anyone who's watched open-source infrastructure companies get acquired over the years will recognize this pattern. A project builds enough value that it eventually gets absorbed by one of the major cloud providers, 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 much AWS representation will sit on the foundation's board, or whether the technical advisory committee's decisions will actually carry the power to shift the roadmap.

For teams in Korea running DuckDB inside data pipelines or internal analytics tools, nothing changes right away — 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 that marketed itself on vendor neutrality ends up under one specific cloud provider. Expect AWS to roll out announcements in the coming weeks tying its own services more tightly to DuckDB — and that will be the first signal of whether this was simply an acquisition or the start of a bigger platform strategy.