DBPinball

Appearance

DBPinballA CLI-first database workspace for MySQL and PostgreSQL

Inspect databases from the terminal, or from a desktop app that shares the same Rust core and the same connection store.

Get started
CLI reference
Architecture

One core, two front ends

The Rust core owns connection storage, validation and inspection. The CLI and the Tauri desktop are thin adapters over it, so they cannot drift apart.

Credentials stay in the OS keyring

Passwords are stored in Keychain, Credential Manager or libsecret. The connection store holds metadata only and has no password field.

Safe concurrent edits

A cross-process lock and a monotonic revision stop the desktop and the CLI from silently overwriting each other's profiles.

Honest about limits

Safe Sync, the security policy milestone and several desktop pages are not available yet. The roadmap says exactly what is implemented and what is not.

What DBPinball is ​

DBPinball is a database workspace for developers and administrators who work with MySQL and PostgreSQL. It has two front ends over one Rust core:

  • a standalone CLI (dbpinball) for scripted and headless inspection;
  • a desktop application (Tauri + React) for interactive work.

Both read and write the same connection store, so a profile created in one appears in the other.

What is available today ​

CapabilityStatus
Connection vault (create, edit, test, delete)Available
Credential storage in the OS keyringAvailable
Database and table listingAvailable
Query execution in the desktop workspaceAvailable
dbpinball CLI (doctor, connections, schema inspect)Available
Shared connection store between desktop and CLIAvailable
Backup, restore and copy from the desktop UINot routed in the UI
Shared security policy and destination verification (M3)Planned
Safe Sync (M4 and later)Not available

See the roadmap for the full picture.

Where to go next ​

Released under the MIT License.

DBPinball