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
- 02 Kubernetes
- 05 Package managers
- 03 OS & desktop packages
- 08 PaaS catalogs
- 03 Deploy recipes
- 01 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, 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.
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.
-
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
In the Dokploy template catalog.
-
Cloud
In the Kubero template catalog.
-
Cloud
A template in the Sealos App Store.
-
Container
A servapp in the Cosmos marketplace.
-
Container
Installable from Unraid’s Community Applications tab.
-
Container
In the TrueNAS SCALE community apps catalog.
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 deliberately ships no default credentials — you supply your own.
Cloud marketplaces
Provisioned from a cloud provider’s own marketplace.
-
Cloud
Provisioned straight from DigitalOcean’s marketplace.
The channel inventory, the update SLA per channel and the drift check that keeps them honest are documented in the repository. Read DISTRIBUTION.md ↗