--- title: "LibreDB Studio: an open source, self-hosted SQL IDE for PostgreSQL in the browser" url: https://daily.dev/posts/libredb-studio-an-open-source-self-hosted-sql-ide-for-postgresql-in-the-browser-hamfaprfe source_url: https://www.postgresql.org/about/news/libredb-studio-an-open-source-self-hosted-sql-ide-for-postgresql-in-the-browser-3368 type: article source: "PostgreSQL" published: 2026-08-20T23:37:28.369Z updated: 2026-08-20T23:38:15.410Z tags: ["open-source", "database", "postgresql"] reading_time: 2 upvotes: 59 comments: 4 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # LibreDB Studio: an open source, self-hosted SQL IDE for PostgreSQL in the browser **[PostgreSQL](https://daily.dev/sources/postgres)** · 2 min read · 59 upvotes · 4 comments ## Summary LibreDB Studio is an MIT-licensed, self-hosted SQL IDE for PostgreSQL that runs in the browser and deploys as a container, Helm chart, or npm package alongside the database it manages. It uses pooled connections with explicit transactions and an auto-rollback timeout, supports query cancellation via pg_cancel_backend, and performs staged schema introspection for large databases with hundreds of tables. Monitoring relies on pg_stat_* views and gracefully degrades based on the connected role's permissions. An optional query assistant is grounded in the live schema before generating statements, and read-only runs execute inside BEGIN READ ONLY. Authentication supports local accounts or OIDC with role-based access control on every API route. The current release is version 0.12.0. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is LibreDB Studio and how does it connect to PostgreSQL? LibreDB Studio is an MIT-licensed, self-hosted SQL IDE for PostgreSQL that runs in the browser and is deployed as a container, Helm chart, or npm package next to the database it manages rather than installed on developer machines. It uses pooled connections, explicit BEGIN/COMMIT/ROLLBACK transactions with an auto-rollback timeout, and query cancellation via pg_cancel_backend on the tracked backend PID. _Teams evaluating self-hosted database tooling can track releases like this one on daily.dev._ ### How does LibreDB Studio's AI query assistant avoid hallucinating table or column names? The query assistant is given the real schema of the connected database before its first turn, so a drafted SQL statement names objects that actually exist rather than relying only on prompt text. Read-only runs execute inside a single BEGIN READ ONLY statement over the extended protocol, limiting what a generated query can do even if it errs. _Developers weighing AI-assisted SQL tools against manual query writing can follow tools like this on daily.dev._ ### How does LibreDB Studio handle schema introspection on PostgreSQL databases with hundreds of tables? Schema introspection is designed to stay responsive on large databases by rendering the table tree from a first pass while relationships stream in from a second pass. Monitoring reads pg_stat_* views, including pg_stat_statements when installed, and degrades gracefully to what the connected role can see instead of failing when superuser-only views are unavailable. _Engineers managing large PostgreSQL schemas can keep an eye on tooling improvements like this via daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@allinonetools** · 5 upvotes > This looks really useful, especially the staged schema introspection and auto-rollback. Self-hosted + PostgreSQL support makes it even more interesting. **@trevorsuna** · 1 upvotes > The explicit transactions and auto-rollback timeout are smart safeguards for a browser-based SQL tool. Staged introspection also sounds important for real databases, where eagerly loading hundreds of tables can turn a convenient IDE into its own performance problem. **@agustinbarrientos** · 0 upvotes > Every destructive query should confirm the database, role, and transaction timeout before it runs. I'd make the target banner impossible to dismiss while the browser IDE has an active transaction. ## Similar posts on daily.dev - [The browser is your database: Local-first comes of age](https://daily.dev/posts/the-browser-is-your-database-local-first-comes-of-age-qpvygfxu9) · InfoWorld · 4 upvotes · 0 comments --- Tags: [#open-source](https://daily.dev/tags/open-source), [#database](https://daily.dev/tags/database), [#postgresql](https://daily.dev/tags/postgresql) [View this post on daily.dev](https://daily.dev/posts/libredb-studio-an-open-source-self-hosted-sql-ide-for-postgresql-in-the-browser-hamfaprfe)