Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
A database client that runs in the browser from a single Node.js container. It connects to MySQL, MariaDB, PostgreSQL, CockroachDB, SQL Server, Oracle, SQLite, MongoDB, Redis, ClickHouse, Firebird and DuckDB, and offers a data grid with filters and editing, a table-structure editor, an ER diagram, a SQL editor with completion, and import and export of CSV, Excel, JSON and other formats. Saved connections, scripts and archives are kept in files under the data directory; the web login is set through environment variables, and connections can be preconfigured there too. The Docker image is the Community edition; a separate Premium image adds more engines and features.
Runs on a VPS from $6/mo (Kamatera 2GB, 2 GB RAM) · prices checked Nov 2026
Fits home hardware (62 MB measured idle, RAM only): Raspberry Pi 4 (4 GB) (arm64 untested), Raspberry Pi 5 (8 GB) (arm64 untested), Repurposed laptop (8 GB), Intel N100 mini PC (16 GB), AMD Ryzen mini PC (32 GB).
Pick DbGate when you want one browser-based client that covers relational and document databases together — PostgreSQL and MySQL next to MongoDB, Redis, SQLite or ClickHouse — and you would rather run a single container than a different admin tool per engine. It gives you a filterable data grid with inline editing and a SQL change preview, a schema editor, an ER diagram, a SQL editor with completion, and import and export to CSV, Excel, JSON and NDJSON. It is GPL-3.0 and ships as the Community image, a Node.js backend with a Svelte frontend; the same code also runs as a desktop app. Pick something else if you need a team-managed server with roles and an admin UI, because that is the separate Team Premium image, or if you only ever touch one engine and its own purpose-built tool is enough.
Paid link — we earn a commission if you shop through it.
Run these commands on your server:
# DbGate — Community edition image dbgate/dbgate pinned to 7.3.4; compose adapted from the Docker Hub example, with a sign-in set through LOGIN/PASSWORD and one preconfigured sample PostgreSQL 17.11 connection (documented CONNECTIONS variables) so the UI has a database to open
echo "DBGATE_PASSWORD=$(openssl rand -hex 16)" > .env
echo "SAMPLE_PG_PASSWORD=$(openssl rand -hex 16)" >> .env
cat > docker-compose.yml <<'EOF'
services:
sample-db:
image: postgres:17.11-alpine
restart: unless-stopped
environment:
POSTGRES_USER: sample
POSTGRES_PASSWORD: ${SAMPLE_PG_PASSWORD}
POSTGRES_DB: sample
healthcheck:
test: ["CMD-SHELL", "pg_isready -U sample -d sample"]
interval: 5s
timeout: 5s
retries: 20
volumes:
- sample-pg:/var/lib/postgresql/data
dbgate:
image: dbgate/dbgate:7.3.4
restart: unless-stopped
depends_on:
sample-db:
condition: service_healthy
ports:
- "3000:3000"
environment:
LOGIN: admin
PASSWORD: ${DBGATE_PASSWORD}
CONNECTIONS: sample
LABEL_sample: Sample PostgreSQL
SERVER_sample: sample-db
PORT_sample: 5432
USER_sample: sample
PASSWORD_sample: ${SAMPLE_PG_PASSWORD}
DATABASE_sample: sample
ENGINE_sample: postgres@dbgate-plugin-postgres
volumes:
- dbgate-data:/root/.dbgate
volumes:
sample-pg:
dbgate-data:
EOF
docker compose up -d
timeout 300 bash -c 'until curl -fsSL -o /dev/null http://localhost:3000/; do sleep 3; done'
# → http://SERVER_IP:3000 — the DbGate sign-in page; log in as admin with the password in .env (DBGATE_PASSWORD), then open the preconfigured Sample PostgreSQL connectionDbGate's Docker Hub page, environment-variable docs and pricing page flag these before you rely on it:
DbGate used 62 MB of RAM at idle on GCP e2-standard-2 · Ubuntu 26.04 LTS · Docker 29.9.3 (first boot, measured Nov 2026). We list a minimum of 512 MB.
The DbGate install snippet is marked verified on Ubuntu 26.04 (Nov 2026).