On Aug. 26, Amazon’s cloud unit announced it has acquired DuckLabs, the Amsterdam-based company behind DuckDB, the open-source analytics database that has become one of the most popular tools in data engineering. Financial terms were not disclosed. The deal folds a developer darling into the world’s largest cloud business, and it signals where Amazon sees the next battleground in data infrastructure.
DuckDB’s rise has been unusually fast for a database. Released in 2019 as a research project, it grew into an embedded engine that runs analytical queries directly inside a process, with no server to manage. Data engineers adopted it for tasks that once required standing up clusters: inspecting parquet files, prototyping queries, and powering the back end of notebook analyses. By 2026, it had millions of downloads a month and a vocal community that treated the tool as a standard part of the modern data stack.
The acquisition ends a period of speculation about DuckDB’s future. The project’s core developers had resisted offers from other companies for years, and DuckLabs operated on a mix of consulting revenue and venture funding. AWS approached with a pitch centered on preserving the project’s open-source character, according to a person familiar with the talks. DuckDB’s licensing remains unchanged, and the company said its development team will stay in Amsterdam.
For AWS, the deal is about embedding analytical capability into places where its own engines do not reach. DuckDB’s model of running inside applications makes it a natural fit for the edge of the AWS ecosystem: Athena, the serverless query service, and the S3 object store that holds much of the world’s data. AWS executives said customers will be able to run DuckDB workloads against S3 with tighter integration, and that the engine will power new features inside Athena.
The move follows a pattern of cloud giants absorbing open-source data software. Google and Microsoft have built or bought their own analytics engines, and the database market has consolidated around a handful of vendors who control both the code and the platform. DuckDB’s acquisition removes an independent option that many developers had come to rely on, and it raises the same question every open-source acquisition raises: will the code stay open?
The project’s founders said yes. In a post on the DuckDB blog, they framed the deal as a way to secure long-term funding for a project that had outgrown its garage-style governance. “The cloud is where analytical workloads increasingly live, and we wanted to be part of that infrastructure rather than watching from the outside,” the post read. The company said DuckDB’s community edition will remain free and that contributions from outside developers will continue to be accepted.
Analysts read the deal as recognition that embedded analytics is the growth layer of the data market. The days of every query running in a dedicated warehouse are giving way to a world where applications analyze data locally, on laptops, on edge devices, and inside pipelines. DuckDB’s performance in that niche, analysts said, made it the most credible independent challenger to the query engines offered by the big clouds.
AWS’s rivals are not standing still. Microsoft has pushed its Fabric platform, and Google has invested in BigQuery’s analytical muscle. But neither has an embedded engine with DuckDB’s mind share. The acquisition gives AWS a developer-facing asset that could pull a generation of data engineers deeper into its orbit, the same way its early open-source bets on Kubernetes and Spark built loyalty a decade ago.
The near-term risk is cultural. DuckDB’s community has been prickly about commercial influence, and the project’s mailing lists have already seen messages questioning the acquisition. AWS has a mixed record with open-source stewardship: it has supported projects like Apache Airflow while also facing criticism over how it has used open-source code from others. The company moved quickly to address the concern, announcing a governance structure that keeps the core team’s veto power over the codebase.
For customers, the practical effects will be gradual. DuckDB users who never touch AWS will see little change; those who do will gain features such as direct S3 access, federated queries across data lakes, and integration with AWS’s catalog and security systems. AWS said migration tools will be published for teams running DuckDB in other clouds, a concession to the reality that the database’s users are scattered across every platform.
The financial logic is straightforward even without disclosed terms. DuckLabs was a small company with modest revenue, and the value of the deal lies in what DuckDB unlocks inside AWS: a reason for developers to choose Amazon’s data services over competitors. Cloud businesses are won on habits, and DuckDB has become a habit for a generation of engineers who will now find it already wired into the platform they use at work.
The acquisition closes a chapter for the Amsterdam team that built a database in a university research group and watched it outgrow every expectation. The next chapter belongs to Amazon, which has bet that the most beloved tool in open-source data can become a wedge for its own empire.
