// sqlly vs whodb

SQLly vs WhoDB

WhoDB describes itself as a lightweight, self-hosted workspace for your databases: a Go server you start with one docker run and open in a browser, with desktop apps and a terminal UI on the side. It covers 18 database types in its free Community edition, MongoDB and Elasticsearch included. SQLly is a native desktop app that goes deep on SQL. They solve different problems, so here’s the honest breakdown.

Last reviewed: November 2026

The short version

SQLly

A deep SQL workbench on your desktop

One Rust codebase drawn on the GPU on macOS, Windows, and Linux. Thirty engines including SQL Server and Oracle, IntelliSense that reads your data, results that stream to disk, layered guardrails, plans, compare, and a full set of script-first admin tools.

WhoDB

A free browser client you host once

Apache 2.0, about 5,000 GitHub stars, and a release most weeks (0.138.0 shipped on 28 October 2026). Run it in Docker and everyone on the network opens it in a browser. A spreadsheet-style grid, a schema graph, a query scratchpad, imports, mock data, AI chat, a CLI with an MCP server, and an interface translated into more than 60 languages.

Feature by feature

SQLly’s column uses the same honest status badges as the features page and the docs. For WhoDB we list what its own README, documentation, release assets and website state for the free Community edition.

Feature comparison of SQLly and WhoDB
Capability SQLly WhoDB
How the app is built NativeOne Rust codebase, rendered on the GPU (Metal, Direct3D, Vulkan), no browser engine. How it works WebA Go backend serving a React and TypeScript front end. The desktop app wraps the same front end with Wails.
Use it from a browser, hosted for a team NoDesktop only. The browser preview at sqlly.app/app is a demo. Yesdocker run -p 8080:8080 clidey/whodb, then open localhost:8080. The image is about 73 MB compressed on amd64.
Desktop apps YesmacOS is signed and notarized; Windows and Linux are a supported beta, on amd64 and arm64. Mac App Store edition too. YesMac App Store, Microsoft Store and Snap, plus direct downloads on GitHub.
Intel Macs NoApple Silicon only. YesIts release workflow builds a universal Mac app.
Download size 65.6 MBmacOS dmg. Windows x64 zip 60.9 MB, Linux x64 tarball 76.2 MB. 139.4 MBmacOS dmg on GitHub (83.1 MB on the Mac App Store). Windows exe 132.9 MB, Linux amd64 server binary 136.8 MB, both uncompressed.
Free to use Free tierTwo saved servers, one cloud account, and a reminder to pay about every five hours. Pricing YesCommunity is free at any company size. The separate WhoDB Platform runs $20 to $200 per member per month.
Open source NoLifetime licenses carry a source-escrow promise if SQLly is ever discontinued. YesCommunity is Apache 2.0. Enterprise code lives in a separate private repository.
PostgreSQL, MySQL, MariaDB, SQLite YesPlus hosted compatibles such as CockroachDB, Neon, Supabase and Aurora. Full list YesPlus CockroachDB, YugabyteDB, QuestDB and TiDB.
SQL Server & Azure SQL YesIncluding Extended Events and SQL Agent; Entra sign-in is in progress. NoNot in Community. Listed as an integration of the commercial Platform.
Oracle, libSQL/Turso YesNative drivers. Per-engine coverage NoOracle is listed for the Platform only; libSQL isn’t listed.
DuckDB & ClickHouse YesDuckDB is bundled; ClickHouse gets plans, dashboard, activity monitor and compare. YesIts docs note DuckDB isn’t built for every architecture.
Redis YesTyped key editing, Cluster and Sentinel, ACLs, pub/sub, profiler, memory analyzer, slow log; Valkey, KeyDB, DragonflyDB, ElastiCache and MemoryDB too. Redis YesRedis, Valkey and Dragonfly, plus Memcached.
MongoDB & Elasticsearch No YesMongoDB and FerretDB, Elasticsearch and OpenSearch.
SSH tunnels YesSSH hops, SOCKS and HTTP proxies, and Kubernetes. Engine docs PartialBuilt into the CLI. The web login has no SSH option; its docs say to set up a tunnel first.
IntelliSense YesAlias- and scope-aware, JOIN ON from foreign keys, real column values in WHERE, GROUP BY mistakes flagged. IntelliSense PartialTable, column and keyword autocomplete in a multi-cell scratchpad with history.
Edit table data YesA row editor generated from the table’s own metadata. Row editor YesInline editing, add-row dialog, batch delete, and a visual WHERE builder.
Large result sets YesStreams rows and spills to disk past 50,000 rows or 64 MiB; memory stays flat at 50 million rows. Streaming PagedThe grid pages through rows with a configurable page size.
Pivot, charts & result diff YesPivot, charts, conditional formatting, computed columns and diffs on any result. Pivot NoIts docs suggest exporting to Excel for pivots and charts.
Import & export data YesCSV, JSON, Excel with live formulas and a pivot sheet, SQL, and more. Export YesExport CSV, Excel or NDJSON; import CSV, Excel or a SQL script, up to 50 MB and 100,000 rows per file.
Test data generation YesTest data generator under Tools. Tools YesMock data from the grid, up to 200 rows per run, with foreign-key variety.
ER diagrams YesExport to SVG, Mermaid or DBML. Relationship Graph YesAn interactive schema graph of tables and relationships.
Execution plan viewer In progressPlain-language findings, tree and diagram across nine engines. Query plans PartialThe CLI runs the database’s own EXPLAIN; in the web app you type EXPLAIN into the scratchpad.
Schema & data compare YesRisk-graded schema diffs across engines, with sync and rollback scripts, plus data compare. Schema Compare PartialSchema metadata diff in the CLI and terminal UI.
Session & activity monitoring YesActivity Monitor with blocking chains, top queries and waits, Server Dashboard, Query Insights. Activity Monitor -We couldn’t find a monitor; its DBA guide has you query pg_stat_activity yourself.
Import connections from other tools YesDataGrip, DBeaver, pgAdmin, Azure Data Studio, DbGate, TablePlus, Navicat and Redis Insight. Compatibility -Couldn’t confirm. Saved profiles can come from environment variables.
Guardrails in the editor YesSELECT-only connections, no UPDATE/DELETE without WHERE, auto-rollback, tenant checks, prod painted red. Safety PartialAsks for confirmation before destructive SQL in the scratchpad.
AI chat about your schema YesLocal models (Ollama, MLX), your own endpoint, or opt-in cloud providers; no default provider. On-device AI YesOllama and LM Studio locally, or OpenAI, Anthropic, Gemini and OpenAI-compatible services with your key. Writes need confirmation.
MCP server for AI agents YesSchema tools and a read-only SELECT that is always rolled back; writes come back to you as proposals; production refused. How reads are kept read-only Yeswhodb mcp serve: native read-only transactions for reads, confirmed writes by default, with --read-only and --allow-write modes.
Terminal UI Nosqlly-cli exists, but there’s no full-screen terminal client. YesA Bubble Tea terminal UI with a table browser, SQL editor and AI chat.
Interface languages 10English, Spanish, Simplified and Traditional Chinese, Japanese, Korean, German, French, Brazilian Portuguese and Russian. 60+Its locale files carry more than 60 languages.

