Twelve database projects now list LibreDB Studio in their docs
PostgreSQL, Redis, ClickHouse, MariaDB, DuckDB, Trino, YugabyteDB, StarRocks, DragonflyDB, OpenSearch, Apache Cloudberry and Aiven now list LibreDB Studio in their official documentation. Every entry went through the project's own review.
Twelve database projects now list LibreDB Studio in their official documentation or ecosystem pages:
- PostgreSQL
- Redis
- ClickHouse
- MariaDB
- DuckDB
- Trino
- YugabyteDB
- StarRocks
- DragonflyDB
- OpenSearch
- Apache Cloudberry (Incubating)
- Aiven
Why a docs page matters to us
A documentation page is where someone goes after they have already picked a database and are asking what to use with it. Being there means the project’s maintainers looked at the tool and agreed it works with their engine.
What LibreDB Studio is
A database editor you deploy next to your database, as a container, a Helm chart or a Kubernetes operator, and open in the browser. No port opened to the internet, no SSH tunnel, no desktop client on every laptop.
It ships eighteen drivers. Twenty-eight more engines speak one of those wire protocols and connect through an existing driver. Each of the twenty-eight was tested against a live instance, and the compatibility table says how much works on each: eighteen fully, nine partially, one in the query editor only.
Everything is MIT licensed, including SSO, role-based access and the AI assistant. There is no paid edition.
docker run -d -p 3000:3000 ghcr.io/libredb/libredb-studio:latestSource: github.com/libredb/libredb-studio · Demo: app.libredb.org