July 2026
The first version of Thunderduck was built in the second half of July. Rather than a change log, this page describes what it could do by the end of the month.
The first version
New
- Sign-in — email and password or Google sign-in, with email verification. Teammates on the same company email domain join the same company.
- Studio — a SQL editor with a catalog tree, query results in the browser, and a list of recent runs.
- PostgreSQL catalogs — register a PostgreSQL database, query it as
catalog.schema.table, and write to it. Setup - Tables — a page listing every table in your catalogs with its columns, row count, size, indexes and partitions, also used by the Studio catalog tree.
- Query History — every run with its SQL, status, timings, CPU and memory, and who or what ran it (a person, an API token or a scheduled job), with sorting and filters.
- Saved queries — save a query from Studio by name, update it, and open it again from the Saved Queries page.
- Scheduled jobs — run a query on a cron schedule in your time zone, with the last status and a history of runs. A job never overlaps with its own previous run. Scheduled jobs
- Save and download results — keep a query's result as a Parquet file and download it through a short-lived link, from Studio or Query History.
- API tokens and the JDBC driver — create tokens in Settings and connect any JDBC tool. JDBC driver
- dbt projects — connect a dbt project in a Git repository and run it against your catalogs. dbt
- Monitoring — usage per user across your company.