r/postgres • • Aug 07 '26

Self made Postgres clients OSS

Post image

Hi all, hopefully this does not break any rules, I see some posts here requesting for new Postgres clients I made one and ended up releasing a local lightweight webapp version of my app today. It’s not the best or replaces pgadmin but works well for me.

It’s this one https://github.com/FrancisTCE/gresui-web.

Do you have your own Postgres client tools? I would like to see where I can improve this, it’s useful for me as well see what you got if you want to share.

0 Upvotes

3 comments sorted by

2

u/arbyyyyh Aug 08 '26

So then why should I use this over pgadmin?

1

u/BassIs4StringDrum Aug 08 '26

Honestly gresui isn't trying to compete with pgAdmin as a full database administration tool. It's built for a much narrower use case: quick, lightweight database browsing when you don't want or need a heavy client and also has mcp capability so the dev flow is smother.

The idea is:
Start instantly, just gresui-web on cli and you're looking at your tables quick.
Minimal footprint compared to pgAdmin that is hundreds of megabytes with its own full application server. gresui is a lean Bun + React app well under 100MB
SPA in the browser with React frontend, no page reloads, pretty snappy for basic browsing and querying.
Encrypt on rest
Easy mcp to table configuration

Tbh sometimes that's genuinely all I want/need. pgAdmin's feature set is massive but when I'm just trying to check if a row got inserted correctly or leverage ai this feels better.

1

u/navicat-gu 14d ago

Nice work shipping it. A few things people here usually care about more than "yet another SQL editor" — useful as a checklist for gresui-web or anyone else building one:

  1. Connection hygiene: SSH tunnels, SSL modes (require/verify-full), and a way to colour or label prod vs local. Wrong-database mistakes are the #1 pain.

  2. Don't freeze on big results. Default LIMIT, cancelable queries, and streaming rows beat a pretty grid that OOMs at 500k rows.

  3. EXPLAIN that humans read — tree with the slowest node highlighted beats a raw text dump.

  4. Schema browse that's fast on large catalogs (pg_catalog can be huge); lazy-load columns/indexes.

  5. Export that doesn't surprise Excel (CSV BOM option; escape cells that look like formulas).

  6. Local-first / no telemetry if you're pitching "lightweight webapp" — people will ask where credentials live (browser localStorage vs OS keychain vs server).

pgAdmin is feature-rich and often disliked for weight/UI; DBeaver covers "one tool many engines"; psql + a pager still wins for a lot of veterans. A small web UI wins when it's fast to open, safe on prod, and pleasant for browsing — not when it tries to become an enterprise suite on day one.

Disclosure: I'm RC, Director of Digital Strategy @ Navicat. We make a commercial multi-engine client (Premium Lite is free for SSH/SSL connections, colour-coded connections, query editor with code completion, CSV/JSON import/export; structure/data sync and scheduling are paid). Always good to see more OSS options — the checklist above is what I'd dogfood against, regardless of vendor.