Frequently asked

The short answers, with nothing softened

Every answer below is the same claim the product makes elsewhere on this site. Where a limit exists, it is stated rather than left for you to find.

01 What does "the tool goes to the data" actually mean?

Studio runs as a container inside the same private network as your database, and you reach it over a URL. Nothing is exposed to the internet, no SSH tunnel is dug, and the data never travels — only the query and its result do.

02 Which databases are supported?

Seventeen engines: PostgreSQL, MySQL, Oracle, SQL Server, SQLite, libSQL, DuckDB, ClickHouse, Apache Druid, Apache Trino, MongoDB, Couchbase, Redis, LibreDB, Cassandra, Elasticsearch and OpenSearch — relational, document, key-value, wide-column, analytical, search and federated query.

03 Is anything held back from the open-source build?

No. OIDC single sign-on, ER diagrams, the AI assistant and the MongoDB and Redis drivers are all in the MIT build. What costs money is someone else running it for you; no capability moves across that line to create a reason to upgrade.

04 Why does each engine list what it does not do?

Because a feature list quietly breaks on the fourth engine. Capability flags come from the provider itself, so a control that cannot work is hidden rather than offered and then failed — Cassandra has no joins, search engines have no row editing, ClickHouse has no foreign keys to draw.

05 How do I install it?

One container: docker run -p 3000:3000 libredb/libredb-studio. There is also an npx package, a Helm chart, a certified chart in Rancher Partner Charts, an embeddable npm package and one-click templates for Railway, Dokploy, CapRover, DigitalOcean, Sealos and Fly.io — 33 channels, 26 of them live.

06 Does it work on a phone?

Yes. There is dedicated mobile navigation and a card view for results, because the query that matters is often the one you run on call, away from a laptop.

07 What does the database agent do?

You state an objective; the agent runs read-only, budgeted SQL and writes a report where every claim cites a result. It is available on PostgreSQL and SQLite.

08 How is it secured for a team?

OIDC single sign-on, role-based access control, an audit trail of every executed query, and risk analysis before a destructive statement runs. First boot generates its own secrets and prints them once; native channels bind to localhost by default.

Still unanswered? The architecture notes and provider docs live in the repository. Read the docs ↗