SQLly vs gobang
gobang is a terminal database browser written in Rust: one small binary, vim-style keys, and MySQL, PostgreSQL and SQLite. It is MIT-licensed and has about 3,300 GitHub stars, but it hasn’t shipped a release since September 2021. SQLly is also written in Rust, but it is a desktop app, and the two answer different questions. This is terminal against desktop, and here’s the honest breakdown.
Last reviewed: November 2026
The short version
A desktop SQL workbench
One Rust codebase drawn on the GPU on macOS, Windows, and Linux. Thirty engines, IntelliSense that reads your data, layered safety guardrails, a grid that pivots and charts, and a full set of script-first admin tools. It needs a screen, and the download is 61 to 76 MB.
A keyboard-only browser for the terminal
A single binary of about 3.5 MB compressed that runs anywhere you have a shell, including over SSH. Browse databases and tables, filter records, and read columns, constraints, foreign keys and indexes with h/j/k/l. Still marked alpha, and dormant: the last release was v0.1.0-alpha.5 on 15 September 2021.
Feature by feature
SQLly’s column uses the same honest status badges as the features page and the docs. For gobang we list what its README, source and release assets show. Where a feature exists only on its unreleased main branch, we say so.
| Capability | SQLly | gobang |
|---|---|---|
| Interface | DesktopOne Rust codebase, rendered on the GPU (Metal, Direct3D, Vulkan). How it works | TerminalA full-screen TUI built on the Rust tui and crossterm crates. |
| Works over SSH or in tmux | NoNeeds a graphical session. It can reach remote databases through SSH tunnels, a bridge or a relay, but the app runs on your machine. | YesAnywhere a terminal runs. |
| Runs on macOS, Windows & Linux | YesmacOS is signed and notarized; Windows and Linux are a supported beta, on amd64 and arm64. | YesRelease binaries for x86_64 macOS, x86_64 and i686 Windows, x86_64 Linux (musl) and 32-bit ARM Linux. No Apple Silicon or arm64 Linux binary; cargo install builds for any target. |
| Download size | 61-76 MBmacOS dmg 65.6 MB, Windows x64 zip 60.9 MB, Linux x64 tarball 76.2 MB. | 3-3.6 MBRelease archives for alpha.5 range from 3.1 MB (Windows i686) to 3.6 MB (macOS and Linux x86_64). |
| Install | Installerdmg, zip or tarball from the download page, or the Mac App Store edition. | Package managersHomebrew tap, Scoop, nixpkgs, AUR (gobang-bin), NetBSD pkgsrc, cargo install, or a release binary on your PATH. |
| Free to use | Free tierTwo saved servers, one cloud account, and a reminder to pay about every five hours. Pricing | YesNo paid tier. |
| Open source | NoLifetime licenses carry a source-escrow promise if SQLly is ever discontinued. | YesMIT on GitHub. |
| Actively maintained | YesRegular releases. Changelog | NoLast release 15 Sep 2021, last code change Dec 2021, last commit (README) Jan 2023. 57 open issues. |
| MySQL, PostgreSQL, SQLite | YesPlus MariaDB and hosted compatibles such as Neon, Supabase and Aurora. Full list | YesThrough sqlx 0.5. |
| SQL Server, Azure SQL | YesAzure SQL (Entra sign-in in progress). | No |
| DuckDB, ClickHouse, Oracle, libSQL/Turso | YesNative drivers; DuckDB is bundled. Per-engine coverage | No |
| Redis | YesTyped key editing, Cluster and Sentinel, pub/sub, slow log; Valkey, KeyDB, DragonflyDB, ElastiCache and MemoryDB too. Redis | No |
| Adding connections | YesA connection dialog, plus import from DataGrip, DBeaver, pgAdmin, TablePlus, Navicat and more. Compatibility | PartialEdit config.toml by hand. |
| Password storage | YesPasswords stay in the OS keychain; connection files never hold them. | PartialAn optional password field in plain text in config.toml. |
| SSH tunnels | YesSSH hops, SOCKS and HTTP proxies, and Kubernetes. Engine docs | NoNo tunnel settings in the config; run gobang on the server or forward a port yourself. |
| Keyboard-only, vim-style navigation | PartialFull keyboard shortcuts and multi-cursor editing, but no vim mode across the app. | Yesh/j/k/l, g/G, / to filter, y to copy a cell. Custom key bindings exist on main only. |
| Browse tables & structure | YesObject tree, designers and Edit Structure. Designers | YesRecords, columns, constraints, foreign keys and indexes tabs, with a filter over records. |
| SQL editor | YesParameters, templates, multi-cursor, split views, folding, AI ghost text; a 0.5 MB script edits at about 5 ms a keystroke. | PartialAn SQL tab was merged in October 2021 but has never been in a release; you’d build main with Cargo to get it. The README still lists it as a TODO. |
| IntelliSense | YesAlias- and scope-aware, JOIN ON from foreign keys, real column values in WHERE. IntelliSense |
PartialCompletes from a fixed list of 12 keywords such as SELECT, WHERE and LIMIT. |
| Edit table data | YesA row editor generated from the table’s own metadata. Row editor | NoThe grid is read-only; on main you can type an UPDATE in the SQL tab. |
| Large results | YesStreams and spills to disk past 50,000 rows or 64 MiB; memory stays flat at 50 million rows. Streaming | -Records load page by page; we didn’t measure it. |
| Pivot, charts & result diff | YesPivot, charts, conditional formatting, computed columns, and diffs on any result. Pivot | No |
| Export data | YesCSV, JSON, Excel with live formulas, SQL, and more. Export | PartialCopy a cell or a selected block of cells. |
| ER diagrams, plans, schema compare | YesRelationship Graph, schema and data compare; query plans on nine engines are in progress. | No |
| Session & activity monitoring | YesActivity Monitor with blocking chains, top queries, Server Dashboard. Activity Monitor | No |
| Guardrails in the editor | YesSELECT-only connections, no UPDATE/DELETE without WHERE, auto-rollback, tenant checks. Safety |
No |
| AI & MCP for agents | YesLocal or opt-in cloud models; sqlly-cli mcp gives agents read-only SELECT and turns writes into proposals. Read-only enforcement |
No |
A dash means we couldn’t confirm it from gobang’s own materials - check its repository for the current state.
Where SQLly is different
gobang is a fast way to look at a table from a shell. SQLly is where you write, check and analyse the SQL.
Thirty engines, not three
SQL Server, Azure SQL, MariaDB, DuckDB, ClickHouse, Oracle, libSQL/Turso and Redis sit beside MySQL, PostgreSQL and SQLite, and each engine gets its own plans, dashboards and compare tools where it supports them.
Supported databases →Autocomplete that knows your data
gobang offers 12 fixed keywords. SQLly tracks aliases and scope, writes a join’s ON clause from real foreign keys, pulls a column’s distinct values into a WHERE clause, and underlines a GROUP BY mistake as you type.
A grid that does analysis
Pivot, charts, conditional formatting, computed columns, result diffs, and Excel export with a pivot sheet. A one-line SQL comment can save the layout so it travels with the query.
SQLly directives →Guardrails on your own queries
Read-only connections that refuse file-reading and shell-escape tricks, a hard stop on UPDATE/DELETE with no WHERE, auto-wrapped transactions, and prod painted red - inherited down your client, project, and environment tree.
DBA tools under one menu
Activity Monitor, Query Store and pg_stat_statements, SQL Agent, schema and data compare, an index analyzer, test data, and backup and restore. Anything destructive opens as SQL in a tab for you to read before it runs.
Tools →Secrets out of config files
Connections are plain files you can sync or diff, but passwords live in the OS keychain, not in a TOML file next to them. SSH tunnels, proxies and TLS modes are part of the connection.
TLS →When gobang is the better choice
gobang, or a terminal client like it, is probably the better fit if:
- You’re SSH’d into a box. gobang runs inside the session, next to the database, with nothing to forward. SQLly needs a desktop.
- You live in tmux and vim keys. Everything in gobang is on the home row, and it fits in a pane beside your editor.
- Size matters. A 3.5 MB archive with one binary in it, against SQLly’s 61-76 MB download.
- You only need a quick look. Check that a migration ran, peek at a row, read a table’s indexes. You don’t need a workbench for that.
- It has to be free and open source. gobang is MIT with no paid tier. SQLly’s source is closed, and its free tier isn’t available inside organizations with more than 100 employees.
- You’re on an Intel Mac or a 32-bit ARM board. gobang ships binaries for both; SQLly needs Apple Silicon on the Mac and amd64 or arm64 elsewhere.
The honest caveat in the other direction: gobang has had no release since September 2021, its SQL editor never shipped in one, and an open issue from April 2024 asks for a release with updated dependencies. Treat it as a finished-as-is tool, not one that will grow.
Questions
Is gobang still maintained?
It looks dormant. The newest release, v0.1.0-alpha.5, came out on 15 September 2021, the last code change landed in December 2021, and the last commit of any kind was a README update in January 2023. The README still says gobang is in alpha. It is MIT-licensed, so anyone can fork it, and it still has about 3,300 stars on GitHub.
Which databases do SQLly and gobang support?
gobang connects to MySQL, PostgreSQL and SQLite. SQLly connects to those three plus SQL Server, Azure SQL, MariaDB, DuckDB, ClickHouse, Oracle Database, libSQL/Turso and Redis, along with documented wire-compatible services such as CockroachDB, Neon, Supabase and Valkey - 30 engines in all.
Does SQLly have a terminal UI like gobang?
No. SQLly is a desktop app drawn on the GPU, so it needs a graphical session. Its command-line tool, sqlly-cli, runs an MCP server for AI agents, but it is not a full-screen terminal browser. If you need to browse tables from inside an SSH session or a tmux pane, gobang or another terminal client is the right kind of tool.
Other comparisons
Keep both
Plenty of people keep a terminal client for SSH sessions and a desktop app for real work. SQLly is free on macOS, Windows, and Linux, with no account required.