The DuckDB team shipped 2.0.0 LTS under the name “Cinnamon Teal” — Spatula cyanoptera. This is not makeup on 1.x: about 20,000 commits landed since 1.5. People remember 1.0 as a bet on compatibility; the team itself calls 2.0 the big feature release. Support runs at least to October 2027. Line 1.4 is kept until 17 November 2026; 1.5 was extended to March 2027.
A server that is still a duck
DuckDB has lived in-process since day one. 1.5.3 brought the Quack protocol: any process can serve its databases. 2.0 polished that protocol and added CONNECT — attach a remote database and switch the session in one statement. By default the server listens on localhost; the team does not recommend exposing it without a TLS proxy. The same CONNECT works with PostgreSQL and MySQL; queries are promised to push to the far side instead of dragging whole tables over.
The CLI gained -serve and -connect flags. Also on the 2.0 shelf: asynchronous I/O, a VARIANT type, triggers, an extensible SQL parser and an “agent mode”. That is a shelf, not one button.
How to look at it
It matters if you already keep a duck as a local warehouse and want to hand it to a colleague over the network without a separate Postgres. It does not matter as a cluster replacement: this is still an analytical engine that learned to listen on a port. Read the 2.0 breaking changes before moving, not just the bird’s code name. Watch whether Quack holds simple SELECTs from a laptop, not the promise of “duck as a server for years”.
