AWS Acquires DuckLabs
DuckDB just got a cloud parent. DuckLabs — the bootstrapped, founder-owned company behind the embedded OLAP database — is joining Amazon Web Services. The deal closes early September. The team stays in Amsterdam. The MIT license stays. The DuckDB Foundation stays.
This is the biggest infrastructure acquisition of the year in the data world.
DuckDB has been eating the world quietly. A million downloads a day. Powering dbt, MotherDuck, GlareDB, and half the data science tooling you touch. It's the SQLite of analytics — embeddable, zero-config, columnar, and fast enough that people keep accidentally building production systems on it.
AWS gets more than a database. They get a file format play. DuckDB's .duckdb files and the emerging DuckLake / Quack stack give AWS a native columnar format that competes with Parquet on speed and blows it away on ease of use. Expect first-class AWS integration — Athena reading DuckDB files natively, Redshift importing from them, Glue jobs outputting them.
What this means:
- DuckDB gets resources. The founders were explicit: they hit the ceiling of a 30-person bootstrapped company. AWS removes that ceiling.
- The open-source promise holds. MIT license, foundation stewardship — same as Java under Oracle, React under Meta. It's credible as long as the foundation exists and a fork is trivial.
- Every cloud OLAP vendor just recalibrated. Snowflake, Databricks, ClickHouse, SingleStore — DuckDB under AWS sponsorship accelerates the columnar-embedded trend they've all been chasing.
The risk is real but narrow: MotherDuck (DuckDB's cloud-hosted companion) exists in a gray zone now. AWS could build competitive hosted DuckDB or just absorb the use case into Athena. MotherDuck's differentiation needs to deepen fast.
For everyone else: the database you already use just got a backer that can actually fund it. That's unambiguously good for the ecosystem.