PostgreSQL
SQLThe reference engine — pooled connections, full catalog introspection, visual EXPLAIN, ER diagrams, live health and agent mode.
- TRANSPORT
- pg pool · 5432
- REFERENCE
- docs/providers/postgres.md
Open source · MIT · v0.13.4
You created the database.
The editor is already beside it.
LibreDB Studio is the database IDE that deploys next to your data instead of onto your laptop — one browser tab for PostgreSQL, MySQL, MongoDB, Redis and thirteen more engines, with SSO and audit built in.
docker run -p 3000:3000 libredb/libredb-studio or npx @libredb/studio — no Docker needed. Running in about ten seconds.
Why it exists
The database took forty seconds. Reaching it took the afternoon.
You create a Postgres on Railway. It is ready before your coffee. Then you want to look inside it — so you expose a port to the internet, or install a desktop client and dig an SSH tunnel, or give up and drive it from a shell.
Databases moved — into Kubernetes, into PaaS platforms, into a customer's VPC. The tools that read them did not. They are still desktop applications: heavy, licensed per seat, built for one database, one laptop, one person who never changes machines.
✕ database exposed to the internet — closed by the first security review ✕ tunnel dropped — reconnect, re-authenticate, start over ✕ works — on one machine, for one person, until they change laptops → https://studio.internal — every browser, every phone on the team
The tool goes to the data. Not the data to the tool.
Take that seriously and it becomes a specification: the editor has to run in a browser, reach a phone, deploy like infrastructure and stay unrestricted. MIT is not generosity — it is a requirement of the architecture.
✕ dumps, replicas, tunnels — terabytes travel to one machine → the data never leaves the network — a URL travels instead
runs in a browserreaches a phonedeploys like infrastructureMIT licensed
How it works
From forty seconds to the whole team
-
01
Create the database
A one-line provision, a Helm release, a managed instance — ready in forty seconds, inside a network your laptop cannot see.
-
02
Deploy Studio beside it
One container next to the database. Same network, nothing exposed to the outside, no SSH tunnel dug. Docker, Helm, an operator, or a one-click template.
-
03
Open a browser tab
The editor is a URL. It reaches your laptop, your teammate's machine, and the phone you are holding during an incident. Nothing to install, ever again.
-
04
Sign the whole team in
OIDC single sign-on, role-based access control, an audit trail of every executed query, and risk analysis before a destructive statement runs.
Seventeen engines
One interface.
Different engines.
Relational, document, key-value, analytical, search and federated query — the same tree, editor and grid over each of them, and each engine's real limits declared rather than papered over.
What this engine does not do
Nothing held back — every capability in the product ships here, including agent mode.
Stated because the alternative is a feature list that quietly breaks on the fourth engine. Capability flags come from the provider itself — a control that cannot work is hidden, not offered and then failed.
MySQL
SQLPooled connections with information_schema introspection, EXPLAIN plans and performance_schema-backed monitoring.
- TRANSPORT
- mysql2 pool · 3306
- REFERENCE
- docs/providers/mysql.md
What this engine does not do
Agent mode is unavailable, as on every engine but PostgreSQL, SQLite and DuckDB.
Stated because the alternative is a feature list that quietly breaks on the fourth engine. Capability flags come from the provider itself — a control that cannot work is hidden, not offered and then failed.
Oracle
SQLPooled connections with introspection and monitoring through the ALL_* and DBA_* data-dictionary views.
- TRANSPORT
- oracledb pool · 1521
- REFERENCE
- docs/providers/oracle.md
What this engine does not do
Agent mode is unavailable here. Operate still reads the server's own reporting interface.
Stated because the alternative is a feature list that quietly breaks on the fourth engine. Capability flags come from the provider itself — a control that cannot work is hidden, not offered and then failed.
SQL Server
SQLPooled connections with sys.* catalog introspection, estimated plans and DMV-backed monitoring.
- TRANSPORT
- mssql pool · 1433
- REFERENCE
- docs/providers/mssql.md
What this engine does not do
Agent mode is unavailable here; the editor, diagrams and health are identical.
Stated because the alternative is a feature list that quietly breaks on the fourth engine. Capability flags come from the provider itself — a control that cannot work is hidden, not offered and then failed.
SQLite
SQLThe embedded engine — a file, no network. Full editor, ER diagrams, EXPLAIN and agent mode.
- TRANSPORT
- file · embedded
- REFERENCE
- docs/providers/sqlite.md
What this engine does not do
There is no server to monitor: health reads file size and pragma statistics only.
Stated because the alternative is a feature list that quietly breaks on the fourth engine. Capability flags come from the provider itself — a control that cannot work is hidden, not offered and then failed.
libSQL
SQLSQLite's dialect over the network — Turso and self-hosted sqld, spoken natively.
- TRANSPORT
- hrana · 443
- REFERENCE
- docs/providers/libsql.md
What this engine does not do
Monitoring is limited to what the sqld server itself exposes.
Stated because the alternative is a feature list that quietly breaks on the fourth engine. Capability flags come from the provider itself — a control that cannot work is hidden, not offered and then failed.
DuckDB
AnalyticsIn-process analytics — query Parquet and CSV files directly, with full EXPLAIN support and agent mode.
- TRANSPORT
- file · embedded
- REFERENCE
- docs/providers/duckdb.md
What this engine does not do
Single-writer by design: no sessions to list, so health shows storage, not connections.
Stated because the alternative is a feature list that quietly breaks on the fourth engine. Capability flags come from the provider itself — a control that cannot work is hidden, not offered and then failed.
ClickHouse
AnalyticsHTTP interface with system.* introspection, EXPLAIN pipelines and query-log monitoring.
- TRANSPORT
- http · 8123
- REFERENCE
- docs/providers/clickhouse.md
What this engine does not do
No foreign keys exist, so ER diagrams show structure without discovered relations.
Stated because the alternative is a feature list that quietly breaks on the fourth engine. Capability flags come from the provider itself — a control that cannot work is hidden, not offered and then failed.
Apache Druid
AnalyticsSQL over HTTP with datasource and segment introspection for streaming analytics.
- TRANSPORT
- http · 8888
- REFERENCE
- docs/providers/druid.md
What this engine does not do
Append-oriented: row editing is disabled rather than offered and then failed.
Stated because the alternative is a feature list that quietly breaks on the fourth engine. Capability flags come from the provider itself — a control that cannot work is hidden, not offered and then failed.
Apache Trino
FederatedFederated SQL — one query across the catalogs you already have, from object storage to RDBMS.
- TRANSPORT
- http · 8080
- REFERENCE
- docs/providers/trino.md
What this engine does not do
Trino queries catalogs; it does not manage a lakehouse. Writes depend on the underlying connector.
Stated because the alternative is a feature list that quietly breaks on the fourth engine. Capability flags come from the provider itself — a control that cannot work is hidden, not offered and then failed.
MongoDB
DocumentDocument browsing, aggregation pipelines and index introspection over the native driver.
- TRANSPORT
- driver · 27017
- REFERENCE
- docs/providers/mongodb.md
What this engine does not do
No SQL translation layer is faked — queries here are MongoDB queries.
Stated because the alternative is a feature list that quietly breaks on the fourth engine. Capability flags come from the provider itself — a control that cannot work is hidden, not offered and then failed.
Couchbase
DocumentSQL++ queries with bucket, scope and collection introspection over the documented REST surfaces.
- TRANSPORT
- http · 8091
- REFERENCE
- docs/providers/couchbase.md
What this engine does not do
Agent mode is unavailable, as on every engine but PostgreSQL, SQLite and DuckDB.
Stated because the alternative is a feature list that quietly breaks on the fourth engine. Capability flags come from the provider itself — a control that cannot work is hidden, not offered and then failed.
Redis
Key-valueKey browsing by pattern, type-aware value views and INFO-backed live monitoring.
- TRANSPORT
- resp · 6379
- REFERENCE
- docs/providers/redis.md
What this engine does not do
No SQL, and none is pretended — the editor speaks commands here.
Stated because the alternative is a feature list that quietly breaks on the fourth engine. Capability flags come from the provider itself — a control that cannot work is hidden, not offered and then failed.
LibreDB
Key-valueThe embedded ordered key-value store — a file, no server and no wire protocol. Mapped onto the interface by convention rather than by emulating SQL.
- TRANSPORT
- file · embedded
- REFERENCE
- docs/providers/libredb.md
What this engine does not do
No sessions and no index objects exist, so those two panels are absent with their reason rather than answered empty. Maintenance operations are refused, not faked.
Stated because the alternative is a feature list that quietly breaks on the fourth engine. Capability flags come from the provider itself — a control that cannot work is hidden, not offered and then failed.
Cassandra
Wide-columnCQL editor with keyspace, table and type introspection for wide-column data.
- TRANSPORT
- cql · 9042
- REFERENCE
- docs/providers/cassandra.md
What this engine does not do
No joins and no EXPLAIN — the grid respects partition-key query rules instead of hiding them.
Stated because the alternative is a feature list that quietly breaks on the fourth engine. Capability flags come from the provider itself — a control that cannot work is hidden, not offered and then failed.
Elasticsearch
SearchQuery DSL and browsing over indices, with mapping introspection and cluster health.
- TRANSPORT
- http · 9200
- REFERENCE
- docs/providers/elasticsearch.md
What this engine does not do
Search engines are query-and-browse: no row editing, no ER diagrams.
Stated because the alternative is a feature list that quietly breaks on the fourth engine. Capability flags come from the provider itself — a control that cannot work is hidden, not offered and then failed.
OpenSearch
SearchThe same query-and-browse surface as Elasticsearch, against OpenSearch clusters.
- TRANSPORT
- http · 9200
- REFERENCE
- docs/providers/opensearch.md
What this engine does not do
Search engines are query-and-browse: no row editing, no ER diagrams.
Stated because the alternative is a feature list that quietly breaks on the fourth engine. Capability flags come from the provider itself — a control that cannot work is hidden, not offered and then failed.
The claim is the span, not a count — seventeen engines, one interface. Per-engine detail lives in the provider docs.
The product
A serious IDE, not an admin panel
Monaco under the hood, a virtualized grid over millions of rows, and the panels a DBA actually opens.
studio — live tour query.sql query.sql query.sql studio — on a phone postgres · prod-eu
⌘K filter tables…
▸ public
▤ orders 184k
id uuid PK
user_id FK
status text
total_cents int4
▤ users 12.4k
▤ order_items 512k
▤ products 2.1k
▤ payments 96k
-- checkout latency, last 24 h
SELECT o.id, u.email, o.total_cents, o.created_at
FROM orders o
JOIN users u ON u.id = o.user_id
WHERE o.status = 'pending'
ORDER BY o.created_at DESC
LIMIT 50; Results History Saved 50 rows · 14 ms
idemailtotal_centscreated_at
▤ users
id uuid PK
email text
▤ orders
id uuid PK
user_id FK
status text
▤ order_items
order_id FK
product_id FK
qty int4
▤ products
id uuid PK
price_cents int4
3 foreign keys · discovered from the schema · export SVG / PNG
Active sessions
24
Cache hit ratio
99.2%
Database size
4.2 GB
Slowest queries · last hour
SELECT … FROM order_items JOIN products ON … 1840 ms
UPDATE orders SET status = … WHERE created_at < … 902 ms
SELECT count(*) FROM payments WHERE settled = false 488 ms
read from the engine's own reporting interface · sessions can be terminated from here
The incident does not wait
The same editor reaches the phone in your pocket
Dedicated mobile navigation and card views for results — because the query that matters is often the one you run on call, away from a laptop.
What ships
Everything a database IDE owes you
- 01
Schema-aware SQL editor
Monaco under the hood — table and column completion, formatting, snippets, ⌘⏎ to run.
- 02
Visual EXPLAIN
Plan trees for PostgreSQL, MySQL, DuckDB, ClickHouse, Trino and more — scan types, joins and costs, drawn.
- 03
ER diagrams
Foreign-key graphs discovered from the schema. Pan, filter, and export as SVG or PNG.
- 04
AI that knows your schema
Explain a query or draft one in plain language — Gemini, OpenAI, Ollama or any compatible endpoint. Generated SQL is yours to read before it runs.
- 05
Live health dashboard
Sessions, slow queries, cache hit ratios and storage — read from each engine's own reporting interface.
- 06
The database agent
State an objective; the agent runs read-only, budgeted SQL and writes a report where every claim cites a result.
Open source
Nothing sits behind an enterprise wall
LibreDB Studio is MIT because it has to go everywhere. What costs money is someone else running it for you — no capability moves across that line to create a reason to upgrade.
| Capability | LibreDB Studio | Typical community editions |
|---|---|---|
| OIDC single sign-on | in the MIT build | Enterprise, AWS only |
| ER diagrams | in the MIT build | PRO editions |
| AI assistant | in the MIT build | Enterprise |
| MongoDB and Redis | in the MIT build | absent from community driver sets |
License and feature scope only, each line with a primary source — the full table lives on the comparison page.
- 100% line coverage, enforced as a CI gate
- 17 engines — SQL, NoSQL, analytics and search
- 33 distribution channels, 25 of them live
- MIT license. All of it, nothing held back
Deploy
It installs like infrastructure, because it is
A container, a Helm chart, a certified Rancher listing, a one-click template, or an npm package embedded inside your own product.
docker run -p 3000:3000 libredb/libredb-studio
# zero-config first run — secrets generated at boot, printed once
npx @libredb/studio
# no Docker needed — binds to 127.0.0.1 by default
helm install studio ./charts/libredb-studio
# also a certified chart in Rancher Partner Charts
npm i @libredb/studio
# mount the editor inside the product that created the database
Railway →Dokploy →CapRover →DigitalOcean →Sealos →
# one click on the platform that already runs your database
Bring the editor to the data.
Open the live demo, or have your own Studio running next to your database in about a minute.
github.com/libredb/libredb-studio ↗