A fast, open-source PostgreSQL GUI client

Why pgNimbus

The gap in the Postgres client market: truly fast + open source + modern UI. pgAdmin and DBeaver are heavy; TablePlus is closed and paid; HeidiSQL is dated and MySQL-first.

The road to 1.0

Three months from the first commit to 1.0, with the benchmark run on every release along the way.

1. July 4First commitA weekend experiment, typed on a phone on holiday. By Sunday evening it connected, drew the schema and streamed rows.
2. July25 releases in the first monthA Microsoft Store listing, macOS and Linux builds, and signed build provenance on every release.
3. AugustRoles and permissionsA window that asks the server whether a role can do something, and explains where the answer comes from.
4. SeptemberA tool for every daySafe mode that notices someone else's edit, completion that reads SQL the way the server does, and a macOS pass.
5. 1.0Reviewed before the tag18 findings, from a query that could run twice to unchecked SSH host keys. All of them are fixed in 1.0.

What's in 1.0 →

See it in action

Cold start to first frame, completion that predicts the next move, and the tools around the query.

Everything you need, nothing you don't

A minimalist shell over a serious engine. Secondary actions live in the palette, not on a toolbar.

• Streaming, cancellable results. The first screenful renders before the full result set arrives, in a virtualized grid.
• Safe mode. Stage grid edits, inserts and deletes, review the exact SQL, and commit them as one transaction. If someone else changed a row in the meantime, you see before, now and yours side by side.
• SQL completion that reads SQL like the server. Only what can legally come next at the caret: tables, scoped columns, aliases, CTE columns, functions, DDL. A join and its ON condition in one accept.
• Browse without writing SQL. Paged, sortable browsing pushed down to Postgres, filter chips per column, a row details card, and a hand-typed WHERE comes back as chips.
• Follow foreign keys from the grid. Jump to the referenced row, or list every row that references this one.
• Roles and permissions. Ask whether a role can do something and see why: a direct grant, a group, PUBLIC, ownership. Grants come out as a script you review, never applied behind your back.
• Server insight. Live activity with a who-blocks-whom lock tree, a database overview, a slow-query shortlist from pg_stat_statements, and a LISTEN/NOTIFY monitor.
• Read-only connections. Mark a profile read-only and the server itself refuses writes.
• Transaction control. Explicit Begin, Commit and Rollback on one held connection, with rollback on failure.
• Multi-tab editor. SQL formatting, find and replace, run history, saved queries, whole-script execution, and closed tabs come back with Ctrl+Shift+T.
• Cell inspector. Press Space on any cell to read a long text or jsonb value, pretty-printed or as a tree.
• Import and export. Type-inferred CSV and JSON imports through COPY. Export writes every row, not just the page on screen. Copy results as CSV, JSON, Markdown or INSERTs.
• Connection manager. Paste a URI, a JDBC URL, libpq keywords or a whole psql command line and the form fills itself. Per-connection accent colors, SSH tunnels with agent auth and checked host keys, TLS verification, and passwords only in the OS credential store.

Fast is measured, not asserted

Every tagged release runs the benchmark suite: startup to first frame, memory at first frame, connect and round-trip latency, time to first row batch, and full-stream throughput of a 100,000-row query.

View the benchmark history →

Download

Windows is the primary target; macOS and Linux builds ship as early betas.