On August 26, 2026, Amazon signed a definitive agreement to acquire DuckLabs, the company behind the open-source analytical database DuckDB. The deal is subject to customary closing conditions, and DuckLabs expects it to close in early September. What AWS is acquiring is not the DuckDB project or its intellectual property, but the Amsterdam-based development company of more than 30 people. The code remains legally independent, while the people who actually drive the roadmap will join AWS. Missing this two-layer structure risks misreading what the acquisition actually means.
Why would AWS buy a 30-person development company?
DuckLabs took no venture capital funding; it has been owned by its founders and development team. Its business model was to take on contract feature development and support work for companies, using that revenue to grow DuckDB. Co-founders Hannes Mühleisen and Mark Raasveldt had grown concerned that as adoption expanded, their small company was becoming a bottleneck for support, and that building out a large sales and operations organization would eat into the time available for technical development.
AWS and DuckLabs already had a product-level relationship. The two companies had collaborated for over a year, developing features that connect DuckDB to Amazon S3 Tables and Amazon SageMaker Lakehouse. DuckDB runs analytical processing inside an application without spinning up a separate database server. For AWS, which wants to bring computation closer to data stored in S3, the value of DuckLabs lies less in the DuckDB brand and more in its development capacity for connecting storage to an analytics engine.
DuckDB has traditionally been embedded within a host application's processing, expanding use cases where users query local files directly with SQL. This approach reduces the need to move all data into a large database before analysis. DuckLabs says it now wants to embed DuckDB inside products where users aren't even aware a database is involved. AWS's customer base and infrastructure offer a path to extend a developer-facing engine into a component of broader services.
After the deal closes, Mühleisen and Raasveldt are expected to continue leading the team and setting DuckDB's technical direction. Both companies have signaled they intend to use DuckDB, the lakehouse-oriented DuckLake, and Quack, a tool for remote connections, in new data services. However, neither has disclosed specific AWS products, timelines, or pricing.
Board composition matters more than the MIT license
AWS has explicitly stated that it is "not acquiring the DuckDB open-source project." Core intellectual property and trademarks for DuckDB, DuckLake, and Quack remain with the nonprofit DuckDB Foundation, and each project will continue to be released under the permissive MIT license. This is not a deal in which AWS closes off existing code or bars other companies from using or forking it.
What the MIT license protects is the freedom to use, modify, and redistribute published code. It does not determine which features get prioritized going forward or who continues to maintain them. If a company is dissatisfied with AWS's direction, it can fork the project, but keeping pace with the core development team requires comparable staffing and funding. For companies relying on DuckDB, the Foundation's decision-making process and the pathways available to outside contributors matter more for long-term options than the license text itself.
Even so, a license alone doesn't guarantee neutrality in the roadmap. According to the Foundation's official page, the current board has three members: chair Mühleisen, board member Raasveldt, and CWI researcher Peter Boncz. Since the co-founders joining AWS after the acquisition hold two of the three board seats, there remains personnel overlap even though the legal IP holder and the day-to-day development organization are formally separate.
Under the Foundation's bylaws, drafted in 2021, the board itself appoints and removes board members, and each member holds one vote. Ordinary decisions require a vote representing a majority of sitting board members and an absolute majority of votes cast. A board member whose personal interests conflict with the Foundation's interests is excluded from deliberation and decision-making on that matter. However, if this makes a decision impossible, the board can still decide after documenting the reasons in writing. The design that separates the company from the foundation includes safeguards, but how conflicts of interest will actually be handled post-acquisition remains a matter of practice.
v2.0 expands into server mode and custom extensions
Nine days before the acquisition was announced, DuckDB published an overview of v2.0, planned for fall 2026. Building on its traditional strength of in-application execution, it will stabilize Quack and introduce a server mode that allows connections to a remote DuckDB instance. It will also add asynchronous I/O, making it easier to read and write in parallel to network storage such as S3. The range of scenarios where combining DuckDB with AWS makes sense is already expanding from local analytics toward shared data in the cloud.
Another change concerns how extensions are distributed. In the current version, official and community extensions are centrally built and signed by DuckDB. In v2.0, organizations will be able to register their own public keys and distribute self-signed extensions from their own repositories. If cloud providers other than AWS and independent vendors can deliver connectivity features through the same mechanism, technical neutrality would be strengthened.
Supporting this distributed model is a stable C-language binary interface introduced in v2.0. Currently, extensions often need to be rebuilt to keep up with DuckDB updates, which is a significant burden. Under the new mechanism, extensions become less sensitive to version-to-version differences in DuckDB, and each organization can manage its own repository and signing keys. For independent cloud providers looking to continue offering features, this is a more direct lever than participating in an advisory board.
When a trusted repository is registered, DuckDB pins the distributor's public key and displays a SHA-256 fingerprint for verification. The plan includes support for key rotation with multiple keys, as well as functionality to audit or remove registered entries. Because companies can choose their own extension distribution sources, they would be able to manage other vendors' features on the same foundation as AWS's service integrations.
That said, this trusted extension repository system was still under development at the time of the announcement. Details of v2.0 may also change before the official release. This should be evaluated as a roadmap item that was already in progress before the acquisition, not as an accomplishment produced by the deal.
Does the Technical Advisory Board have voting power?
DuckLabs plans to establish a Technical Advisory Board under the Foundation in fall 2026. According to the official explanation, it will serve as a forum where key users and contributors can offer input on the roadmap for DuckDB, DuckLake, and Quack. The companies say they plan to increase investment in open-source technology and community after the deal closes, but they have not specified how the advisory board's input will factor into the board's actual decisions.
The composition of the advisory board, how its members will be selected, and what authority it holds relative to the Foundation's board remain undisclosed. In comments to The Register, Mühleisen said the precise governance structure and voting rights had not yet been finalized. The same report noted that the acquisition price has also not been disclosed. In other words, the institutional design needed to make good on the promise of continued open-source governance is still incomplete.
Under the current bylaws, both the authority to set the roadmap and the power to appoint or remove board members rest with the board. Even if the advisory board can offer input, without an obligation for the board to respond or a formal role in voting, it's not guaranteed that users outside AWS will be able to influence direction. Key things to watch will be how advisory board members are selected, how much of their proceedings is made public, and how the board responds to their recommendations.
MotherDuck is not part of this acquisition. It hasn't been disclosed how the existing partnership might change, and DuckLabs says it will share more details in the future. Even if development speeds up under AWS, the real test will be whether the Foundation can handle requests from parties outside AWS through the same process as everyone else. If the advisory board is given a genuinely effective voice and third-party-signed extensions work as planned in v2.0, DuckDB could continue to grow as a cross-vendor analytics foundation even after being absorbed into a corporate acquisition.