Agentic data analysis for PostgreSQL, MySQL, Oracle & SQL Server
Ask your data
anything.
Your database holds the answers. QueryAI uncovers them with natural-language questions, context-aware SQL, and clear analytical insights.
No data movement. QueryAI reads your schema, runs read-only queries, and writes nothing.
Try another question
Agent activitymax 2 queries
Question understood
retrieve_context · hybrid schema search
run_sql · validated read-only
Composing the answer
$4,820
top product revenue
| Revenue per product | Value |
|---|---|
Meridian Desk Lamp | $4,820 96 orders |
Fieldline Backpack | $3,690 74 orders |
Halden Mug Set | $3,156 118 orders |
Vantage Desk Mat | $2,480 63 orders |
Orla Ceramic Vase | $1,931 41 orders |
Top 5 of 24 products by quarterly revenue
Starting demonstration
Sample workspace with demonstration data. Nothing here is executing, connect your own database inside the app.
01 · How it works
From connection to answer in three steps
No dashboards to configure, no SQL to hand-write. QueryAI sits on top of the database you already have.
- 01
Connect
Point QueryAI at a supported database. The schema (tables, columns, foreign keys) is extracted and indexed for retrieval.
database_typepostgresqlhostdb.internal.acme.ioport5432Credentials encrypted (Fernet) before they are stored
- 02
Ask
Describe the analysis in plain English. The agent retrieves the most relevant tables from your indexed schema before it touches any query.
How did churn move after the March pricing change?Schema context retrieved first, so SQL fits your tables
- 03
Discover
Inspect the generated SQL, the returned rows, and a written analytical answer that states what the data actually shows.
SELECT plan, SUM(total)
FROM v2_mrr_by_plan GROUP BY plan
Every answer links back to the exact query and rows
Supported engines: PostgreSQL, MySQL, Oracle, and Microsoft SQL Server.
02 · Under the hood
An agent that investigates before it answers
Each question runs through the same honest pipeline: ground the question in your real schema, query carefully, then explain what came back.
Question
Plain English
Schema retrieval
Dense + BM25, top 10
SQL execution
Validated read-only
Results
Up to 50 rows per run
Explanation
The numbers, in words
The agent is bounded: at most two schema retrievals and two SQL queries per question, so it investigates with intent instead of thrashing.
03 · Features
Built for questions, not dashboards
Everything on this page maps to shipped behavior: hybrid schema retrieval, bounded agent runs, read-only execution, conversation memory.
Natural-language exploration
Ask in the words you'd use with a colleague. Follow-ups keep the thread, so refinement doesn't mean starting over.
Top customers by spend this month?
The top 5 account for 62% of monthly revenue. Alice Johnson leads at $15,420.
Ask a follow-up: “Which of them ordered in the last 7 days?”
Context-aware schema retrieval
Your schema is indexed and searched with hybrid dense + sparse retrieval, filtered to your account and database.
T:orders | cols:8 | J:customers(customer_id)
T:products | cols:6 | J:orders(product_id)
T:customers | cols:5
AI-assisted, read-only SQL
Queries are generated for you, validated as read-only, and executed with results capped before they reach the answer.
run_sql · validatedwrite blocked
DROP TABLE orders
returns: rejected before execution
SELECT total FROM orders ✓
Analytical answers
Not just rows: a written answer that names the metric, the comparison, and the conclusion you can act on.
“August orders split 44% repeat vs 56% new; repeat buyers average $61 per order vs $48 for first-time customers.”
metric · comparison · conclusion
Conversation history
Every conversation and turn is stored, so yesterday's investigation is still available today.
- Revenue Analysis4 turns
- Churn after pricing change2 turns
- Top regions by margin6 turns
Preferences that stick
The agent remembers how you like answers delivered and applies it conversation after conversation.
Preferences are remembered per user and per database, and steered into every new answer.
04 · Security
Your database is respected as your database
QueryAI is designed around one rule: it can look, but it cannot touch. These are current product behaviors, not roadmap promises.
Read-only by construction
Every SQL statement is validated before execution. Only reads pass; the agent cannot insert, update, or delete anything in your database.
Credentials encrypted at rest
Connection credentials are encrypted before they are stored and decrypted only in memory, at the moment a query runs.
Tenant-scoped context
Schema retrieval is filtered strictly to your user and your database. One tenant never sees another tenant's tables.
Bounded, observable runs
Each answer is limited to two schema lookups and two SQL queries. You see the exact queries and rows behind every conclusion.
Your data has answers.
Start asking.
Sign up, connect one database, and ask your first real question in plain English.
Works with PostgreSQL, MySQL, Oracle, and SQL Server