They all demo identically — a question goes in, SQL comes out. The differences show up in week three, on your schema, and they are all architectural.
Ask these of any tool in this category, including this one. Each is architectural — a vendor either built it in or cannot add it later without a rewrite, which is why they predict week-three experience better than any feature list.
Most tools in this space are web apps you paste a connection string into, which means your credentials and your schema live on a third party's infrastructure and your database has to accept connections from theirs. That is a real trade for real convenience — nothing to install, works from anywhere. The cost is that privacy becomes a policy question rather than an architectural fact, and in a regulated environment the difference is the entire procurement conversation.
It is a desktop application. It introspects the live catalog and caches keys, types, distinct values and statistics; it executes read-only and self-corrects; every generated statement is parsed to an AST and validated to a single SELECT; credentials never leave the machine; and with a local model configured it runs with no network access at all. The trade we made is the mirror of the hosted one — there is something to install, and it runs where you install it.
Accuracy percentages quoted against public benchmarks tell you about that benchmark's schema, not yours. Logos on a landing page tell you about the marketing budget. The only test that predicts anything is pointing a candidate at your own worst schema and asking the five questions your team actually asks — which is why there is a free plan here with no card and no expiry.
More answers on the main FAQ, or ask us directly.
The landscape
For people who already write SQL
The category, explained
Every page in this section covers a different question about the same product. See all solutions.
Start free, upgrade when you are asking enough questions for it to matter.