Comparison
AddisDB vs Dory
An Apache-2.0 SQL workspace built for humans and coding agents to share. The only tool here where an external agent is a first-class user.
Engine breadth
How many database engines and data-file formats it can actually open.
Dory — Good
Twelve SQL engines — Postgres (with Neon and Supabase), MySQL, MariaDB, SQLite, Cloudflare D1, DuckDB, SQL Server, Oracle, Snowflake and a deeply integrated ClickHouse — plus local CSV, TSV, Parquet, JSON and Excel files read through DuckDB. All SQL: no Mongo, Redis, Cassandra or Neo4j, and no BigQuery, Redshift or Databricks.
AddisDB — Strong
95 engines and data-file formats, from Postgres and MySQL through Mongo, Redis, Cassandra and Neo4j to Snowflake, BigQuery, ClickHouse and local CSV/Parquet/GeoJSON. Every engine is on every plan, including the free one.
Cost & openness
What it costs to use for real work, and whether you can read the source.
Dory — Strong
Apache-2.0 and free, with nothing sold: no pricing page, no paid edition, commercial use included. Self-host it with Docker or run the desktop build. The hosted service carries hobby/pro plumbing and an AI token quota that a deployment can switch on, but a self-hosted install with your own key has neither.
AddisDB — Good
Free forever for databases on your own machine — the whole client, every engine, no account and no card. $49/year to reach databases that are not local; $99/user/year for teams; $299/user/year for SSO, audit log and RBAC. Source is not public.
Platform reach
Which operating systems and surfaces it runs on.
Dory — Good
macOS and Windows desktop builds, a self-hosted web app over Docker, and an npm CLI that doubles as the agent runtime. No Linux desktop app — on Linux you self-host and use the browser.
AddisDB — Strong
macOS, Windows and Linux as a native app, plus a CLI with a TUI and a VS Code extension that share the same core.
Production safety
What stands between you and the wrong statement on a production database.
Dory — Limited
The safety thinking is aimed at the agent rather than at you: agents get read-only SQL, and their work lands as an inspectable workspace to review before you act on it, which is a better answer than a chat transcript. For your own statements there is nothing — no read-only connections, no statement classification, no production tag.
AddisDB — Strong
Connections can be marked read-only; statements are classified before they run, so an unqualified DELETE or a DROP is stopped rather than reported afterwards. A prod environment tag adds write guards, and row-count thresholds catch the statement that would hit more rows than you meant.
AI capability
What the AI does, what it costs, and where your schema and keys go.
Dory — Strong
Schema-aware SQL generation, rewriting and explanation, bring-your-own-key across OpenAI, Anthropic, Google, Qwen, xAI and any OpenAI-compatible endpoint. The distinctive part is MCP: Claude Code or Codex can use Dory as their database execution layer, and what the agent did comes back as editable SQL tabs, result sets and charts. One caveat their README states plainly — AI requests are the exception to everything staying on your machine, routed through a Cloudflare AI gateway; it is a per-deployment setting, so self-hosting with your own key is how you avoid it.
AddisDB — Strong
Plain-English to SQL, schema-aware, with the generated statement shown for you to edit before it runs. Bring your own provider key: it is stored in the OS credential store, calls go straight to your provider, and AI is included on the free tier because we are not the ones paying for the tokens.
Schema tooling
Diagrams, diffs, and getting a schema change from your laptop to production.
Dory — Limited
An interactive schema graph of primary keys, foreign keys and relationships, with PNG and SVG export — genuinely good for learning an unfamiliar database. There is no schema diff and no migration tooling, so getting a change to production is not something it helps with.
AddisDB — Strong
ERD of tables and foreign keys, schema diff between databases, and a migration preview that shows the exact SQL plus the dangerous parts — dropped columns, rewrites, locks — before anything runs. Reads Drizzle Kit and Prisma changes too.
The scoreboard
Dory matches or beats AddisDB on: Cost & openness, AI capability.
AddisDB comes out ahead on: Engine breadth, Platform reach, Production safety, Schema tooling.
Which one to pick
Pick Dory if…
Your coding agent should be driving the database, and you want that layer to be Apache-2.0 with nothing sold on top of it. Nothing else here treats an external agent as a first-class user, and nothing else here is this generous.
Pick AddisDB if…
You need a Linux desktop app, an engine outside its SQL set, or a client that stops your own destructive statement — Dory guards what the agent does, not what you do.
About this comparison
Ratings and prices were checked against each vendor's own pages on 2026-08-11. We wrote this and we make one of the tools in it, so read it as what it is — and if something here is wrong or out of date, tell us and we will correct it.