db-manager dev

MySQL · MariaDB · PostgreSQL · SQLite · MongoDB · TiDB · Apache Doris

Six engines, one desktop client, and the tools that actually do the work

Browse and edit data, design tables, export a whole database, run a .sql file statement by statement, generate test data, compare two databases, turn a table into code — and keep a log of every statement the app runs. Connections, favourites and logs stay on this machine: no account, no telemetry, no cloud.

Download the latest release Source on GitHub See the screens

Screens

Six pages of the app, playing by themselves — hover to pause, or jump with the thumbnails below.

Every screen

What is in the box

Every tool is built on the same driver contract, so it is offered when the engine can serve it — an entry point that would fail is not drawn at all.

Engines

The driver layer does not assume a relational model, so a document engine goes through the same contract — and an entry point the engine cannot serve is simply not drawn.

On the roadmap Oracle and SQL Server: the dialect and the placeholder are already in the tree, the DSN and the catalogue queries are not — so they stay off the menu until they are.

Download

Every release is built by CI on three runners and attached to the release:

Checksums

Each release carries a checksums.txt next to the downloads: sha256sum -c checksums.txt

Build from source

Go 1.24+, Node 20+, the Wails CLI 2.16 and just. `just release` compiles the current platform into release/ with a checksums file.

Read the build instructions

Release notes

Each release body is rendered from the annotated tag and the Conventional Commit subjects since the previous one — the commit subjects are the release notes.

Where your data lives

Connections, favourites, saved query files, the tree layout, the window state, the encryption key and the change log all live in one data folder — %APPDATA%/db-manager on Windows, the usual config folder on macOS and Linux.