Get started
Running next to your database in about a minute
Studio is one container. Put it on the network the database already lives on, open the URL, and sign the team in. Nothing is installed on anyone's laptop.
-
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.
Pick an install channel
Docker
docker run -p 3000:3000 libredb/libredb-studio # zero-config first run — secrets generated at boot, printed once
npx
npx @libredb/studio # no Docker needed — binds to 127.0.0.1 by default
Helm
helm install studio ./charts/libredb-studio # also a certified chart in Rancher Partner Charts
Embed
npm i @libredb/studio # mount the editor inside the product that created the database
One-click templates for Railway, Dokploy, CapRover, DigitalOcean, Sealos and Fly.io, plus the Helm chart and its certified Rancher Partner Charts listing, are on the deploy page with the rest. Every channel ↗