// sqlly vs tablepro

SQLly vs TablePro

TablePro’s README opens with “TablePro is what I wanted TablePlus to be: native, fast, open source.” It is a Swift app for the Mac, iPhone and iPad, AGPL-licensed, with 37 engines, an AI assistant and an MCP server, and it has gathered about 6,400 GitHub stars in under a year. SQLly is a Rust workbench for macOS, Windows and Linux that spends its effort on writing and running SQL safely. Both are good; here’s where each one wins.

Last reviewed: November 2026

The short version

SQLly

A deep SQL workbench on every desktop

One Rust codebase drawn on the GPU on macOS, Windows, and Linux. Thirty engines, IntelliSense that reads your data, guardrails you set once per environment, a grid that streams millions of rows to disk, and script-first admin tools. Agents get read-only access; anything that writes comes back to you as a proposal.

TablePro

An open-source native client for Apple devices

A Mac app that runs on Apple Silicon and Intel, plus a free iPhone and iPad app. 37 engines through built-in and plugin drivers, from PostgreSQL to MongoDB, Snowflake and Kafka. AI chat with about 15 providers, an MCP server with tokens and an activity log, plan diagrams on many engines, and Vim mode. Free at work; a license adds a set of extras. No Windows, and Linux isn’t released yet.

Feature by feature

SQLly’s column uses the same honest status badges as the features page and the docs. For TablePro we list what its website, docs and repository state, checked against v0.85.0 (November 4, 2026).

