VeloxDB: open-source Rust and Tauri database admin tool for six engines on Linux

A new open-source database administration client named VeloxDB has arrived for Linux, packaging support for six different database engines into a single desktop application. According to a post on dev.to, the tool is written in Rust, uses the Tauri 2 framework for its interface, and ships as .deb and .AppImage packages for both x64 and ARM64 machines.

Six engines under one roof

VeloxDB handles PostgreSQL, MySQL, MongoDB, Redis, SQLite and DuckDB, a mix spanning relational servers, a document store, a key-value data store and an embedded analytical engine. The dev.to post also notes that wire-compatible managed services, including Supabase, PlanetScale and Atlas, can be used through the app, since they accept the same protocols as the engines they are built on.

Connections start with a URI

Instead of walking users through connection forms, VeloxDB lets them paste a standard connection string such as postgresql://, mysql://, redis://, mongodb(+srv):// or sqlite://. The application then works out the engine, host, port and credentials on its own. For developers who keep connection strings in password managers or internal documentation, this reduces setup to a single copy-paste and removes a common source of typos.

Editing and design tools

The feature set described on dev.to includes:

• Schema-aware SQL autocomplete while writing queries
• A visual ER diagram designer with drag-and-drop table editing, generated migrations, and exports to SQL, PNG or PDF
• SSH tunneling for reaching databases that sit behind firewalls
• SSL/TLS support for encrypted connections

For engines without a fixed schema, the tool offers an inferred schema view. MongoDB collections and Redis keys get a reconstructed structure even though neither system enforces one natively, which should make exploratory work on NoSQL data less of a guessing game.

A small footprint

Because VeloxDB is built on Tauri rather than Electron, the download comes in at 17–30MB and memory use stays around 50MB, according to the dev.to post. The project also states that there is no telemetry and that all processing happens locally, a relevant detail for an application whose job is to hold credentials to production databases.

Why it matters

Database GUI clients usually fall into two camps: dedicated tools such as pgAdmin or MySQL Workbench that serve one engine deeply, or cross-platform generalists like DBeaver that carry the weight of a Java runtime. A native Rust application covering six engines, including DuckDB, which is still uncommon in admin clients, while staying near 50MB of RAM gives Linux users a genuine middle path. The ARM64 build extends that to ARM servers and single-board development setups, a segment where Electron-based tools often struggle.

The MIT licence and the no-telemetry stance also align with what many teams now expect from developer tooling, and the URI-first connection flow respects how connection details are actually stored in practice. The usual caveat for a young open-source project applies: per-engine depth may not yet rival tools focused on a single database, and the dev.to post makes no claim that it does. Even so, as a lightweight, local-first option for juggling several databases from one window, VeloxDB looks like a project worth watching.