Rust · GPUI · v0.7.7
An extensible, keyboard-first data platform. Twelve built-in drivers, a driver-neutral core, and anything else you need over the RPC driver protocol.
$ curl -fsSL https://raw.githubusercontent.com/0xErwin1/dbflux/main/scripts/install.sh | sudo bashPrefer no sudo? Append -s -- --prefix ~/.local to install under your home directory.
$ paru -S dbfluxAny AUR helper works. yay -S dbflux is equivalent.
$ sudo dpkg -i dbflux-linux-amd64.debSwap amd64 for arm64 on ARM machines. The .rpm installs the same way with dnf.
$ chmod +x dbflux-linux-amd64.AppImage && ./dbflux-linux-amd64.AppImageFully portable. Nothing is written outside your home directory.
$ nix profile install github:0xErwin1/dbfluxThe default package is a prebuilt binary. Use #dbflux-source to build from source instead.
The build is not signed with an Apple developer certificate. To skip the dialog: xattr -cr /Applications/DBFlux.app. Requires macOS 11 Big Sur or later.
The executable is not signed with a Windows code signing certificate. Requires Windows 10 or later on x86_64; ARM64 is not supported yet.
Nothing is installed and nothing is written outside the folder you extract into.
Built-in drivers
Capability matrix →Relational, document, key-value, time-series and object stores share one result grid, one chart engine and one audit log. External drivers register over the RPC protocol without a fork.
What you get
Completion, validation and dangerous-statement detection come from the driver, not a shared guess. A DELETE without a WHERE is caught before it runs.
Edit cells in place when the result maps cleanly back to one table, page through millions of rows by keyset, and copy any selection as a native query.
Turn any result into a chart, save it, and pin it to a dashboard alongside instance metrics from the same connection.
Run a command, a script or in-process Lua around connect and disconnect, with live output in the tasks panel and a failure policy you choose.
SSH tunnels, HTTP proxies and AWS SSO are first-class. Secrets live in the OS keyring, never in the profile file.
Queries, hooks, scripts and MCP calls all write to the same event log, with redaction and retention you control.
Keyboard-first
Every surface has a binding and a command-palette entry: open a connection, run a statement, jump to a table, pivot a result into a chart. The empty state tells you the four you need on day one.
Full keyboard reference →Governance
The MCP server classifies every operation — metadata, read, write, destructive, admin — and a policy engine decides per role and per connection. Write and destructive calls can sit behind human approval.
Audit
Events land in a local SQLite log with category, severity, actor and outcome. Query text is fingerprinted rather than stored, sensitive values are redacted, and the whole log exports to JSON or CSV.
Documentation
All guides →First launch, creating a connection, running queries, browsing results, charting and exporting.
SSH tunnels, proxies, AWS SSO and value sources for everything that is not a plain host and port.
Wire an AI client to DBFlux, then set the roles, policies and approvals that keep it inside the lines.