Disclosure first: I help maintain this. MIT licensed, no paid tier, no enterprise edition.
The sysadmin problem it addresses: giving people read access to a database without giving them a path to it. The usual answers are a jump host, a VPN plus a desktop client on every machine, or a port you promised yourself you would close later. Each one adds an account to deprovision when somebody leaves.
LibreDB Studio runs as one container inside the network the database already lives in, and people reach it in a browser. Nothing per workstation, nothing exposed outward.
What makes it relevant to this community specifically:
- OIDC single sign-on and role based access control in the free build. Hook it to Keycloak, Entra, Authentik or whatever you already run, and offboarding is one account in one place rather than N desktop installs.
- An audit trail in the admin console. Sign-ins, permission denials, maintenance actions, object edits, and agent and MCP operations, each with the user behind it, plus the signed-in admin's own query history. Exports as CSV or JSON. To be precise about scope: this is not a transcript of every statement every user runs in the editor.
- Column level masking. Columns the app reads as personal data stay masked until someone with the right role unmasks them.
- The optional AI agent runs read-only, enforced by the database rather than by a parser. A read-only transaction on PostgreSQL,
PRAGMA query_onlyre-asserted per statement on SQLite, aREAD_ONLYhandle on DuckDB, and on SQL Server a session principal verified at open to be unable to write. Writes and DDL are refused before the database is reached. That pipeline is the agent's alone; statements you type in the editor go straight to the provider, so for human users the real boundary is still the grant on the connection. - 42 drivers reaching 69 engines, so one tool covers the Postgres, the MySQL, the Redis and the Mongo instead of four.
Runs as a Docker image, a Helm chart or a Kubernetes operator, and there are deb and rpm packages if you would rather not run a container.
docker run -d -p 3000:3000 ghcr.io/libredb/libredb-studio:latest
Honest limits: Redis is single node only for now, no Cluster, no Sentinel, no TLS. Druid, Elasticsearch, OpenSearch and Trino take host and port rather than a connection string. Cassandra reports no row count or table size, because the numbers it publishes are estimates that are often wrong, so it shows nothing instead.
Repo: https://github.com/libredb/libredb-studio Demo: https://trial.libredb.org/ (admin@libredb.org / Admin!2026)
Posted this in c/selfhosted earlier today from the homelab angle; this one is written for the people who have to answer for the access list.
AI use, since it comes up: of 2,508 commits in the public history, 31 carry Co-Authored-By: Claude, 8 say "Generated with Claude Code" and 35 mention Copilot, so AI assisted on part of the implementation and review while humans did the bulk. CONTRIBUTING.md states the project's policy.
Edit: tightened the audit and read-only bullets. The first version said the audit trail covers every statement and that read-only is grant-enforced in general; both were broader than what the project's own docs claim, and the text above now matches them.