SQLore answers questions about your own PostgreSQL and MySQL databases in plain English — and shows you exactly how it got there.
1
Statement per query. Anything that is not a single read-only SELECT never reaches your database.
0
Rows sent to a model provider. Your schema is read; your data stays on your machine.
We read your schema, write the SQL, run it read-only, and show you every query.
Generated SQL is parsed to an AST and validated down to a single read-only SELECT before it is allowed near your database, then executed on a read-only connection with a statement timeout. Not a blocklist of dangerous words — a parser.
An answer arrives explained and drawn — a chart, a table, a single figure — and directly beneath it the query that produced it, the rows it returned and how long it took. The picture is what makes it readable; the query is what makes it checkable, and an answer you cannot check is one you cannot use for anything that matters.
Your schema goes to the model so it can write the query. Your data does not. The query runs against your own database and the results stay on your machine — and if that is still too much, point it at a local model.
Answering a question may take several model calls — linking the schema, generating, retrying after a bad join. They are charged once, because anything else is impossible to explain on an invoice.
Questions we have not answered here are probably in the FAQ, the full capability list is on the features page, and anything else reaches a real person at our contact page.
Start free, upgrade when you are asking enough questions for it to matter.
