DB Pro vs SQLly: an Electron data studio and a Rust SQL workbench

An honest comparison of DB Pro and SQLly: download sizes, engines, free-plan limits, dashboards, AI, the self-hosted Studio, and who should pick which.

By

DB Pro is a commercial database client built by a two-person team in the UK. It launched on Hacker News in November 2025, reached version 2.10.2 on 29 October 2026, and its makers film a devlog most months. It has a desktop app for macOS, Windows and Linux, a self-hosted browser version called Studio, AI on your own API key, and dashboards. It also publishes “DB Pro vs” pages about other clients, so it seemed fair to write one back.

We build SQLly, so take the bias into account. We read DB Pro’s website, pricing, FAQ, roadmap and Show HN post, checked the size of every 2.10.2 download, and unpacked the Linux .deb to see what it is built from. We did not run the app against a database or benchmark it. For several kinds of user it is the better choice, and we say which ones below.

What it is built from

DB Pro’s comparison pages describe it as “a true native app” and contrast it with Java-based tools like DataGrip and DBeaver. Its own Show HN post says something different: the tech stack is “Electron, React, tRPC, Drizzle ORM”. The 2.10.2 Linux package agrees. It contains Chromium’s resource packs, libffmpeg.so, and a 332 MB app.asar whose package.json is named @dbpro/electron. The SQL editor is Monaco, the editor from VS Code, and the grid is Glide Data Grid.

That is a reasonable way to build an app, and the DB Pro team clearly cares about how it feels. It does show up in the downloads:

DownloadSQLlyDB Pro 2.10.2
macOS (Apple Silicon)65.6 MB DMG204.4 MB DMG
Windows x6460.9 MB zip156.5 MB installer
Linux x6476.2 MB tarball214.3 MB AppImage, 153.9 MB .deb

SQLly is one Rust codebase drawn on the GPU through Metal, Direct3D or Vulkan, with no browser engine inside. DB Pro has a platform win, though: it ships an Intel Mac build and Linux arm64 packages in three formats. SQLly needs Apple Silicon on the Mac.

Databases

EngineSQLlyDB Pro
PostgreSQL, MySQL, MariaDB, SQLite, SQL ServerYesYes
ClickHouse, Redis, Turso/libSQLYesYes
Supabase, NeonYes, as documented Postgres compatiblesYes, as named connectors
MongoDB, Amazon DynamoDBNoYes
Oracle Database, DuckDBYesNo
Azure SQL with Entra sign-inAzure SQL yes; Entra sign-in in progressNot documented
Valkey, KeyDB, DragonflyDB, ElastiCache, MemoryDBYesNot documented

DB Pro’s homepage shows thirteen connector logos; four of them are hosted providers, so it comes to ten engines. If MongoDB or DynamoDB is part of your day, DB Pro covers them and SQLly doesn’t. SQLly’s engine list runs to 30, and spells out which tools work on which engine.

Writing SQL

DB Pro’s editor has schema-aware autocomplete for tables, columns and aliases, results in separate tabs when you run several statements, saved queries with labels and version history, and full query history. Typing a forward slash in the editor asks the AI to write SQL at the cursor.

SQLly spends most of its effort here. IntelliSense tracks aliases and scope, writes a JOIN ON clause from real foreign keys, pulls a column’s actual values into a WHERE clause, understands plain-language dates, and flags a GROUP BY mistake while you type. A 0.5 MB script costs about 5 ms per keystroke. There are also query parameters, templates, multi-cursor editing, split views, folding and AI ghost text.

Results and dashboards

This is where DB Pro is most distinctive. Its grid has inline editing with a review of pending changes before commit, and filters that persist between sessions. On top of that sit dashboards: metric, chart, sparkline, map, table, text and image tiles on a canvas, refreshed on a timer, and an AI button that drafts a dashboard from a table. A workflow builder schedules exports and cleanup jobs. SQLly has nothing like the dashboard canvas.

