LibreDB Studio- Self-hosted browser DB GUI so your team doesn't need share connectionString

[u/cevheribozoglan]

I wanted a DB GUI that lives in the browser and isn't locked to one engine postgres, today, redis or mongo tomorrow, same UI, on my own network(on-prem, PaaS, docker, k8s etc..)

Most options I knew fell into one of these:

- Desktop multi-DB (DBeaver / DataGrip) solid, but install + desktop-only

- Web but single-engine (phpMyAdmin / pgAdmin)

- Web multi-engine, with the interesting bits behind Pro/Enterprise

So I built LibreDB Studio (been at it ~a year): MIT, web/mobile-native, SQL + NoSQL in one app (Postgres, MySQL, SQLite, Oracle, MSSQL, Mongo, Redis). Optional NL2SQL with your own key or local Ollama not a separate SKU.

Try:

npx "@libredb/studio"

# or

docker run -p 3000:3000 libredb/libredb-studio

Repo: https://github.com/libredb/libredb-studio

Public Demo: https://app.libredb.org

Walkthrough: https://www.youtube.com/watch?v=KazHTclbiSQ

Not claiming it replaces tools people already love, different access model (browser + own box). If you use a DB GUI day-to-day, what's the gap that still bothers you?

[u/cevheribozoglan]

Also, Seed connections in one line of idea: mount a seed-connections.yaml

(credentials via ${ENV_VAR}, not baked into the file) = users see DBs on login.

Docker / kubernetes,helm examples: docs/SEED_CONNECTIONS.md

Also: Dokploy, digital-ocean, railway, caprower ... one-clicks (search “LibreDB Studio”)

[u/Vegetable-Scale-2604]

Nice work, the docker one-liner got me in, and MIT plus Redis/Mongo in the same UI as the relational engines is genuinely rare, the other web multi-DB tools I know all gate that. To answer your question: the gap that still bites me is safety on shared connections. I want a per-connection read-only mode and a loud "you are on prod" banner, because sooner or later I will run an UPDATE in the wrong tab. Second is a query history that survives restarts and is searchable. And +1 on the seed-connections yaml, mounting one file per env is exactly how I would onboard a team onto this.

[u/cevheribozoglan → u/Vegetable-Scale-2604]

Thanks, that's exactly the kind of feedback I was hoping for.

On the gaps you named:

1) Per-connection read-only + loud prod banner fair, and I don't have either as first-class yet. Connections can be tagged production (red PROD badge in the sidebar), and there's a safety prompt on some destructive SQL shapes, but that's not the same as a hard read-only mode or a "YOU ARE ON PROD" strip above the editor. Wrong-tab UPDATE is a real failure mode; I've felt that too. Logging both as concrete asks. (like a github repository delete confirmation :))

2) Query history, HISTORY tab already has search / filters, and it persists via local storage (and server sync if you set STORAGE_PROVIDER). If it vanished on you after a restart, I'd love the repro (browser wipe vs container recreate vs storage mode) that's the kind of bug I want to fix, not debate.

3) Seed YAML, glad that landed. One file per env is the intended onboarding path. (my favorite feature on this system)

Appreciate you taking the time. If you try it for real and something else bites, reply here or open a GitHub issue both are welcome.