Feature comparison of SQLly and TablePro
Capability SQLly TablePro
macOS YesSigned and notarized. Apple Silicon only. A Mac App Store edition is available too. YesmacOS 13 or later, on Apple Silicon and Intel. Homebrew cask or DMG.
Windows & Linux YesA supported beta on amd64 and arm64, from the same codebase as the Mac app. NoNo Windows version. A Linux app is in development in the repository, with nine engines so far and no release.
iPhone & iPad No YesiOS and iPadOS 18 or later, free, on a subset of engines, with connections synced from a Mac.
Download size (macOS) 65.6 MBDMG, with DuckDB compiled in. 82.3 MBThe v0.85.0 DMG. Plugin drivers download separately: DuckDB’s is 37.7 MB, Oracle’s 11.5 MB.
Free to use Free tierTwo saved servers, one cloud account, and a reminder to pay about every five hours. Not for organizations over 100 employees. Pricing YesFree at any company size, with no time limit. On day 30 a sheet asks whether you’ll buy a license, then again every 90 days unless you say you use it personally.
Open source NoLifetime licenses carry a source-escrow promise if SQLly is ever discontinued. YesAGPL-3.0, paid features included in the source.
SQL Server, PostgreSQL, MySQL, SQLite YesPlus MariaDB, Azure SQL (Entra sign-in in progress), and documented compatibles such as CockroachDB, Neon, Supabase and Aurora. Full list YesSQL Server is a plugin, with Kerberos and Entra ID sign-in. MariaDB, TiDB, OceanBase, CockroachDB and Redshift too.
DuckDB, ClickHouse, Oracle, libSQL/Turso YesNative drivers, DuckDB bundled. Per-engine coverage YesClickHouse is built in; the other three are plugins.
Snowflake, BigQuery, Trino Planned YesPlugins, alongside Teradata, Spanner, SAP HANA, Databend and Cloudflare D1.
MongoDB, Cassandra, DynamoDB, Elasticsearch, Kafka NoSQLly sticks to SQL databases and Redis. YesPlugins, plus SurrealDB, ScyllaDB, Typesense, Weaviate and etcd.
Redis YesTyped key editing, Cluster and Sentinel, ACLs, pub/sub, profiler, memory analyzer, slow log; Valkey, KeyDB, DragonflyDB, ElastiCache and MemoryDB. Redis YesKeys and TTLs on standalone, Sentinel and Cluster, with sessions and metrics on its server dashboard.
Write your own driver NoNo plugin system. YesDriver plugins in Swift, with a public plugin registry.
Import connections from other tools YesDataGrip, DBeaver, pgAdmin, Azure Data Studio, DbGate, TablePlus, Navicat and more; exports too. Passwords stay behind, except from Redis Insight. Compatibility YesTablePlus, Sequel Ace, DBeaver, DataGrip, Beekeeper Studio and Navicat, with passwords and saved queries.
Autocomplete YesAlias- and scope-aware, JOIN ON from foreign keys, real column values in WHERE, plain-language dates, GROUP BY mistakes flagged. IntelliSense YesSchema-aware, with aliases, subqueries, CTEs, per-dialect operators and enum values.
Vim mode No YesVim and Emacs key bindings.
Edit table data YesA row editor generated from the table’s own metadata. Row editor YesEdits queue up with an SQL preview and save in one transaction. Data Rewind (Pro) restores a save.
Very large results YesStreams and spills to disk past 50,000 rows or 64 MiB; memory stays flat at 50 million rows. Streaming CappedQuery results stop at a configurable row cap, and the grid pages through them.
Pivot & conditional formatting YesPivot, conditional formatting, computed columns, and result diff. Pivot -Couldn’t find a pivot view in its docs.
Result charts YesIncluded. Charts ProA chart mode in the grid, plus a map mode for location data.
Import & export data YesCSV, JSON, SQL, and Excel with live formulas and a pivot sheet. Excel export YesExport to CSV, JSON, SQL, MQL, XLSX or a data dictionary, with a Parquet plugin; import SQL, JSON and CSV.
Execution plan viewer In progressPlain-language findings, tree, and diagram across nine engines. Query plans YesDiagram and tree from about a dozen engines, including SQL Server showplan and Oracle actual plans, and a compare between runs.
Schema & data compare YesRisk-graded schema diffs with sync and rollback scripts, across engines, plus data compare. Schema Compare ProCompare & Sync covers schema and rows, and writes a script you read before it runs.
Query history statistics YesQuery Insights reads the server’s own Query Store, pg_stat_statements, Performance Schema, ClickHouse query log or Redis slow log. ProQuery Insights groups the queries you ran in TablePro: most run, slowest, got slower, failures.
Sessions & server activity YesActivity Monitor with blocking chains, waits and expensive queries, Server Dashboard, Extended Events and SQL Agent. Activity Monitor YesServer Dashboard with sessions, cancel and kill, metrics and slow queries on nine engine families.
Other admin tools YesIndex analyzer, test data generator, disk usage, cross-engine Data Transfer, scheduled tasks, notebooks, backup and restore as reviewable scripts. Tools YesUsers & Roles editor, Table Health (bloat, unused indexes), a PL/pgSQL and PL/SQL debugger, data masking, and backups through each engine’s own dump tool.
ER diagrams YesExport to SVG, Mermaid, or DBML. Relationship Graph YesInteractive, with schema edits from the diagram, on engines that report foreign keys.
Guardrails in the editor YesSELECT-only connections that block file-read and shell-escape tricks, a hard stop on UPDATE/DELETE without WHERE, auto-rollback, tenant checks, optional AI review, inherited from client to project to environment. Safety YesSix Safe Mode levels per connection, from none to Touch ID on every write to read-only, a warning on DELETE with no WHERE at every level, and a minimum level an MDM can enforce.
AI in the app YesLocal models (Ollama, MLX), your own endpoint, or opt-in cloud providers, with no default. Ghost text in the editor. On-device AI YesChat, inline suggestions, review/explain/optimize/fix, on about 15 providers including Ollama, MLX and Apple Intelligence. Edit and Agent modes can run queries, behind Safe Mode.
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 YesOff by default, local only, scoped tokens, per-connection approval, writes through Safe Mode, and a 90-day activity log. Free.
Sync between machines PartialEverything is plain files, so any file-sync tool works; passwords stay in the OS keychain. iCloud Drive sync is planned. ProiCloud Sync across Macs, iPhone and iPad.
UI languages 10English, Spanish, Simplified and Traditional Chinese, Japanese, Korean, German, French, Brazilian Portuguese and Russian. 7English, Vietnamese, Simplified and Traditional Chinese, Korean, Turkish and French.

A dash means we couldn’t confirm it from TablePro’s own materials - check its docs for the current state. “Pro” means TablePro needs a paid license for it.

Where SQLly is different

TablePro goes wide on engines and Apple platforms. SQLly goes deep on SQL, on every desktop OS.

The same app on Windows and Linux

SQLly is a single Rust app, so a feature lands on macOS, Windows, and Linux in the same release. If your team isn’t all on Macs, that settles it: TablePro has no Windows version and its Linux app hasn’t shipped.

How it works →

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, turn “last tuesday” into a date, and underline a GROUP BY mistake as you type.

