Setup guide

Answer a few questions and get a ready .env file. Nothing leaves your browser.

Where will it run?

CoolifyDocker host with a proxyLocal trial

Public domainBecomes https://dbloom.example.com. Must match the domain your proxy serves.Pin the domain (recommended; required for DBLoom accounts)Only trust my proxy network (recommended)

How do people sign in?

DBLoom accountsDatabase credentials

Users, second factors and saved connections live in DBLoom. Needs a server key.

Server keyMade in your browser, never sent anywhere.

My databases are on a private network (allow private addresses)Read-only: nobody can change data

.env

# Where users reach DBLoom (scheme and host, no path).
DBLOOM_PUBLIC_ORIGIN=https://dbloom.example.com

DBLOOM_LOGIN_MODE=account
# Keep a copy outside the server. Without it, TOTP secrets and recovery codes in a backup are unusable.
DBLOOM_SECRET_KEY=(click Generate key)

Generate a server key to finish the file.

Not sure what a line does? Every variable is explained in the reference. DBLoom has about a hundred settings, but everything except these lines has a sensible default.

Deploy it: Coolify, Docker Compose or another platform.
Open your domain. In account mode the first visit starts a setup wizard; print its token with docker exec CONTAINER node .output/cli/dbloom.mjs setup-token.

Setup guide

Next