Engines as images
Engine binaries as images. Install in seconds, run anywhere.
dbpod engine install postgres@17<open-source database cli />
dbpod runs real MySQL & PostgreSQL engines as project-local instances — installed like images, run detached, cleaned like containers. Zero global pollution.
curl -fsSL https://dbpod.io/install.sh | sh$ dbpod engine install mysql@8.0$ dbpod run --name dev --engine mysql@8.0$ dbpod exec devFull lifecycle: install → run → query → inspect → stop. Re-recordable with vhs; scripted in-repo.
mental model
Every concept maps one-to-one. No new vocabulary, no new workflow.
imageengine versiondbpod engine install mysql@8.0 — the series resolves to the latest known patch (8.0.46).containerinstancedbpod run --name dev --engine mysql@8.0 — detached, ready when the prompt returns.volumeproject datadirAll state lives in ./.dbpod/ — data, logs, socket, pid. Delete the directory, the database is gone.docker images / rmi / pullsame-named commandsDocker-compatible commands ship as hidden aliases. Docker users already know dbpod.capabilities
One static binary. No system services, no /usr/local litter, no root.
Engine binaries as images. Install in seconds, run anywhere.
dbpod engine install postgres@17Your data lives in your project. ./.dbpod is the whole story.
ls ./.dbpod/dev/Detached like a daemon, clean like a container.
dbpod run --rm --name ci --engine postgres@17MySQL and PostgreSQL built in. MariaDB, Percona, MongoDB via one YAML file.
dbpod registry add ./mongodb.yamlEvery binary in the distribution, one command away.
dbpod exec dev mysqldump --helpOne binary. macOS, Linux, Windows.
dbpod engine ls --allengines
Builtin engines ship with the binary. Community engines come from thedbpod-ext registry — adding one touches zero lines of main code. How extending works →
Read the source, file issues, or add your own engine. Start in under a minute: