Send us your last 90 days of Sev1s. We'll show you what we would have found.
The 90-day replay is how Onepane asks to be evaluated: we re-investigate your own recent Sev1 incidents inside your environment, produce the RCA artifacts we would have delivered, and score them against what your team actually wrote, on accuracy and time-to-cause. Two weeks. No cost. Not a demo.
Two weeks, no cost, no production changes. Tell us a little about the estate and we'll come back within one business day with the intake steps and an NDA.
One exercise, four jobs.
You see the actual RCA documents for your actual incidents, not a demo on synthetic data.
Time-to-cause on your telemetry tells us, and you, what window is realistic.
That is the pricing input. It's why we don't quote before the replay.
The comparison is against the human RCA, not another vendor's polished walkthrough.
How does the replay work?
You send the tickets. Your last 90 days of Sev1/Sev2 tickets and the RCAs your team actually wrote, under NDA. Read-only access or an export, no production changes.
We connect, read-only. Scoped access to the observability, change and topology sources for those incidents. Where access isn't possible we work from exports.
Agents replay each incident. The same investigation we'd run live: change history, topology, telemetry, causal chain, evidence index. Engineers review; abstentions are recorded.
We score against the human RCA. Per incident: our cause vs what your team wrote, time-to-cause, confidence, and where we abstained and why.
You get the reports. The Replay Bake-off Report, the RCA Readiness and Telemetry Coverage Report, and sample artifacts for two or three real incidents, yours to keep whether or not you buy.
Six questions we ask on every first call.
If you can answer four of them from memory, the replay will be worth your time.
About the replay.
What is the 90-day replay?
You send us your last 90 days of Sev1 tickets. In about two weeks, at no cost, we show you what we would have found, how fast, and what the RCA document would have looked like, scored against what your team actually wrote. It is the only way we ask to be evaluated. Not a demo.
Why not just a demo?
A demo shows our data. The replay shows yours. It proves the outcome before we charge for one, sets the SLA we can safely commit to, quantifies the labour we'd displace, and beats any demo a competitor can run, because the comparison is against the human RCA, not another vendor's walkthrough.
What do we need to provide?
Under NDA: the tickets and RCAs for the period, and read-only access, or exports, from the observability, change and topology sources involved. No production changes, no agents installed on hosts.
What do we get if we don't buy?
The Replay Bake-off Report and the RCA Readiness and Telemetry Coverage Report, which services are instrumented well enough for a confident cause, and which blind spots cap accuracy. Most teams say the coverage report is the most useful artifact of the evaluation.
Will you quote pricing before the replay?
No. Pricing without proof anchors low and destroys the outcome narrative. The replay tells us how much investigation and authoring labour we would actually displace, and that is what the price should be based on.
How long does it take?
About two weeks from access to readout, depending on how many incidents and how quickly access is granted.