u/cevheribozoglan

Affiliation: I’m the maintainer of LibreDB Studio.

LibreDB Studio is a free, open-source, self-hosted web DB GUI. One browser UI for SQL + NoSQL (Postgres, MySQL, SQLite, Oracle, MSSQL, Mongo, Redis) on your own network, not another desktop install, not a single-engine admin panel.

Also ships as an npm package (@libredb/studio) so other web apps can embed the same UI. Optional AI/NL2SQL with your own key or local Ollama. OIDC supported. MIT.

Self-host:

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

helm install libredb oci://ghcr.io/libredb/charts/libredb-studio

# or: npx "@libredb/studio"

One-click: Railway, Dokploy, DigitalOcean Marketplace.... (search “LibreDB Studio”)

More deploy options: https://github.com/libredb/libredb-studio/tree/main/deploy

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

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

Happy to hear what works / what’s missing if you try it.

I wanted a DB GUI that runs in the browser and isn't locked to one engine Postgres today, Redis or Mongo tomorrow, same UI, self-hosted on my own box.

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-native, SQL + NoSQL in one app (Postgres, MySQL, SQLite, Oracle, MSSQL, Mongo, Redis).

Optional AI/NL2SQL is built-in and model-agnostic (local or cloud) not a separate SKU.

Short walkthrough: https://www.youtube.com/watch?v=wJPWPe1mJes

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

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

I maintain LibreDB Studio (open-source browser SQL IDE: Postgres/MySQL/SQLite/Oracle/MSSQL/Mongo/Redis). Wanted a zero-install path for people already on DigitalOcean, so I went through Marketplace as a 1-Click Droplet app.

A few things from the image side that might be useful if you've shipped (or are shipping) a Marketplace app:

- Packer builds Ubuntu 24.04 + Docker; the app image is pre-pulled so first boot isn't waiting on a pull.

- Per-Droplet secrets (JWT + admin/user passwords) are generated once in cloud-init first-boot, nothing baked into the snapshot. Creds land in /etc/libredb-studio.env (mode 600); MOTD points you there.

- systemd unit starts the container; SQLite data on a volume under /app/data so restarts keep state.

- Cleanup must run before snapshot without a reboot afterward, otherwise first-boot can bake the same secrets into every customer image (easy footgun).

Create from Marketplace --> SSH in --> open http://<droplet-ip>:3000. Happy to answer Marketplace/Packer questions; also curious what you'd change about the first-boot UX.

Marketplace: https://marketplace.digitalocean.com/apps/libredb-studio

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

I got tired of bouncing between desktop IDEs and random cloud SQL consoles for day-to-day DB work, so I built a self-hosted browser SQL IDE.

LibreDB Studio runs in Docker / npx / Helm. One UI for Postgres, MySQL, SQLite, Oracle, SQL Server, MongoDB, and Redis. Monaco editor, schema explorer, result grid; optional AI (or fully local with Ollama).

Why it matters for me (and maybe you):

- no desktop install for the team — just a URL on your VPN / private network

- multi-engine in one place (not only “another pgAdmin”)

- MIT, self-hostable, secrets stay on your infra

How it’s built (short):

- Next.js app + Strategy Pattern DB providers

- published image(ghcr and docker hub): ghcr.io/libredb/libredb-studio

- also in a few one-click catalogs (Dokploy, etc.)

try one command:

`docker run -d -p 3000:3000 libredb/libredb-studio:latest`

or `npx "@libredb/studio"` (Node 20.9+)

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

Demo: https://app.libredb.org

still early feedback on what’s confusing or missing is more useful than praise.

I’m the maintainer.

Been running LibreDB Studio (open-source browser SQL IDE 
Postgres/MySQL/SQLite/Oracle/MSSQL/Mongo/Redis) on my own Dokploy instance for a while, 
so I put together a template and got it merged into the official catalog
(Dokploy/templates#931). 
Template URL: https://templates.dokploy.com/?q=libredb+studio

A few things about the template mechanics that might be useful if you're
building your own:
- Per-install secrets (ADMIN_PASSWORD, USER_PASSWORD, JWT_SECRET) generated
  from ${password:32} / ${password:64} vars — nothing baked into the image,
  no manual secret entry.
- Single container, SQLite on a named volume for persistence — no external
  DB needed to get started.
- Domain assignment just maps the container's port 3000 behind Traefik,
  same as any other template.

Search "LibreDB Studio" in your template catalog to try it. Happy to answer
anything about the template setup itself — first time going through the
submission process, curious if others hit similar friction.

Links: https://github.com/libredb/libredb-studio · https://libredb.org

Hey folks, first-time posting here, so please be gentle😅

I’ve been working on an open-source project called LibreDB Studio.

It’s a browser-based SQL IDE you can self-host. I got tired of jumping between desktop tools and random cloud consoles, so I tried to build something lighter that still feels usable day to day.

What it does (roughly):

- Run queries in the browser (Monaco editor, like VS Code)

- Connect to PostgreSQL, MySQL, SQLite, Oracle, SQL Server, MongoDB, and Redis from one UI

- Optional AI for natural-language → SQL (Gemini / OpenAI / local Ollama) — can stay fully local if you want

- Schema explorer, result grid, basic monitoring bits

- Also ships as Docker / Helm / npx (and a few one-click templates)

Try it in one command(node or docker):

npx @libredb/studio

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

Then open http://localhost:3000 on first run the admin password is printed in the logs (zero-config).

I’m not pitching this as finished or perfect — there’s still plenty I want to improve.

That said, it’s MIT, it runs in one command, and I’d really value feedback from people who live in databases / self-hosting.

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

Live demo (no install): https://app.libredb.org

Website: https://libredb.org

If you prefer one-click instead of a terminal: dokploy (official template catalog), railway, cap-rover, cosmos, kubero both have ready deploys, links in the first comment.

If you try it: what feels broken, confusing, or missing? Honest feedback > polite praise.