Tablio and SQLly: a 20 MB Tauri client against a deep workbench
Tablio is a free MIT Tauri client with Cassandra support and careful grid editing; SQLly goes deeper on SQL, guardrails and tools. An honest side-by-side.
Tablio is a free, MIT-licensed desktop database client built with Rust and Tauri. Its README pitches it as lightweight and native, with one interface for PostgreSQL, MySQL, MariaDB, SQL Server, CockroachDB, TiDB, SQLite and Cassandra/ScyllaDB. It edits tables inline, searches inside the grid, opens JSON columns as a tree, and shows per-query statistics. That is a lot of SQLly’s daily territory, so this post puts the two side by side.
We build SQLly, so take the bias into account. We read Tablio’s README, website and source, and checked the sizes of its v0.5.0 release files; we did not install it or benchmark it. For some people it is the better pick, and we say who below.
How they’re built
- Tablio is a Tauri 2 app. The backend is Rust (sqlx, tiberius for SQL Server, scylla for Cassandra, russh for tunnels). The interface is React with AG Grid and the Monaco editor, running in the operating system’s webview.
- SQLly has no webview. The engines, parser, IntelliSense and tools are a Rust core, and the UI is one Rust codebase drawn on the GPU through Metal, Direct3D or Vulkan.
Tauri’s payoff is size. Tablio’s Apple Silicon DMG is 19.8 MB, the Windows setup .exe is
15.5 MB and the .deb is 20.4 MB (the AppImage, which bundles its own libraries, is 93.8 MB). SQLly’s
macOS DMG is 65.6 MB, its Windows zip 60.9 MB and its Linux tarball 76.2 MB. Tablio also ships an
Intel Mac build, and on Linux it runs signed APT and RPM repositories so updates arrive with
apt upgrade. SQLly needs Apple Silicon.
Databases
| Engine | SQLly | Tablio |
|---|---|---|
| PostgreSQL, MySQL, MariaDB, SQL Server, SQLite | Yes | Yes |
| CockroachDB, TiDB | Yes, as documented wire-compatibles | Yes, dedicated drivers |
| Cassandra, ScyllaDB | No | Yes |
| DuckDB, ClickHouse, Oracle, libSQL/Turso | Yes | No |
| Redis and its forks | Yes | No |
If Cassandra or ScyllaDB is part of your week, Tablio handles it and SQLly does not. Otherwise SQLly covers more engines, 30 counting the wire-compatible services it documents.
Editing data
This is where Tablio puts real care. Grid edits are tracked and committed in one transaction. When you edit a query result rather than a table, Tablio parses the SQL first: the grid becomes editable only if the query reads a single table with no joins, unions, subqueries or CTEs, and every primary key column is in the result. Otherwise the grid is read-only, and a badge explains why. That is a sensible rule, and it prevents a whole class of wrong-row updates. Drops and truncates ask for confirmation.
SQLly’s row editor is generated from the
table’s own metadata, and its guardrails sit around every
statement, not only grid edits: SELECT-only connections that block file-reading and shell-escape
tricks, a hard stop on UPDATE or DELETE without WHERE,
automatic rollback, tenant checks, and production colored red. You set them once on a client,
project or environment and every connection under it inherits them. We found no read-only
connection mode in Tablio.
Grid, search and JSON
Both apps search inside a result. Tablio steps through matches; SQLly adds find and replace that stages its changes like any other edit. Both open JSON cells in a structured viewer; Tablio lets you edit the JSON there, and SQLly’s viewer also recognizes XML, YAML and Markdown.
Past that, SQLly’s grid spills to disk past 50,000 rows or 64 MiB, so fifty million rows use about as much memory as fifty, and it carries pivots, charts, conditional formatting, computed columns, result diffs and Excel export with live formulas. Tablio has bar, line, pie and scatter charts, and its Excel import and export is solid: typed values both ways, a sheet picker and column mapping on the way in.
Writing SQL
Tablio uses Monaco with table and column autocompletion, a formatter, pinned history and saved
queries. SQLly’s IntelliSense tracks aliases
and scope, writes a JOIN ON clause from real foreign keys, pulls a column’s actual
values into a WHERE clause, reads plain-language dates and flags GROUP BY
mistakes as you type. A 0.5 MB script still edits at about 5 ms per keystroke.
Query stats and admin tools
Tablio’s query statistics read pg_stat_statements, MySQL and MariaDB’s
performance_schema, SQL Server’s sys.dm_exec_query_stats and
TiDB’s statement summary, and tell you how to switch the source on when it’s missing. It
also has a session and lock dashboard, a plan viewer, role management, an ER diagram and backup
through pg_dump and mysqldump.
SQLly covers the same ground with Query Insights and the Activity Monitor, and adds schema compare with sync and rollback scripts, data compare, cross-engine data transfer, SQL Agent, Extended Events, an index analyzer and a test data generator. Its plan viewer is still marked in progress; Tablio’s is shipping.
Credentials, AI and agents
Tablio’s source saves connections, password field included, to
~/.tablio/connections.json; we found no keychain integration. SQLly keeps connections in
plain files too, but passwords stay in the OS keychain.
Tablio has no AI features and no MCP server that we could find. SQLly works with local models
(Ollama, MLX), your own endpoint or opt-in cloud providers, and sqlly-cli mcp lets an
agent read schemas and run one SELECT in a read-only transaction that is always rolled
back. If you don’t want AI near your databases at all, Tablio’s absence of it is a point in
its favor.
What they cost
Tablio is free and MIT-licensed, with no paid tier. SQLly has a free tier for hobbyists (two saved servers), a one-time $100 SQLly 1.x license and a $200 Lifetime license; see pricing. Lifetime licenses carry a source-escrow promise if SQLly is ever discontinued, but SQLly is not open source. Tablio is young: v0.5.0 shipped in May 2026, and most commits come from its author and a dependency bot.
Which one to pick
Pick Tablio if:
- You need Cassandra or ScyllaDB.
- You’re on an Intel Mac.
- You need open source, or free at any company size.
- You want a 20 MB install that updates through your Linux package manager.
- You mostly browse, edit rows and check query stats.
Pick SQLly if:
- You work in DuckDB, ClickHouse, Oracle, libSQL or Redis as well as the usual SQL engines.
- You write a lot of SQL and want completions that know your data.
- You want guardrails on every statement, set once per environment.
- You compare schemas, move data between engines, or analyze results in the grid.
- You want passwords in the keychain rather than a JSON file.
The fair test is your own database. The side-by-side table is at SQLly vs Tablio, and SQLly’s download is free.