AWS: DuckDB will provide ‘connective tissue’ across the data estate
AWS has acquired DuckLabs, the company behind the open-source in-process analytics database DuckDB, in a move the cloud giant says reflects its broader thinking on the future of application building and data analytics. Although AWS already runs its own data warehouse in Redshift and does not gain DuckDB's intellectual property, since the database remains open source, executives argue the deal is less about owning the technology and more about positioning DuckDB as a lightweight "connective tissue" layer that links diverse data tools, engines and platforms, including rivals such as Google BigQuery and Microsoft Fabric.
DuckDB runs embedded within a host application rather than requiring separate server software, letting developers process smaller datasets locally before "graduating" larger or centralised queries to external engines like Redshift or RDS via SQL commands. DuckLabs was founded by DuckDB creators Hannes Mühleisen and Mark Raasveldt, both researchers at Amsterdam's Centrum Wiskunde & Informatica; the software stays under the MIT licence and the independent, non-profit DuckDB Foundation will continue setting strategic direction, though its governance is expected to broaden. Andy Pavlo of ClickHouse Labs welcomed the deal, suggesting AWS funding would help cover rising development costs, including AI-agent-driven CI/CD infrastructure, without altering the project's long-term direction; AWS is not alone in backing DuckDB, with Jordan Tigani's MotherDuck also building a commercial cloud service around it.
- AWS acquired DuckLabs, the firm behind open-source database DuckDB
- DuckDB stays open source; AWS sees it as cross-platform "connective tissue"
- Founders' non-profit DuckDB Foundation retains strategic control, with broader governance
New here? Start with this
DuckDB is an open-source database designed to run inside another programme, rather than as a separate server. It lets developers analyse data where it is being used, and send larger or shared queries to services such as Amazon Redshift or Google BigQuery.
The project was created by researchers Hannes Mühleisen and Mark Raasveldt, and is maintained under an MIT licence. Its independent, non-profit foundation guides the project, while companies including MotherDuck offer commercial services based on DuckDB.
The deal matters because AWS is backing a tool that can connect different data systems, including products from competing cloud providers. That reflects a broader role for databases: helping applications work across a mix of local software and centralised data services.
Both sides, in good faith
The strongest fair case each way — we don't pick a winner.
The case for
AWS’s backing could give DuckDB’s developers more resources to meet rising engineering costs while keeping the database open source and under the Foundation’s strategic direction. Positioning DuckDB as a portable layer across tools and cloud platforms could also make it easier for developers to analyse data locally and move larger workloads to the engine that best fits their needs.
The case against
AWS’s influence could still shape DuckDB’s priorities or governance over time, even without ownership of its intellectual property, potentially weakening confidence in its independence. As a major cloud provider with competing services, AWS may also benefit from making DuckDB a bridge into its ecosystem, so users and rival platforms could become more reliant on a tool whose direction is partly influenced by AWS.