AWS, DuckDB Analitik Veritabanının Arkasındaki Şirket DuckLabs’ı Satın Aldı

Amazon (AMZN ) 26 Ağustos 2026 tarihinde DuckLabs’ı satın alacağına dair kesin bir anlaşma imzaladığını duyurdu; Amsterdam merkezli şirket, ekibi DuckDB’yi inşa edip sürdürmektedir; bu açık kaynaklı analitik veritabanı artık günde bir milyondan fazla indirme kaydetmektedir. Finansal koşullar açıklanmadı.

The transaction is expected to close in early September, subject to customary closing conditions. When it closes, the DuckLabs team of more than 30 engineers will join Amazon Web Services and remain based in Amsterdam. Hannes Mühleisen and Mark Raasveldt, who created DuckDB and co-founded the company, will continue to lead both the team and the open-source project’s technical direction, according to Amazon’s announcement.

Amazon’un Satın Aldığı Şey — ve Satın Almadığı Şey

The deal’s structure matters more than its undisclosed price. Amazon is acquiring DuckLabs the company (its engineering team and its commercial support business) but explicitly not the DuckDB open-source project. The core intellectual property and trademarks of DuckDB, DuckLake, and Quack are held by the DuckDB Foundation, an independent Dutch non-profit, and will remain there. All three projects continue to be distributed under the permissive MIT license, Amazon said.

That split is the mechanism by which AWS gains the people who set the project’s technical direction without taking ownership of the code itself: a structure designed to keep DuckDB neutral ground for the ecosystem of vendors built on top of it. DuckLabs’ own post, signed by Raasveldt and Mühleisen, states the company was bootstrapped and fully owned by its founders and development team, having turned down venture capital when it was founded five years ago. Its revenue came from commercial support contracts and engineering services for organizations running DuckDB, a model the founders describe as approaching its limits as adoption scaled.

“We believe the DuckDB revolution can grow by another couple of orders of magnitude. To give it that opportunity, we realized we needed a different setup,” the founders wrote. They pointed to the cost of scaling a sales, support, and operations organization as the specific pressure: “We also worried that scaling DuckLabs into a much larger sales, support, and operations organization would pull our attention away from the technical work and open-source community that made DuckDB successful in the first place.”

Neden Anlaşma Analitik Pazarına Önemli

DuckDB occupies a distinct position in the data-infrastructure stack. It is an in-process analytical SQL engine. It runs inside the application or notebook that calls it, rather than as a separate database server, and it reads open formats including Parquet and Apache Iceberg directly from object storage. The DuckDB project describes the broader “Duck Stack” as three components: DuckDB itself, DuckLake (an open lakehouse format that keeps catalog metadata in a SQL database), and Quack (a client-server protocol released in beta in Mayıs 2026).

For AWS, the acquisition brings in-house the team behind an engine that already runs heavily against Amazon S3 data and sits underneath a growing layer of analytics products. Andy Warfield, an Amazon vice president and distinguished engineer, framed the rationale around that existing usage in the company’s announcement.

“DuckDB is an incredible open source project with an amazing community; it is broadly used and very much loved by S3 customers today,” Warfield said, quoted in the DuckLabs post. “After about two years of working closely with Mark, Hannes and the whole team at DuckLabs I’m excited at the opportunity to help the project have an even broader impact.”

The competitive context is the cloud data-platform market where AWS’s analytics services (Redshift, Athena, and its lakehouse tooling) compete with Snowflake, Databricks, and Google’s BigQuery. DuckDB and DuckLake are open-format, vendor-neutral pieces of that stack; DuckLake in particular is an alternative catalog approach to the lakehouse architectures those rivals sell. Bringing the core team in-house gives AWS direct influence over the development velocity and direction of formats its customers increasingly use to organize data in S3.

The announced plans, per the DuckLabs post, are to use DuckDB, DuckLake, and Quack “to help power a new generation of data services.” Specific AWS product integrations were not announced.

Açık Kaynak Güvence Çerçeveleri

The continuity commitments are unusually specific, because the deal’s value to AWS depends on the ecosystem not forking or defecting. The DuckDB Foundation, which holds the IP, will continue its stewardship, and a new technical advisory board will be added so community members can input on technical direction, according to DuckLabs. The team also plans to open the extension stack so that extensions signed by outside developers and organizations can run in DuckDB.

Peter Boncz, the CWI Amsterdam database group lead and a DuckDB Foundation board member, addressed the governance question directly in the DuckLabs announcement: “When DuckLabs spun out of CWI, we created this foundation, which holds all IP of open-source DuckDB, and will continue to do so. I am delighted that AWS is committed to keep advancing open-source DuckDB.”

The commercial ecosystem around DuckDB also stays in place. MotherDuck, the separate company that sells a managed cloud service built on DuckDB, contracts with DuckLabs for engineering work and supports the Foundation, a relationship described on the DuckDB project history page. Jordan Tigani, MotherDuck’s CEO, said in the DuckLabs post that “Amazon putting its weight behind DuckDB is going to add a ton of momentum and strengthen the ecosystem.”

Sonra Ne Olacak

The near-term observables are the closing, expected in early Eylül 2026, and the detail Amazon has said it will share afterward on how DuckLabs and AWS will be brought together for customers. The DuckDB Foundation’s planned technical advisory board and the opening of the signed‑extension stack are the two stated structural changes to watch in the project itself.

For DuckDB users, both companies said nothing changes at close: the code stays MIT-licensed, the Foundation keeps the IP, and the team stays in Amsterdam working on the same three projects. The monetization question — how AWS turns a free, embedded engine into revenue inside its analytics portfolio — is the piece Amazon has not yet detailed, and it is what will determine whether this reads as an engineering acqui‑hire or the start of a more direct AWS push into the open‑format lakehouse layer.