A dash means we couldn’t confirm it from WhoDB’s own materials - check its repository for the current state. WhoDB’s binaries are uncompressed and SQLly’s figures are compressed archives, so the size row isn’t a like-for-like contest.

Where SQLly is different

WhoDB is built to be the easiest way to look at a database from any browser. SQLly is built for the person who writes SQL all day.

SQL Server and Oracle without a sales call

WhoDB Community doesn’t connect to SQL Server, Azure SQL or Oracle; those sit with its commercial Platform. SQLly connects to all three, with SQL Server’s Extended Events, SQL Agent and Query Store in the same app.

Engines →

Autocomplete that knows your data

SQLly can pull a column’s real distinct values into a WHERE clause, write a join’s ON clause from actual foreign keys, understand “last Tuesday”, and underline a GROUP BY mistake as you type. A half-megabyte script still edits at about 5 ms a keystroke.

IntelliSense →

Results that don’t stop at a page

SQLly streams rows and spills to disk, so fifty million rows use about as much memory as fifty. On top sit pivots, charts, conditional formatting, computed columns, result diffs and Excel export with live formulas.

Spill-to-disk results →

Guardrails that inherit

Read-only connections that refuse file-reading and shell-escape tricks, a hard stop on UPDATE/DELETE with no WHERE, auto-wrapped transactions and an optional AI review, set once on a client, project or environment and inherited by every connection below it.

