1
Clone & Install
$ git clone https://github.com/libredb/libredb-studio.git$ cd libredb-studio$ bun install
✦ AI · Query explanation
Run it in one command — Docker (ghcr.io image) or npx, no clone or build — then open localhost:3000. Building from source (clone, install, dev server) is the separate contributor path below.
get_started.sql
SELECT step, title, command FROM quickstart ORDER BY step;3 rows |3 cols1ms
Get started in minutes
One command to run it — or build from source.
Run it — zero install
all deploy channels →No clone, no build — one command, then open localhost:3000.
Docker
$ docker run -d -p 3000:3000 ghcr.io/libredb/libredb-studio:latestnpx · Node 20.9+
$ npx @libredb/studioOn first run the admin password is printed to the log — zero-config. Open localhost:3000 and log in.
-- 70s: install → connect your database → first query. the steps below, in motion.
Build from source
For contributors and local development — clone the repo and run the dev server.
2
Configure
$ cp .env.example .env.local# set JWT_SECRET (32+ chars),# admin/user creds, LLM provider$ LLM_PROVIDER=ollama
3
Launch
$ bun dev→ localhost:3000# or: docker compose up -d
Need full configuration?
A copy-paste docker-compose.yml with every environment variable — auth, OIDC SSO, storage, AI/LLM, and seed connections.
Prefer a one-click deploy?
LibreDB Studio is an official Railway template, CapRover one-click app, and Dokploy marketplace template — and runs on Docker, Helm, npm, and every major PaaS and cloud.
Next: connect your first database
- 1 Log in and open Connections → New connection.
- 2 Pick your engine — PostgreSQL, MySQL, Oracle, SQL Server, SQLite, MongoDB, Redis, Couchbase, ClickHouse, or Apache Druid.
- 3 Enter host and credentials. Start with a dedicated read-only database account — least privilege first, write access when you actually need it. Databases behind a firewall connect over an SSH tunnel.
- 4 Deploying for a team? Define seed connections whose credentials resolve from environment variables at runtime — secrets stay in your secret manager, never in a config file.