LibreDB Studio is a database client you install next to the database instead of on every laptop. You reach it in a browser, so the database no longer needs a port open to the outside world. Sixteen drivers cover forty two engines, among them PostgreSQL, MySQL, Oracle, SQL Server, MongoDB, Redis, SQLite, ClickHouse, DuckDB, Elasticsearch, Trino and Cassandra, and they all sit in one sidebar.
It has the parts you would expect from a desktop client: a Monaco editor with schema aware completion, visual EXPLAIN, ER diagrams with real foreign key edges, schema diff with generated migration SQL, and a grid that handles millions of rows. The optional AI assistant runs against your own model, including a local Ollama, and its read only mode is enforced by the database rather than by parsing the SQL.
It deploys as a container, a Helm chart, an npm package, deb and rpm, or a Tauri desktop build. Authentication is local accounts or OIDC, with role based access control.
 Homepage
 Download
Recent Releases
0.16.221 Sep 2026 09:47
security:
Closes a cross-account authorization defect, GHSA-3wh2-8x78-jfw4, scored 8.8. A connection id supplied in a request could select another session's already-authenticated database provider, so a user account could reach a connection restricted to admin. The cache key is now derived from the server the connection resolves to and a digest of its credentials, so a forged id buys nothing. Upgrade if more than one account reaches your instance. Schema diff now reads a column default as a value rather than as SQL, so a default of 0, empty string or false is no longer dropped from the generated DDL. Elasticsearch connections can authenticate with an API key id and secret.
0.16.017 Sep 2026 14:07
minor feature:
The schema sidebar is now an object tree. Views, materialised views, sequences, routines and triggers are listed per engine, each folder carrying a count. Opening a deferred connection issues no catalog query, and a large folder mounts only the rows in view. View, routine and trigger definitions can be read, and edited where the engine allows it. The agent keeps a run history of the last fifty conversations.
0.15.015 Sep 2026 22:57
minor bugfix:
Database sizes the server declines to answer are now reported as absent rather than as 0 bytes, on MySQL, PostgreSQL, SQL Server and Oracle. An unmeasured database previously read as an empty one. The generated CREATE TABLE statement now emits the DDL of the engine it is aimed at instead of always emitting PostgreSQL's. Agent schema grounding no longer captures engine and extension objects. AWS Marketplace, Azure Marketplace and CasaOS channels are live.
| 
Yusuf Gundogdu