Company
Dutch company founded by DuckDB's creators that commercializes the open-source analytics database through support and services; now owned by AWS.
A dev.to walkthrough found DuckDB's operator names in the EXPLAIN output of AWS's aurora_analytics extension, on a Parquet query that executed in 81 ms. That run hit a warm cache on one 500,000-row file, so it tells you which engine ran far more than how fast it will be on lake-scale data.
Reality
AWS has embedded DuckDB in Aurora PostgreSQL from versions 17.11 and 18.6, so one SQL query can join live rows with Iceberg and Parquet tables in S3. Reverse-ETL jobs that exist only for that join can be retired if the database instance has room for the lake scans.
Reality
The engine stays in-process and MIT-licensed, so a vendored copy keeps working after the deal closes. What changes is who decides which storage paths get engineering attention, and the post names six AWS services.
Reality
DuckLabs keeps its Amsterdam desks and the MIT license still holds. The change is who pays for the roadmap, and what that does to a database compiled into your product.
Reality
AWS says the DuckDB projects stay free and open under an independent foundation. The people who write them join AWS by early September, on terms nobody disclosed.
Reality
The MIT-licensed projects stay with the DuckDB Foundation, but the more than 30 people who write them would sit on AWS's payroll. No reporting line has been published.
Reality
The creators of the embedded analytics engine are adding the client-server layer their original design deliberately left out. Treat v2.0 as a provisioning decision, not an upgrade.
Reality