db-studio: open-source database GUI runs nine engines from a single npx command

A solo developer in Istanbul has released db-studio, a free and open-source database studio that starts with one command, npx db-studio. According to the developer's announcement on dev.to, the project is licensed under Apache 2.0 and covers nine database engines, with the adapters, API, web interface, CLI and desktop app all built and maintained by a single engineer named Hüsam.

A local tool with no hosted account

The CLI is designed to be run from a project directory. db-studio looks for a DATABASE_URL in the project's .env file or the environment; if none is found, you paste a connection URL on the Connect page instead. The terminal then prints a local address where the interface runs, and no hosted account is needed.

Connection details stay on your machine, and the desktop app and CLI draw from the same list. Every browser tab holds its own active connection, which the developer says lets you work on several databases side by side. A desktop app is available for those who prefer a dedicated window.

Grid editing that behaves like a spreadsheet

The most recent release focuses on editing workflows in the data grid. You can select a range of cells, copy it together with headers, and paste data in from an external spreadsheet. Unsaved edits can be reviewed, individual cells reverted, and changes undone with Cmd/Ctrl+Z. When entering a value, you explicitly pick between NULL, empty text and the column's default. Rows can be copied out as JSON or as a SQL INSERT statement, or duplicated from a menu.

Capabilities depend on the engine, the developer notes. ClickHouse tables are read-only in the grid, for instance, while explicit mutations remain possible in the query editor. A saved connection can also be opened read-only where the engine supports it.

Nine engines, plus compatible databases

db-studio supports PostgreSQL, MySQL, SQL Server, MongoDB, SQLite, Redis, DuckDB, Oracle and ClickHouse. Databases such as MariaDB, CockroachDB, TiDB, Turso/libSQL and Cloudflare D1 can be reached through their corresponding supported engines.

The interface follows each database's data model: MongoDB presents collections and Redis presents key types, and the available operations differ from engine to engine.

Queries, schema diagrams and optional AI

The query editor includes syntax highlighting, autocomplete and saved queries, with results viewable as a table or as JSON. Import and export handle CSV, Excel and JSON. Relational databases get schema diagrams showing how tables relate to one another, and related records can be browsed through foreign keys.

AI assistance is turned off by default and runs on the user's own provider key. The developer positions it as a helper for writing, explaining, optimising or fixing queries.

The project is open to contributions and bug reports, and the developer is openly soliciting feedback on which tasks the tool should make easier.

Why it matters

Developers who touch more than one database usually accumulate a drawer full of clients, several of them commercial or tied to a cloud account. db-studio bundles that work into a single local tool with close to zero setup cost: if you have npx available, you can try it inside a project in seconds and discard it just as quickly. The Apache 2.0 license and the fact that connections never leave your machine will appeal to anyone reluctant to paste credentials into hosted services.

The obvious caveat is sustainability. This is a single-maintainer project spanning nine engines, so depth of support will vary and long-term upkeep rests on one person plus whatever contributors the call for bug reports attracts. Even so, the combination of one-command distribution, local-first connection handling and broad engine coverage makes it an easy tool to evaluate against heavier incumbents.