LibreDB Studio is the open-source database IDE that deploys next to your data instead of onto your laptop, one browser tab for PostgreSQL, MongoDB, Redis and thirteen more engines. No tunnelling from a laptop into production, no handing credentials to a cloud service. Run it with one docker run, one Helm chart, or npx. SSO, audit trail, ER diagrams and AI-assisted queries are all MIT licensed, with nothing behind an enterprise wall. Live demo, no install: app.libredb.org
Hi Product Hunt π
Every database GUI I tried made me pick one of two bad options: run it on my laptop and tunnel into production, or pay a cloud service and hand it my credentials. Neither felt right for a team's production data, so I started building the third option, a tool that deploys next to the data. One docker run, one Helm chart, or npx @libredb/studio.
What changed along the way was scope. I started with PostgreSQL. Then people asked for MySQL, then MongoDB, then Redis, and once the provider layer was a clean abstraction, adding engines stopped being the hard part. It speaks 17 today: PostgreSQL, MySQL, SQLite, libSQL, DuckDB, Oracle, SQL Server, MongoDB, Redis, Couchbase, ClickHouse, Druid, Elasticsearch, OpenSearch, Trino, Cassandra and LibreDB.
What I did not expect was who would pick it up. It is now listed in the PostgreSQL News, Wiki and Software Catalogue, and in the Redis, ClickHouse and Apache Druid documentation. Those listings, more than the star count, are why I finally felt ready to post here.
Everything is MIT. SSO, the audit trail, the AI query assistant, there is no enterprise tier holding any of it back.
Try it without installing anything: https://libredb.org (demo credentials are on the homepage panel)
I will be around all day. I would genuinely like to hear which engine you would want next, and what your current tool does better than mine.
Report
Maker
@libredbΒ Same-day note, because it is actually about how you install this.
We got accepted into Dockerβs sponsored open-source programme today. That lifts pull rate limits on the Hub mirror (libredb/libredb-studio), so the README docker run does not depend on being logged in. Canonical image is still GHCR; Hub is the discoverability path.
Happy accident of timing. If you were going to try the one-liner, that path just got less annoying.
Report
π Pixel perfection
Great to see LibreDB Studio launching! π
I had the opportunity to contribute to the frontend, working on the Next.js routing and authentication flow, as well as improving the light/dark theme experience across the UI. Really happy to see the project live.
auth and theme are what people hit before they ever write a query, so getting those right matters more than another provider. Appreciate you being in there.
@libredbΒ Same-day note, because it is actually about how you install this.
We got accepted into Dockerβs sponsored open-source programme today. That lifts pull rate limits on the Hub mirror (libredb/libredb-studio), so the README docker run does not depend on being logged in. Canonical image is still GHCR; Hub is the discoverability path.
Happy accident of timing. If you were going to try the one-liner, that path just got less annoying.
Great to see LibreDB Studio launching! π
I had the opportunity to contribute to the frontend, working on the Next.js routing and authentication flow, as well as improving the light/dark theme experience across the UI. Really happy to see the project live.
Congrats to the team! π
Thanks@omerfarukbolatΒ
auth and theme are what people hit before they ever write a query, so getting those right matters more than another provider. Appreciate you being in there.