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.
Start here
Docker image — GHCR
Containerdocker run -p 3000:3000 ghcr.io/libredb/libredb-studio:latest The canonical image. Zero-config: the admin password is printed to the log on first run.
npm — @libredb/studio
Linux · macOS · Windowsnpx @libredb/studio No Docker needed. Node 24+; downloads the release server archive. Also the package you embed in your own product.
Helm chart
Kuberneteshelm install libredb oci://ghcr.io/libredb/charts/libredb-studio Published to the libredb.org repo, GHCR as OCI, and ArtifactHub. First-run credentials are printed to the pod log.
Homebrew tap
macOS · Linuxbrew trust libredb/tap && brew install libredb/tap/libredb-studio brew trust is required once on Homebrew 6+; run brew update first if the command is unknown.
- 02 Registries & releases
- 02 Containers
- 04 Kubernetes
- 06 Package managers
- 03 OS & desktop packages
- 15 PaaS catalogs
- 03 Deploy recipes
- 04 Cloud marketplaces
Registries & releases
The published artifacts every other channel is built from.
-
GitHub Releases ↗
autoLinux · macOS · Windows
Standalone tarballs plus the .deb, .rpm and snap assets every other channel repackages.
-
Linux · macOS · Windows
npx @libredb/studioNo Docker needed. Node 24+; downloads the release server archive. Also the package you embed in your own product.
Containers
One image, the fastest path from nothing to a running Studio.
-
Container
docker run -p 3000:3000 ghcr.io/libredb/libredb-studio:latestThe canonical image. Zero-config: the admin password is printed to the log on first run.
-
Docker Hub mirror ↗
autoContainer
docker run -p 3000:3000 libredb/libredb-studioA mirror for discoverability. GHCR above is the canonical registry.
Kubernetes
The published Helm chart and operator, on any cluster — including a certified partner listing.
-
Helm chart ↗
autoKubernetes
helm install libredb oci://ghcr.io/libredb/charts/libredb-studioPublished to the libredb.org repo, GHCR as OCI, and ArtifactHub. First-run credentials are printed to the pod log.
-
Kubernetes
A certified chart in Rancher Partner Charts, with a SUSE Partner Certification listing.
-
Kubernetes
The operator in the community catalogs of operatorhub.io and the OpenShift console. Community, not Red Hat certified, so the console lists it under Community.
-
Kubernetes
A chart of its own in the ZopDev repository, served from helm.zop.dev. Not a copy of the libredb.org chart.
Package managers
Install on your own machine with the manager you already use.
-
Homebrew tap ↗
automacOS · Linux
brew trust libredb/tap && brew install libredb/tap/libredb-studiobrew trust is required once on Homebrew 6+; run brew update first if the command is unknown.
-
Snap Store ↗
autoLinux
sudo snap install libredb-studioStable channel, amd64 and arm64. The admin password is printed to sudo snap logs libredb-studio.
-
winget ↗
autoWindows
winget install LibreDB.StudioPortable zip with a bundled Node.js runtime — then run libredb-studio.
-
Chocolatey ↗
autoWindows
choco install libredb-studioThe same standalone zip as winget, from the Chocolatey community repository.
-
Windows
scoop install extras/libredb-studioThe same standalone zip, from the Scoop Extras bucket (scoop bucket add extras first). The bucket updates itself from each release.
-
Linux
A signed Flatpak remote carrying org.libredb.Studio, repackaged from the official vendor build.
OS & desktop packages
A desktop application and native Linux packages, from the release assets.
-
Linux
A desktop wrapper shipped as release assets: AppImage and a GUI .deb, x64 and arm64.
-
Linux .deb / .rpm ↗
autoLinux
Native server packages, attached to every release.
-
Linux
The catalog AppImage Pool and Zap read. It resolves the latest release itself, so the listing follows every release without a submission.
PaaS catalogs
Listed in the catalog of a platform you already run — self-hosted or managed.
-
Cloud
A one-click template in Railway’s own catalog.
-
Cloud
Listed in CapRover’s official one-click apps.
-
Cloud
An opt-in second CapRover entry: a discovery companion reads the Docker socket and connects Studio to the databases CapRover runs. The plain entry stays socket-free.
-
Cloud
A community plugin, listed on Dokku’s community plugins page.
-
Cloud
In the Dokploy template catalog.
-
Cloud
In the Kubero template catalog.
-
Cloud
A template in the Sealos App Store.
-
Cloud
A servapp in the Cosmos marketplace.
-
Cloud
A template in the Railyard catalog. Railyard builds the Dockerfile from main at deploy time, so a deploy can carry commits no release has shipped yet.
-
Container
Installable from Unraid’s Community Applications tab.
-
Container
In the TrueNAS SCALE community apps catalog.
-
Container
In the CasaOS App Store; installs a container on your own device.
-
Container
The community-maintained app store for 1Panel, bumped by the store’s own Renovate.
-
Container
In the lissy93 Portainer templates aggregator, a third-party list rather than the official portainer/templates repository. It names the :latest image tag.
-
Linux
In the YunoHost app catalog. No container: it unpacks the standalone Linux tarball under systemd with its own Node 24.
Deploy recipes
A config file in the repository that a platform reads to deploy it for you.
-
Cloud
A fly.toml in the repository — fly launch reads it.
-
Cloud
A render.yaml Blueprint in the repository.
-
Cloud
A deploy button in the repository README. It prefills no password and no working secret: you set JWT_SECRET (32+ characters) in the deploy form, or the instance stops at boot; the admin password is generated on first run and printed to the Koyeb runtime log.
Cloud marketplaces
Provisioned from a cloud provider’s own marketplace.
-
Cloud
Provisioned straight from DigitalOcean’s marketplace.
-
Cloud
A free AMI product.
-
Cloud
A free (“Get It Now”) Azure Application solution template.
-
Kubernetes · Cloud
A free Terraform Kubernetes app, deployed from the Google Cloud console into your own GKE cluster.
The channel inventory, the update SLA per channel and the drift check that keeps them honest are documented in the repository. Read DISTRIBUTION.md ↗