One command line for every database, and the APIs in front of them.

Technical teams often end up with a different tool for every database vendor, plus a spreadsheet, plus an API client, plus a folder of one-off scripts. BroadSQL replaces that with one command language: connect, query, move, load, export, script, and call the APIs in front of your data, the same way every time.

Latest release v5.2.4 (download it). Free for personal use. See the license and the source code.

Ships with drivers for H2, PostgreSQL, Apache Derby, HSQLDB, and SQLite. Any other JDBC-compatible database (Oracle, MySQL, SQL Server, MariaDB, DB2, and more) works by adding its driver. See technical requirements.

What BroadSQL lets you do

A small set of strong, repeatable operations, available the same way against every database or API you connect.

1

One command language, every database

Connect to H2, PostgreSQL, Derby, HSQLDB, SQLite, or any other JDBC-compatible database, and use the same commands and the same session, whichever vendor you're pointed at.

2

The same operation, every environment

Run a query on QA, then re-run it on PROD with / PROD, without retyping it or switching connections. Database Groups and Environments keep DEV, TEST, and PROD organized and unambiguous.

3

Move data out with PULL

PULL copies a query's results into a local H2 table, an Excel or OpenDocument tab, or a CSV, JSON, Markdown, or HTML file, all through one syntax instead of a different export tool per format.

4

Load data back in, safely

LOAD validates a CSV file against the target table, previews what will happen, and only writes once you authorize it, in one transaction, with parameter-bound statements rather than pasted-together SQL.

5

Automate recurring work

Save a query or a whole script under a name in the SQL Library and re-run it later, or drive several connections at once from a short JavaScript snippet (JS RUN/JS EVAL) instead of repeating the same click path.

6

Call the APIs in front of your data

Import an existing Bruno collection once, then browse and call its GET/HEAD endpoints, with whatever authentication it defines, from the same workbench you already use for databases. See Universal API Client.

Why not just use a GUI?

Graphical SQL clients are excellent for interactive exploration: browsing a schema, building one query, looking at one database.

BroadSQL earns its place once that work needs to be repeated, scripted, shared with a team, or applied consistently across systems and environments: exactly the part a point-and-click session doesn't preserve. It isn't a claim that GUIs are the wrong tool; it's a different job.

A good GUI is still the right tool for one-off exploration of a single database. BroadSQL is for the part of the job that repeats: the same check next week, the same extract in another environment, the same script run by someone else on the team.

See how BroadSQL measures up against a typical GUI client, or the full, tool-by-tool breakdown against usql, DBeaver, and DataGrip.

Who it's for

Built for people who work across many databases as a matter of routine, not for schema design or one-off exploration.

BroadSQL assumes you're comfortable with SQL and a terminal. That's a feature, not a gap: the more of the job you can express as a command, the more of it you can repeat, script, and hand off.

See the full picture, with the tasks and challenges behind each role, in Who BroadSQL is for.

Trust and control

A short list of things that are true about BroadSQL today, not aspirational claims.

No hidden AI

BroadSQL includes no AI functionality today, and does not send database data, SQL, metadata, credentials, or query results to an AI service. AI-assisted tools may be used to help build BroadSQL, but that's separate from the software you run. See AI and BroadSQL.

No phoning home

BroadSQL only talks to the databases and APIs you connect it to. It does not collect usage telemetry or contact any BroadSQL/UpAndCoding server during normal operation. See Security.

Encrypted, local credentials

Every saved connection, its URL and password, lives in an AES-encrypted local database, unlocked by one master password you choose. See Security.

Open, auditable core

The core of BroadSQL that parses your commands and talks to your databases is published openly, with its own test suite, at github.com/lico/broadsql-source. Read it yourself instead of taking it on faith.

Ready to try it?

Download the latest release, or read the getting started guide to connect your first database in a few minutes.