Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
Self-host WhoDB
updated Nov 2026deployed by usprices checked · Jul 2026Install verified on Ubuntu 26.04 · Nov 2026 · how we test
We earn commissions when you shop through the links below. Full disclosure →
A lightweight database workspace that runs in the browser from one Go container. You enter the connection details of a PostgreSQL, MySQL, MariaDB, SQLite, MongoDB, Redis, ClickHouse, Elasticsearch or other supported database, then browse tables in a spreadsheet-style grid with filtering and inline editing, view the schema as a relationship graph, run queries in a scratchpad, import and export data and generate mock data. Optional AI chat can use Ollama, LM Studio, OpenAI or Anthropic. It has no user accounts of its own: login sessions, holding the database credentials encrypted with AES-256-GCM, are kept in a SQLite file in the data directory.
Pick WhoDB when you want a small browser-based database workspace with nothing to configure on the server: one container, no database of its own, and a login form that takes the connection details of whatever you point it at. It covers the usual SQL engines plus MongoDB, Redis, ClickHouse and Elasticsearch, with a grid you can edit inline, a graph of table relationships, a multi-cell query scratchpad, import and export, and optional AI chat against a local or hosted model. It is Apache-2.0 and written in Go with a React frontend. Pick something else if you need per-user accounts or roles on the WhoDB side: the Community edition has none, and SSO and fine-grained access controls belong to the commercial WhoDB Platform.
What you need
Any VPS with at least 256 MB of RAM
A domain you control — most self-hosted setups need HTTPS in front of them
Paid link — we earn a commission if you shop through it.
Install
Run these commands on your server:
# WhoDB — Community edition, image clidey/whodb pinned to 0.138.0; compose adapted from the project's Docker Compose example, with the session encryption key generated into .env as the docs recommend (no database included: you enter connection details in the UI)echo "WHODB_ENCRYPTION_KEY=$(openssl rand -hex 32)" > .envcat > docker-compose.yml <<'EOF'services: whodb: image: clidey/whodb:0.138.0 restart: unless-stopped ports: - "8080:8080" environment: WHODB_LOG_LEVEL: info WHODB_ENCRYPTION_KEY: ${WHODB_ENCRYPTION_KEY} volumes: - whodb-data:/datavolumes: whodb-data:EOFdocker compose up -dtimeout 180 bash -c 'until curl -fsSL -o /dev/null http://localhost:8080/health; do sleep 3; done'# → http://SERVER_IP:8080 — the WhoDB login screen; there is no WhoDB account, you pick a database type and enter that database's host, user and password
WhoDB's README and installation docs flag these before you rely on it:
non-negotiableThere is no sign-in to WhoDB itself in the Community edition. Anyone who can reach port 8080 gets the login form and can ask the server to connect to any database host it can reach. Keep the port on a trusted network or behind your own authenticating reverse proxy.
non-negotiableIf you preload connection profiles with WHODB_POSTGRES-style variables, the docs warn that in the Community edition they are shared with everyone who can reach the instance: a visitor can pick a profile and connect with its stored password. WHODB_DISABLE_CREDENTIAL_FORM=true hides the manual form but adds no authentication. Our snippet defines no profiles.
non-negotiableLogin sessions hold your database credentials, encrypted with AES-256-GCM in a SQLite file under /data. Set a stable WHODB_ENCRYPTION_KEY (our snippet generates one into .env) and mount /data; changing or losing the key logs everyone out. Keep .env out of the same backup as the volume if you want the encryption to mean anything.
non-negotiableBehind an HTTPS reverse proxy set WHODB_SECURE=true so the session cookie is marked Secure; the docs say WhoDB does not infer HTTPS from proxy headers, and setting it on plain HTTP breaks the cookie. The snippet serves plain HTTP on 8080 and leaves it unset.
non-negotiableFrom inside the container localhost is the WhoDB container, not your server. Use the Compose service name for a database in the same stack. For one on the host, host.docker.internal resolves on Linux only if you add extra_hosts: ["host.docker.internal:host-gateway"], which the snippet does not set. The snippet ships no database, so you must supply one.
non-negotiableReleases are frequent (0.135.0 on 2026-10-15 to 0.138.0 on 2026-10-28 on Docker Hub), so pin the tag and read the release notes before bumping it. Telemetry is partly on by default: per the 0.138.0 source, the server sends an anonymous install heartbeat to PostHog at start and every 24 hours, and the Settings toggle does not stop it; only WHODB_HEARTBEAT_DISABLED=true does, and the snippet does not set it. Product analytics stay off until a user accepts the consent banner. WHODB_DISABLE_UPDATE_CHECK=true turns off release-availability checks.