Every question is a ticket
“How many customers use this feature?” waits in a queue for someone who knows SQL.
Answers from production, for every team.
Product, operations, finance and customer success all have questions only your production data can answer. TraceX lets them ask in plain English, read-only, with the evidence behind every number.
The problem
Sound familiar?
Dashboards never have it
The one number you need is never on the dashboard someone built last quarter.
Nobody trusts the number
Without the query and the rows behind it, every answer starts an argument.
Plain English
Ask it the way you'd ask an engineer.
TraceX knows your schema and how your tables link, writes the query, runs it read-only and answers with a citation for every number.
- No SQL needed
- Tables and charts for counts and trends
- Follow-up questions keep the context
How many refunds are stuck, and since when?
Queried refunds · 34 rows
Read 3 commits in payments-api
Checked the answer against the evidence
34 refunds are stuck in
pending, all created after migration 0142 shipped on Oct 21 1 2.
| Day | Stuck |
|---|---|
| Oct 21 | 12 |
| Oct 22 | 14 |
| Oct 23 | 8 |
Files
Spreadsheets when you need them.
Ask for the data behind an answer as a spreadsheet, CSV or PDF, and download it. Exported files are deleted after 24 hours.
- Excel, CSV and PDF
- Built from the same read-only query
- Deleted after 24 hours
Export the customers still on the legacy plan as a spreadsheet
Queried accounts · 212 rows
Built legacy-plan-customers.xlsx
212 customers are still on the legacy plan 1. ⤓ legacy-plan-customers.xlsx
Safe for everyone
Anyone can ask. Nothing can change.
Every connection is read-only and every query is checked before it runs, so you can give the whole company access without risking production.
- Read-only credentials
- Write queries refused before they run
- Roles for admins, investigators and viewers
SELECT id, state FROM refunds WHERE order_id = 48213UPDATE refunds SET state = 'paid'DROP TABLE refundsOnly read-only queries run. Everything else is refused before it reaches your database.
Charts
Trends, drawn from your data.
Ask how something changed over time and get a chart, built from the read-only query it cites.
- Charts from live production data
- The query behind every chart
- Spreadsheet export on request
How many new workspaces signed up each month this year?
Queried workspaces · 6 months
Sign-ups grew every month 1.
18May
24Jun
31Jul
37Aug
45Sep
52Oct
How it fits
Set up once. Useful every day.
Connect your data
A read-only connection to your databases. TraceX learns the schema and how the tables link.
Invite your teams
Give product, operations, finance and success access, with roles for each.
Ask anything
In the dashboard or in Slack, in plain English, with the evidence behind every number.
What you get
Built for how you work.
Self-serve answers
Teams get the numbers they need without waiting on engineering.
Knows your data
TraceX learns how your tables link, so cross-table questions get the right join.
Checked before you see it
A second model checks every answer against the evidence.
Ask in Slack
Mention TraceX in a channel and get the answer in the thread.
Measured accuracy
Keep test questions with known answers to see how often TraceX is right.
Read-only, always
Production is never changed, whoever is asking.
FAQ
Questions
How does TraceX know our data?
It reads your schema and learns how your tables link, so questions across several tables get the right join.
How do we know the answers are right?
Every answer cites its query and rows, a second model checks it against them, and you can keep test questions with known answers to measure accuracy.
Can someone accidentally change data?
No. Connections are read-only and write queries are refused before they run.
Find the root cause.
Ship the fix.
TraceX is free during the private beta. Connect a database and a repository and ask your first question in minutes.