Safety & guardrails →

A DBA’s toolbox

Activity Monitor, Server Dashboard, Query Insights, an index analyzer, disk usage, backup and restore as scripts, risk-graded schema compare with rollback scripts, data compare, and cross-engine Data Transfer with type mapping.

Tools →

Nothing to host

SQLly is a desktop app: no server to patch, no session key to keep, no port to put behind a proxy. Passwords live in your OS keychain and everything else is plain files you can sync with any tool.

Download →

When WhoDB is the better choice

WhoDB is probably the better fit if:

  • You want one install for a whole team. Put WhoDB on a server and anyone with a browser can use it, including on a Chromebook or a locked-down laptop. SQLly has to be installed on each machine.
  • You need MongoDB, Elasticsearch or Memcached. WhoDB Community connects to all three; SQLly connects to none of them.
  • Open source, or free at any company size, is a requirement. WhoDB Community is Apache 2.0. 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, a Raspberry Pi or RISC-V. WhoDB ships a universal Mac app and server binaries for armv6, armv7 and riscv64. SQLly needs Apple Silicon on the Mac and amd64 or arm64 elsewhere.
  • You live in a terminal. WhoDB’s CLI has a full terminal UI, cloud discovery for AWS, Azure and GCP, and scriptable JSON and CSV output.
  • You want the interface in your language. WhoDB’s UI is translated into more than 60 languages; SQLly’s is in ten.
  • You want an agent to change data after you approve it. WhoDB’s MCP server and AI chat can run writes once you confirm them. SQLly’s agents only read; every write is a proposal you run yourself.

Two things to know before you pick WhoDB: its web UI turns on anonymous usage data, including session replay, by default and shows a banner to switch it off; and the whodb.com site now mostly sells the commercial Platform, so check the GitHub README for what Community includes.

Questions

Is WhoDB free?

WhoDB Community, the version on GitHub, is free and open source under the Apache 2.0 license, and you can self-host it at any company size. WhoDB Platform is a separate commercial product, offered as WhoDB Cloud or a managed private deployment, priced per member: Free for 2 members, Start at $20 per member per month, Pro at $200 per member per month, and Enterprise on request. SQLly is free for hobbyists, with a $100 SQLly 1.x license and a $200 Lifetime license for everyone else.

Which databases do SQLly and WhoDB support?

Both connect to PostgreSQL, MySQL, MariaDB, SQLite, DuckDB, ClickHouse and Redis, plus compatibles such as CockroachDB, Valkey and DragonflyDB. WhoDB Community adds MongoDB, FerretDB, Elasticsearch, OpenSearch and Memcached. SQLly adds SQL Server, Azure SQL, Oracle Database and libSQL/Turso - 30 engines in all. WhoDB lists SQL Server, Oracle, Snowflake and BigQuery for its commercial Platform, not for Community.

Is WhoDB a desktop app or a web app?

Both. WhoDB is a Go server with a React front end: you run it with Docker or as a single binary and open it in a browser, or install the Wails desktop app from the Mac App Store, the Microsoft Store or Snap, which shows the same interface in the system web view. There is also a terminal UI. SQLly is a native desktop app drawn on the GPU with no browser engine; its browser preview at sqlly.app/app is a demo, not a way to host it for a team.

Can AI agents use SQLly or WhoDB over MCP?

Both ship an MCP server. WhoDB’s whodb mcp serve runs reads in native read-only transactions and, by default, lets an agent write after you confirm; --read-only blocks writes and --allow-write skips the confirmation. SQLly’s sqlly-cli mcp lets an agent list connections, read schemas and run a single SELECT inside a read-only transaction that is always rolled back; it never executes a write itself - it sends the statement to SQLly as a proposal you confirm or decline, and production connections are refused.

// try it yourself

Point both at the same database

The quickest way to choose is to run your own queries in each. WhoDB is one docker run away; SQLly is free on macOS, Windows, and Linux, with no account required.