DuckDB

What it is for

DuckDB is a local UI / notebook desk: you run SQL in the in-process engine, and the license is $0 (MIT). Use it when the job is a columnar query you open on one machine, not when you need a $20 chat seat.

What makes it unique: the cover is DuckDB’s official local UI (DuckDB UI basics, memory.traininds, Query results 380,959 rows, column explorer) from the UI blog still — not a pricing card. The panes themselves are ops of the local UI. DuckDB bills $0. Hosted MotherDuck is a separate listing.

Key features

• Local UI / notebooks — SQL notebooks against an attached database (cover still; UI blog). One desk. Cover memory.traininds and 380,959 rows sit here.
• Column explorer — the right-hand stats / histogram pane on the same still (UI blog). Diagnostics, not the notebook. Cover service_id / date bars sit here.
• In-process engine — embed DuckDB in Python, CLI, or another host (docs). A library, not the UI. MIT $0 sits here.
• File / HTTP scans — FROM 'https://…parquet' without a server (docs). A scan, not a notebook cell.
• MotherDuck sign-in — the cover’s “Sign in to MotherDuck” chip (UI blog). A hosted attach, not local DuckDB. Dollars for that desk live on MotherDuck.

The Sign-in chip on the cover is the same local UI chrome (not a sixth desk). MIT $0 is the meter. MotherDuck cloud $ is the extra meter, not a desk we fold into the local UI.

Who it's for

Best fit: analysts and app teams who will stay on local DuckDB at $0 (MIT) while they open a first UI notebook, then attach MotherDuck only when they need a hosted share.

Pricing

Verified 2026-10-23 (Asia/Shanghai) from duckdb.org (MIT / “Free & open-source”). There is no Cloud $ for the engine.

• DuckDB — $0. MIT. Local / embeddable. Governed by the DuckDB Foundation.
• Hosted — MotherDuck is a separate product and listing. Confirm that page for Cloud $.

Confirm the license file in the repo you ship; taxes do not apply to $0 MIT.

Limitations / costs

• Local UI is not a warehouse SLA. Persistence, sharing, and SSO live on a host (or MotherDuck).
• A local UI desk, not MotherDuck’s cloud notebook. For the hosted $ see MotherDuck.

Alternatives

• MotherDuck — hosted DuckDB when you want a Cloud $ share, not the local 380,959-row UI.
• Turso — libSQL / SQLite edge when you want Turso’s public $, not DuckDB’s columnar UI.
• Supabase — Postgres + studio when you want Supabase’s Free / Pro desk, not an in-process engine.

Official tutorial

Official DuckDB channel video: DuckDB – Overview and latest developments (DuckCon #5, Seattle, 2024) (oEmbed author: DuckDB). First-party conference overview; the local UI still is the cover. DuckCon on the video is a second desk, not generate-on-UI.

Written path: duckdb.org plus the UI blog still.

Website

https://duckdb.org

Repository

https://github.com/duckdb/duckdb

Source

Catalog row curated for AI Tools Nav. Cover is DuckDB’s official local UI still (notebook + 380,959-row result + column explorer). Dollars: MIT $0 on duckdb.org. Tutorial oEmbed author: DuckDB.

Last verified

2026-10-23 (Asia/Shanghai) editorial check.