SQLly’s grid goes the other way, into analysis of a single result. It streams rows to disk past 50,000 rows or 64 MiB, so fifty million rows use about as much memory as fifty. It has pivots, charts, conditional formatting, computed columns, result diffs and Excel export with live formulas and a pivot sheet, and a one-line comment saves the layout with the query.

AI

DB Pro’s AI arrived in March 2026: a chat sidebar, inline generation in the editor, and AI dashboards. You bring a key for OpenAI, Anthropic, Google or OpenRouter, or run Ollama, and requests go straight to the provider. It has three permission levels - off, schema only, or schema and data - and the chat blocks write queries. That is a sensible design.

SQLly works with local models (Ollama, MLX), your own endpoint, or cloud providers you opt into, with no default provider; see on-device AI. It also ships an MCP server, sqlly-cli mcp, so an agent like Claude Code can list connections, read schemas and run one SELECT in a read-only transaction that is always rolled back. Writes come back to you as proposals, and production connections are refused. We found no MCP server documented on DB Pro’s site.

Admin tools and safety

DB Pro is open about where it stands. Its public roadmap has a section called “Deeper Database Management” - create and drop indexes, view index usage, manage users and roles, view active connections, cancel a running query, run VACUUM and ANALYZE - and every item in it is marked not started. It does warn before destructive queries.

SQLly has those tools today under one Tools menu: Activity Monitor with blocking chains, Query Insights over Query Store, pg_stat_statements and Performance Schema, SQL Agent, Extended Events, an index analyzer, schema and data compare, and backup and restore as scripts you read first. Its guardrails go past warnings: SELECT-only connections that block file-reading and shell-escape tricks, a hard stop on UPDATE or DELETE without WHERE, and automatic rollback, inherited from a client, project or environment.

Teams and the browser

DB Pro Studio is a real advantage. One docker run starts a browser workspace on your own server, free for up to two users, with shared connections, queries and dashboards, roles, an audit log, and scoped tokens so teammates never see raw database passwords. Its custom-priced Team tier lists SSO (still marked not started on the roadmap), air-gapped installs and IP allowlists. SQLly has no shared web version; its browser preview is a demo, and its bridge and relay exist to reach remote databases from the desktop app.

What they cost

DB Pro’s free plan allows 2 connections, 3 open tabs, 5 saved queries, 2 dashboards, 2 table tags and 1 device, and its pricing table marks data import and export as paid. The one-time licence lists at $99, shown at $59 with a promo code when we looked, and includes one year of updates on two devices. The monthly plan is $9.99 with updates while you subscribe.

SQLly is free for hobbyists with two saved servers, one cloud account and a reminder to pay about every five hours, and it isn’t free for organizations over 100 employees. A SQLly 1.x license is $100 one-time and Lifetime is $200; see pricing. At the promo price, DB Pro is cheaper to buy.

One thing to check before you pay: DB Pro’s pages don’t agree with each other. The pricing page says 2 connections on the free plan, the FAQ says the free plan supports unlimited local connections, and its TablePlus page says there are no “artificial tab or connection caps”. The one-time licence shows up at $59, $79 and $99 in different places. The same TablePlus page puts TablePlus at “around $89”; TablePlus’s own pricing page starts at $99. Small team, fast-moving site - but read the pricing page, not the FAQ.

Which one to pick

Pick DB Pro if:

  • You need MongoDB or DynamoDB next to your SQL databases.
  • You want dashboards built from your tables, or a team browser workspace you host yourself.
  • You’re on an Intel Mac.
  • You want to pay monthly, or less up front.
  • You mostly browse tables, edit rows and run simple queries.

Pick SQLly if:

  • You work in SQL Server, Azure SQL, Oracle or DuckDB.
  • You write a lot of SQL and want completions that know your data.
  • You need to see sessions and blocking, read plans, or compare schemas today.
  • You want guardrails that stop a bad statement, not only warn about it.
  • You want a smaller app with no browser engine inside.

The fair test is your own database. The side-by-side table is at SQLly vs DB Pro, and SQLly’s download is free with no account.