open source technical support

The AI support engineer.Built to reproduce the failure before it answers.

join the waitlistsource · coming soon
  • for api-first teams
  • open source
  • self-hosted
reproloop · ticket #4821reproducingverified
12:03:41 ticket #4821 · webhooks returning 401 · sev-2
12:04:05 correlate · 401s match · candidate POST /v1/messages
12:05:12 sandbox replay (mock from openapi) · reproduced 401
12:06:03 cause: signing secret rotated 09:07 · config error
12:07:10 verify · fix replay with rotated secret · 200 ok
12:07:23 verified · reply drafted with sandbox evidence

Illustrative trace.

every reply checked before it ships

01reproduce

Most support AI answers from similar tickets. Reproloop reproduces yours.

A customer reports a request that fails. A general agent searches old tickets that look similar and sends its best guess. Reproloop is built to run the customer's exact failing request in a safe test copy of your product - watch it fail, apply the fix, watch it pass. The difference between "try this" and "it's fixed."

failure reproduced

an example ticket, answered two ways

ticket #4821 · webhooks returning 401sev-2
A general agent

Hi! 401 errors are usually caused by an expired API key. Try regenerating your key in the dashboard and updating your integration. Let us know if that helps!

drafted from similar tickets · never tested

Reproloop

Your webhook signing secret was rotated yesterday at 09:07. Calls signed with the old secret fail with 401. Update the secret in your webhook settings - we reproduced the failure in a test copy of your setup, and with the secret updated, the same call passes.

reproduced · fix proven · checks passed

02diagnose

A verified resolution is not a suggestion.

The answer keeps the proof that produced it: the test that reproduced the problem, the run that shows the fix works, and the record of the check it passed.

audit trail retained

Every decision keeps its evidence.

  • The docs and code the answer drew on
  • The test run that reproduced the bug
  • Its confidence, and the check it passed
  • Whether it replied or handed off to you
the final check

Every ticket ends one of two ways.

Deliver when verifiedEscalate when uncertain

It never guesses.

the verification record
ticket #4821 · webhooks returning 401
reproduced ✓ - the failing call, seen failing
fix proven ✓ - same call, run again: passes
checks passed ✓ - nothing unverified in the reply
result: VERIFIED · sent to the customer

if any line fails, the ticket goes to a human instead.

03resolve

Three stages, every ticket.

01 / reproduce

See it fail.

Built to run the customer's exact failing request in a safe test copy of your product, until it sees the same failure itself.

02 / verify

Prove the fix.

It finds the cause, applies the fix, and runs the same request again. The reply does not go out until that run comes back green.

03 / answer

Show the work.

Your customer gets what broke, why it broke, and the fix that was proven against their own failing request.

04verify

Everything is open to check.

Reproloop core will be open source under AGPL v3 - read every line and run it on your own servers. And our public benchmark tests every support AI, including ours, on 300 real tickets where the answers are hidden. Public results are coming soon.

  • 300 public test tickets
  • answers locked away
  • reproducible by anyone
Open source

Self-host the core.

Deploy with Docker Compose and run the whole thing on your own servers.

Reproloop Cloud

Or let us run it.

Reproloop Cloud runs the same open core, so you do not have to.

05deliver

Be first in the queue.

We are onboarding a small group of API-first teams. Join the waitlist and we will be in touch.

RESOLVED · VERIFIED