DBX

DBX is an open-source database client maintained in the t8y2/dbx project. It provides a graphical workspace for querying, browsing and editing databases, with native Rust/Tauri desktop builds. It suits developers, database administrators and analysts who work across relational, document, key-value and other database systems.

Query and inspect data

DBX supports engines including MySQL, PostgreSQL, SQLite, SQL Server, Oracle, Redis, MongoDB, DuckDB and ClickHouse, with additional engines available through its driver system. Supported capabilities vary by engine and driver; supporting a connection does not mean every database exposes identical editing, schema or transaction features.

The SQL editor provides dialect-aware completion, formatting, saved queries and execution history. Browse schemas and objects, inspect execution plans, edit table structures and explore entity relationships. Data grids offer filtering, inline editing, column navigation and exports including CSV, JSON, Markdown, Excel and INSERT statements. Import and data-transfer tools support moving data between suitable sources and destinations.

Installation and first connection

Install the macOS package with brew install --cask dbx, or obtain the matching official DMG for Apple Silicon or Intel and copy DBX into Applications. Open DBX, choose New Connection, select your database engine and provide its host, port, database and authentication details. For a local database file, select an appropriate SQLite or DuckDB connection instead. Test the connection before opening the query workspace.

A database service, reachable network endpoint or local database file is separate from this client. Supply credentials with the privileges needed for your task, including any database-specific TLS certificates or authentication settings. SSH tunnels support passwords, keys and supported ProxyCommand configurations; the required network route and any external proxy command must also be available. Installing DBX does not create a database server or grant access to an existing database.

Drivers and requirements

Official desktop releases cover macOS, Windows and Linux; Web/Docker deployments and a separately distributed MCP server are also available. The macOS release contains distinct arm64 and x64 disk images. This Cask has no declared extra formula dependency. The 0.6.35 Apple Silicon DMG is 39,037,419 bytes; this is the installer transfer size, excluding installed data, optional drivers and later downloads.

The native desktop application does not bundle Chromium and does not require a blanket Java installation for its core operation. Additional database support can require downloadable driver packages or engine-specific components; follow the selected driver's instructions rather than assuming all connections are dependency-free. The release configuration does not state a specific minimum macOS version, RAM or disk-space requirement, so check current platform compatibility before deploying on an older system.

AI, extensions and database changes

The optional SQL assistant supports configured providers such as Claude, OpenAI and compatible or local endpoints. Provider accounts, API credentials, usage charges and local model requirements are separate from DBX. Review generated SQL and the data sent to a provider before using it with sensitive databases. An AI suggestion is not a guarantee of correctness or safe execution.

Plugins and driver packages extend functionality and may run their own components. Review their source, permissions and dependencies. Optional MCP access is configured separately from ordinary desktop use, with connection allowlists and read-only, data read/write or full-access policies. The desktop installation alone does not install the separately distributed MCP executable.

Editing cells, importing data, transferring structures, executing SQL or clearing tables can change or delete real database data. Use appropriate database permissions, backups and transactions where supported; interface confirmations do not replace database access control. DBX encrypts stored connection, plugin, AI and tunnel credentials, and desktop builds use the platform credential store, including macOS Keychain. Keep backups and exported connection configurations protected.

Cost, accounts and license

The project is distributed under Apache-2.0 and its desktop client is available without buying a proprietary client license. Basic local client operation does not require a hosted DBX subscription account; authentication belongs to the databases and optional services you configure. Database products, cloud hosting, AI providers and third-party extensions can have their own fees and license terms. A self-hosted Web instance may require its configured login password.

The illustration is an official light-theme Mac interface example showing database connections, a PostgreSQL SQL editor and an AI assistant. Its Chinese interface is the publisher's example and it is not a newly captured 0.6.35 screen.

Sources: Official project and installation guide, DBX documentation, Official releases, Apache-2.0 license.