Skip to content
Reference

Frequently asked questions

Answers to common questions about TraceX, what it is, what it can access, how safe it is, how it uses AI, pricing and getting started.

An AI engineer for production issues. It investigates problems across your databases, code, logs, errors and deploys, and tells you the root cause, the evidence and the fix. See Welcome to TraceX.

Engineering teams who run production systems, and the support and operations teams who field issues about them. Engineers get root causes and fixes; support gets an answer they can send to the customer.

How is it different from a monitoring tool?

Section titled “How is it different from a monitoring tool?”

Monitoring tells you that something is wrong. TraceX tells you why, by connecting the symptom to the records, the code and the change behind it. It works alongside your monitoring: Datadog, CloudWatch, Sentry and the rest become sources it reads.

How is it different from asking a chatbot?

Section titled “How is it different from asking a chatbot?”

A general chatbot hasn’t seen your systems. TraceX answers from your real data and code, read live, and cites the query, log line or file behind every claim.

Read-only access to the systems you want it to investigate: usually one repository and one database to start, then logs and errors. You choose what to connect, per project. See Integrations overview.

No. Every query is checked before it runs and refused unless it is a single read-only SELECT. Queries run in read-only transactions with row and time limits. We still recommend a dedicated read-only user, ideally on a replica.

No copy of your databases or repositories. TraceX keeps investigations, conversations, the evidence summaries they cite, and usage records, for as long as your retention settings say.

The text needed to investigate: the issue, relevant query results, log lines and code. Secrets, keys and tokens are always masked first, and personal data can be hidden too. See How TraceX handles your data.

Yes. The data access log records every query, log search and file read, with the investigation or question it was for, and can be exported as CSV.

Settings → Revoke access disconnects TraceX from your systems at once. You can also remove any single integration from Integrations.

Most finish in a few minutes, and you can watch progress live.

Correct it at the bottom of the report. The correction becomes a fact TraceX uses next time. The report also shows confidence and what was ruled out, so weak answers look weak. See Read a report.

No. It drafts fixes and opens pull requests when you ask. People review and merge them, and admins can require approval first. See Fixes and pull requests.

Can my support team use it without engineers?

Section titled “Can my support team use it without engineers?”

Yes. Support can start investigations from their own tools (Zendesk, Intercom, a support inbox, Slack) and get a suggested customer reply with each report.

There’s a free Starter plan, Pro at $39 a month and Team at $390 a month, with yearly billing at two months free. See Plans.

TraceX is in private beta. Request early access, or ask an admin in your organization to invite you.

Email hello@tracexpro.com. Include the investigation id or the error code if you have one.