Duck-UI brings SQL directly to your browser, running DuckDB entirely in WebAssembly with no backend required [1]. Data stays on your machine, and you can load CSV, JSON, or Parquet files from disk or via URL [1].
What Duck-UI does: It's a SQL editor with autocomplete and syntax highlighting. You can import CSV, JSON, Parquet, and Arrow files from disk or remote URLs, and query results show instantly. OPFS-backed persistence means data survives browser refresh [1].
Data locality and privacy: Everything runs in the browser, so data stays on your device, supporting privacy-conscious workflows [1].
Offline usage and deployment options: Duck-UI can run without a server, and you can deploy locally via a one-liner Docker deployment or Node 20+ dev server [1].
Trade-offs vs server-hosted UIs: - Execution happens in-browser via DuckDB WASM, avoiding server round-trips [1]. - Data locality and privacy: data remains on your machine [1]. - Offline capability thanks to OPFS persistence [1].
Bottom line: for quick exploration and privacy-first prototyping, client-side analytics UIs like Duck-UI are shaping a new take on analytics [1].
References
Show HN: Duck-UI – Browser-Based SQL IDE for DuckDB
DuckDB WASM browser UI; no server; local CSV/Parquet imports; features, feedback, and comparisons with other UIs.
View source