Docs / Guides
Let your team query production safely
SayQL lets your team query production safely. Support, ops, PMs and analysts ask in plain English, without being SQL experts.
Get started
- Each person downloads SayQL and connects with their own login. SayQL connects straight from their computer; there's no SayQL server in between.
- Each picks an AI in Settings → AI provider, with their own API key or a local model.
- They ask: "orders for customer 4512 this month", "failed payments in the last hour", "signups per week since January".
Four layers of safety
- Read-only by default. SayQL checks every statement before it runs.
- Confirmation before any change.
INSERT,UPDATE,DELETE, DDL and anything else that could change data stops and asks first. - The database enforces it. Reads run in a read-only transaction on PostgreSQL and MySQL, and on a read-only connection on SQLite, so the database itself refuses writes.
- SQL Server has no read-only mode, so reads run in a transaction that's always rolled back. For production, give people a login that can only read (
db_datareader).
The AI sees table and column names, types, keys, enum values and row estimates, never your table rows. Results show up to 5,000 rows.
More in Run queries safely and Privacy and data.
Something missing or unclear? Ask in Discussions.