LibreDB Studio

The database editor that deploys right next to your data.

LibreDB Studio is an open-source, MIT-licensed database IDE that runs in a browser and deploys as a container alongside your database rather than as a desktop client on a laptop. It addresses the problem of reaching databases that sit inside Kubernetes, PaaS platforms or customer VPCs, where exposing ports or maintaining SSH tunnels and per-seat desktop clients is impractical. One interface covers nineteen engines, including PostgreSQL, MySQL, Oracle, SQL Server, SQLite, libSQL, DuckDB, ClickHouse, Apache Druid, Trino, MongoDB, Couchbase, Redis, LibreDB, Cassandra, Elasticsearch, OpenSearch, Prometheus and Apache Kong.

Core capabilities include a schema-aware Monaco SQL editor with catalog-driven completion, formatting and schema diff, visual EXPLAIN plan trees, ER diagrams generated from foreign keys, a live health dashboard, and AI features that can explain queries, draft SQL and run pre-execution risk analysis via Gemini, OpenAI, Ollama or any OpenAI-compatible endpoint. A database agent runs read-only, budgeted SQL and produces cited reports, currently on PostgreSQL, SQLite and DuckDB. Security controls include OIDC single sign-on, role-based access control, credential encryption and an audit trail of executed queries.

LibreDB Studio is aimed at developers, DBAs and teams working across multiple database engines. It is distributed as a single MIT-licensed build with no edition tiers or seat-based licensing; deployment options include Docker, Helm, npm and other channels, with a live demo available.

12 alternatives to LibreDB Studio

Ranked by how well each tool replaces LibreDB Studio: shared features, audience, price and popularity.

TablePlus
Database management made easy.
Covers 0 of 15 key features.
63 out of 100 match—
MariaDB Server (MariaDB Foundation)
Open source relational database maintained by the MariaDB Foundation
Covers 0 of 15 key features.
Free planOpen source
62 out of 100 matchFree
Beekeeper Studio
Modern, easy-to-use SQL client for MySQL, Postgres, SQLite, SQL Server, Firebird, and more
Covers 0 of 15 key features.
Free planOpen source
62 out of 100 match$9/mo
Apache Drill
Schema-free SQL query engine for Hadoop, NoSQL and cloud storage
Covers 0 of 15 key features.
Free planOpen source
62 out of 100 matchContact sales
PostgreSQL
Open source object-relational database system
Covers 0 of 15 key features.
Free planOpen source
61 out of 100 matchFree
SQLite Online
Browser-based SQL editor for SQLite, PostgreSQL, MySQL and other databases
Covers 0 of 15 key features.
Free plan
61 out of 100 matchContact sales
DBeaver
Professional database management software for 100+ data sources
Covers 0 of 15 key features.
Free planOpen source
61 out of 100 matchContact sales
NocoDB
Instantly turn your Database into a No-Code Platform
Covers 0 of 15 key features.
Free planOpen source
61 out of 100 match$108/mo
HeidiSQL
Free open-source database client for Windows, Linux and macOS
Covers 0 of 15 key features.
Free planOpen source
61 out of 100 matchFree
DB Browser for SQLite
A high quality, visual, open source tool to create, search, and edit SQLite or SQLCipher 3
Covers 0 of 15 key features.
Free planOpen source
60 out of 100 matchFree
DbVisualizer
A cross-platform SQL client and database management tool for connecting to, exploring and
Covers 0 of 15 key features.
Free plan
60 out of 100 matchFree
Letos
Create, edit, browse SQLite databases.
Covers 0 of 15 key features.
Free planOpen source
59 out of 100 matchFree

Key facts

Starts at: Free
Free plan: Yes
Free trial: No
Open source: Yes

What it does

Schema aware sql editor built on the monaco editor with table and column completion drawn from the live catalog formatting snippets multi tab workspace schema diff across snapshots or connections with migration sql generation for postgresql mysql sqlite oracle sql server and clickhouse column modifications and a snapshot timeline for comparing any two points
Visual explain rendering execution plans as trees with scan types join strategies and costs per node reading each engine s own plan output for postgresql mysql duckdb clickhouse trino and others
Er diagrams discovered from declared foreign keys laid out hierarchically with elk js with cardinality labels minimap navigation table search and filter compact mode and export as png or svg
Ai query assistance using gemini openai ollama or any openai compatible endpoint including query explainer plain language query drafting pre execution risk analysis for delete drop and truncate and data profiler summaries the connected schema is sent with the request and generated sql must be read before it runs with no model configured the ai rail does not render
Live health dashboard with seven tabs covering overview performance queries sessions tables storage and connection pool time series trends auto refresh from 5s to 60s colour coded health thresholds live pool metrics one click maintenance commands vacuum analyze reindex update statistics dbcc checkdb alter index rebuild and an audit trail of every query executed across the organisation
Database agent with investigate optimize and assess workflows that runs read only budgeted sql and writes a report citing results bounded at 20 statements 60s of database time 200 rows per read and a 5 minute deadline read only enforced natively on postgresql sqlite and duckdb only plan mode available on every connection the embedded libredb studio package has no agent surface
Openid connect single sign on with auth0 keycloak okta entra id or any oidc provider over authorization code flow with pkce session is a jwt in an httponly samesite lax cookie with a fixed 24 hour token lifetime
Role based access control with per connection visibility scoping admins only users or everyone roles mapped from identity provider claims
Database credentials resolved from environment variables at runtime so secrets stay out of config files
Credentials at rest encrypted with aes 256 gcm when a server side store is used from storage encryption key or derived from jwt secret
Tls between browser and app and tls or ssh tunnels between app and databases including databases behind a firewall with no public exposure
Request integrity controls origin referer checks on state changing requests csp hsts x content type options x frame options referrer policy and permissions policy headers with logins denials and rate limit trips written to the audit log and emitted as structured json on stdout
Self hosting as the default deployment path with nothing required to leave the network perimeter including fully local ai via ollama or lm studio
Supply chain controls mit source sha 256 checksums on every release codeql and sonarcloud in ci dependency scanning on every pull request daily published image scanning and credential scanning of every commit
Sensitive column masking across grid exports and clipboard with rbac enforced described as a display level control to be paired with database side grants

Information is collected from libredb.org and public sources. Spotted something wrong? Tell us