Read-only AI investigator

The bug ticket with no error and no stack trace just landed. Again.

Treap investigates the escalations no other tool can reach, then answers in Slack with a root cause and the evidence.

Sentry catches the crashes.
Treap catches "why is this number wrong?"

Get early access

Self-serve and flat-priced. I will email you personally before launch.

The problem

"It's broken," and there is nothing to grep for.

01

No error. No event.

A customer says the invoice total is wrong, or their data disappeared. Nothing threw. Nothing logged. There is no exception for your monitoring to catch, just a person telling you something is off.

02

A senior engineer stops everything.

They spelunk through GitHub history, log lines, and the production database to reconstruct what actually happened. The most expensive person on the team, doing manual archaeology.

1 to 3 hrs of focused senior time, per incident
03

"Is this a known bug?"

PMs and support keep interrupting mid-dig. Half the time it is config drift or a regression you already fixed once, but nobody remembers, so you find it from scratch again.

How it works

From a Slack message to a root cause.

1

Post the escalation in Slack

Paste the customer report into the channel Treap watches, or @-mention it on the thread where support already flagged it. No ticket format, no error required.

2

Treap investigates, read-only

It correlates across GitHub, logs, your database, and Sentry, reading only and never writing, to reconstruct what changed and when, the way your senior engineer would.

3

Replies in-thread with a verdict

Suspected root cause, the likely PR or deploy, the exact evidence it checked, and a confidence score. Trust it, or take over knowing exactly where it already looked.

4

Saved to incident memory

Every investigation is remembered. When a recurring issue returns, Treap recognizes it: "this matches the rounding regression from PR #4127, fixed and reintroduced."

// what it posts back

# eng-escalations
Riya (Support) 10:42

Acme says their March invoice total is $40 too high. No error on our side, nothing in Sentry. Known bug?

Treap APP 10:43

Investigated. Likely a rounding regression, not a data issue.

root cause   Tax is rounded per line item, then summed, double-counting half-cents. Introduced in #4127.
likely PR     #4127 "Refactor invoice tax calc", deployed Mar 2, 14:10
evidence    
  • Acme invoices skew high only after deploy 8f3c1a2
  • roundLineItem() called before sum(), order flipped in #4127
  • 17 of 92 March invoices affected, all multi-line
confidence87%

Not a dashboard. A teammate that sits in front of your engineers.

Treap takes the first pass at every escalation, so a report only reaches a human when it actually needs one.

Triages every escalation first

Incoming reports get sorted before anyone is pulled in: real bug, known issue, config drift, or expected behavior. The noise stops at Treap.

Reads the code, returns an RCA

It reads the actual code and data, reconstructs what happened, and replies with a root cause you can act on, not a guess.

Answers the rest of the team

Support and product can ask "is this expected?" or "did we ship X?" and get a grounded answer, sparing your engineers the interruption.

Gets sharper with every investigation

Every investigation is saved to incident memory. The next time a similar report lands, Treap surfaces the past one instead of starting from scratch, so the answer comes back faster.

matches PR #4127 · rounding regression, seen 2x

Connectors

Connect a source in one step: paste the key.

No agent to deploy, no sidecar, no infra changes. Drop in read-only credentials for whatever you run and Treap investigates across it.

PostgreSQL
Database
MySQL
Database
MongoDB
Database
GitHub
Source control
OpenSearch
Search and logs
Sentry
Monitoring

...and you name it: anything that speaks SQL, exposes an API, or holds a log.

Connecting Postgres is justtreap connect postgres --url $READONLY_DSN

It answers wherever the question was asked, so nobody opens another tab.

Slack replies in-threadMicrosoft Teams answers in channelsGoogle Chat answers questionsGmail replies by emailJira comments on ticketsConfluence writes to docs

Why Treap

There are great tools. None of them fit you.

vs. Sentry Seer and error-triage AI

It needs an event. Your bug doesn't have one.

Them

Starts from an error or exception Sentry already captured, then triages it.

Treap

Starts from a human message, "this number is wrong," with no event to anchor to.

vs. Cleric, Resolve and enterprise AI SRE

Built for big orgs, sold by a sales team.

Them

Six-figure contracts, a demo call, a pilot, and a platform team to justify it.

Treap

Self-serve, flat $149 a month. Connect read-only access and run an investigation today.

Treap is Cleric and Resolve for the rest of us. The read-only investigator for 10 to 50 person SaaS teams, priced flat and self-serve, not six-figure and sales-led.

You are not handing prod to a black box.

Read-only by design

Treap connects with read-only, scoped credentials you issue. Its toolset has no write, deploy, or mutate actions, and every action it takes is a read, logged in full.

Bring your own key

Point Treap at your own LLM key. Your code and data are used to investigate, never to train a shared model.

Self-host option

Run it in your own VPC if you would rather nothing leaves your network. Scoped credentials, full audit log of every read.

Pricing

One plan. That's it.
$149 / month per team

No per-seat pricing. No usage overages. No sales call.

  • Unlimited investigations
  • Every engineer, no per-seat fee
  • Read-only connectors and incident memory

Stop doing manual archaeology.

Get on the early-access list. I will reach out personally before launch, and design partners get the first real investigations.