person
Co-creator of DuckDB and CTO of DuckLabs; co-presented the v2.0 plan.
No evidence-backed relationships are recorded.
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