Open quickly.
Just works.
Keep it safe.

A SQL client that keeps everything on your disk. Fourteen databases, one window, read only until you say otherwise.

Download for Windows See the drivers
GPQL no session

New session

Database
PostgreSQL

PostgreSQL 18.4 answered in 6 ms

Read only

the server refuses every write

Every database speaks for itself.

Every backend goes through the driver its own people maintain. No wrapper protocol, no hand-rolled HTTP.

  • PostgreSQL rustls
  • MySQL native wire
  • SQLite file
  • DuckDB bundled
  • Supabase postgres wire
  • GreptimeDB port 4003
  • ClickHouse native client
  • Turso libsql
  • InfluxDB 3 arrow flight
  • InfluxDB 2 flux
  • Snowflake account auth
  • Neo4j bolt
  • FalkorDB cypher
  • Cloudflare D1 http api

Three screens. No fourth one.

Data

Virtualized rows and columns, a minimap when the result runs wide, and cell edits the moment you leave read only.

GPQL roomy
Data Query Schema

message

6 columns

Query

Tree-sitter highlighting per dialect, completion from a real language server, a check before anything runs, and an ask bar that writes the SQL with your own key.

GPQL roomy
Data Query Schema
busiest channels this week
select channel.topic, count(*) as messages
from message
join channel on channel.id = message.channel_id
where message.sent_at > now() - interval '7 days'
group by channel.topic
order by messages desc

3 rows in 4 ms, read only

Schema

Tables laid out by what they point at, walkable with the arrow keys, and grouped by hand or, if you turn it on, by a model.

GPQL roomy
Data Query Schema
Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

Read only is the default

The server is asked to refuse writes until you flip one toggle, and it flips back on its own.

Keys stay on the machine

Windows seals saved logins with DPAPI. Elsewhere the file is plaintext, and the readme says so.

Diagrams without a server

Draw an ERD offline. Publish it only when someone else needs the room.

An account is only for carrying settings across machines.

GPQL works forever without one. Sign in when you want the same setup on a second machine.

  • Settings, theme and density
  • Connections you have opened before
  • Queries you kept
  • ERD rooms, co-design with your team
  • Passwords. Those stay sealed on the machine that made them.

Sync

Free, with an account

Same settings, connections and saved queries on every machine. No plan, no card, no seat count.

Sign in with GitHub

Sign in once in the browser. The app picks it up on its own.