IntelliSense →

Results with no row cap

SQLly streams rows and spills to disk past 50,000 rows or 64 MiB, so a 50-million-row result uses about as much memory as a small one. On top: pivot, charts, conditional formatting, computed columns, result diffs, and Excel export with live formulas.

Spill-to-disk results →

Agents never write on their own

TablePro lets an assistant or MCP client run writes once Safe Mode allows them. SQLly’s MCP server only runs a SELECT in a transaction the database keeps read-only and then rolls back. A write comes back as a proposal with the exact SQL, and production connections are off limits.

Read-only enforcement →

Guardrails set once, inherited everywhere

Safety settings live on a client, project or environment, and every connection under it picks them up: SELECT-only, no unbounded UPDATE/DELETE, auto-rollback, tenant checks, and production painted red.

Safety & guardrails →

DBA tools in the base price

Schema and data compare, Query Store and pg_stat_statements insights, charts, Activity Monitor with blocking chains, SQL Agent, Extended Events, test data and cross-engine data transfer are all included. In TablePro, compare, insights and charts need Pro.

Tools →

When TablePro is the better choice

TablePro is probably the better fit if:

  • You use anything beyond SQL and Redis. MongoDB, Cassandra, DynamoDB, Elasticsearch, Kafka, Snowflake, BigQuery, Trino and more are a plugin away. SQLly doesn’t connect to any of them.
  • You’re on an Intel Mac, or want your databases on an iPhone or iPad. TablePro runs on both Mac architectures and has a free mobile app. SQLly needs Apple Silicon and has no phone app.
  • Open source, or free at any company size, is a requirement. TablePro is AGPL-3.0 and free at work with no limit on engines or connections. SQLly’s source is closed, and its free tier stops at two saved servers and isn’t for organizations over 100 employees.
  • You read a lot of plans today. TablePro draws plan diagrams from about a dozen engines and compares runs; SQLly’s plan viewer is still in progress.
  • You want an agent to make changes for you. TablePro’s Agent mode and MCP server can run writes behind Safe Mode, with tokens and an activity log. SQLly’s agents only read.
  • You want a Mac-native feel. Native window tabs, Touch ID on writes, Handoff, Vim mode, Apple Intelligence, MDM policies, and seven UI languages.

One caveat in the other direction: TablePro’s repository dates from December 2025, it is still numbered 0.x, and it published 60 releases and betas in the last 30 days. Check its changelog for anything you rely on.

Questions

Is TablePro free?

Yes. TablePro is open source under the AGPL-3.0, and the free app covers every engine, the editor and grid, the AI assistant and the MCP server, at a company of any size. A Pro license ($39 a year, $4.99 a month or $79 one-time, for up to 3 Macs) adds Compare & Sync, Query Insights, result charts, Data Rewind, iCloud Sync and a few connection features; Team is $10 per seat per month billed yearly. The iPhone and iPad app needs no license. SQLly is free for hobbyists, with a $100 SQLly 1.x license and a $200 Lifetime license for everyone else.

Does TablePro run on Windows or Linux?

Not yet. TablePro runs on macOS 13 or later on Apple Silicon and Intel, and on iOS and iPadOS 18 or later. A Linux app is in development in its repository but has not been released, and its README lists no Windows version. SQLly runs on macOS, Windows and Linux from one codebase, though it needs Apple Silicon on the Mac and has no phone app.

Which databases do SQLly and TablePro support?

TablePro lists 37 engines on the Mac: 12 built-in drivers and 25 plugins that download on first use, including MongoDB, Snowflake, BigQuery, Cassandra, DynamoDB, Elasticsearch and Kafka. SQLly supports 30 engines, all SQL databases plus Redis and its compatibles, with SQL Server, Azure SQL, PostgreSQL, MySQL, MariaDB, SQLite, DuckDB, ClickHouse, Oracle and libSQL/Turso as native drivers. If you need a document, wide-column, search or streaming store, TablePro covers it and SQLly does not.

Can AI agents use SQLly or TablePro over MCP?

Both ship an MCP server. TablePro’s is off by default, listens only on the local machine, needs a scoped token for every request, asks before a client reaches a connection, sends writes through the connection’s Safe Mode, and keeps a 90-day activity log; destructive statements need a full-access token and a click every time. 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. SQLly is free on macOS, Windows, and Linux, with no account required.