Every enterprise has monitoring. Almost none have root cause.
Onepane exists to deliver the root cause, not the tooling to find it. After a Sev1, engineers spend hours reconstructing what happened across five tools and another day writing the RCA someone is waiting on. We do that work, agents investigate inside your VPC, our engineers sign off, and the finished, evidence-linked RCA arrives inside an SLA.
Why does root cause still get done by hand?
Two decades of monitoring, observability and AIOps spending produced better dashboards and faster alerts. It did not produce the document. When a Sev1 closes, the investigation across tools and the write-up for the customer, the regulator or the review board are still human labour, expensive, late, and dependent on whoever happens to know the estate.
The tools that promised to change that mostly sold software the buyer then had to staff, or investigated only their own vendor's data, or could not be deployed where the data was allowed to be. We started Onepane to sell the outcome instead: a managed root-cause service that runs on the observability you already own, inside your VPC, with an SLA.
The analogue is what managed detection and response did for the SOC, sat on the customer's existing tools, sold investigated detections against an SLA, displaced analyst headcount rather than the tooling. We are doing that for the NOC, and the deliverable is the root cause. See how it works.
Where is Onepane based, and what exactly do we sell?
| Headquarters | United States. Founder in San Diego, CA; commercial lead in the San Francisco Bay Area. Registered office at 355 Bryant St, Suite 403, San Francisco, CA 94107. |
| Support and jurisdiction | US entity, US-timezone support, US jurisdiction. Stated plainly in security and procurement reviews because it removes a class of vendor-risk objection before it is raised. |
| What we sell | A managed root-cause service, RCA as a Service. Priced per service under coverage plus accepted RCAs, with an SLA and credits. Never per seat, per host or per gigabyte. |
| Deployment model | Customer VPC, AWS, Azure or GCP, via a Terraform or Helm reference deployment. Not SaaS. Telemetry stays in your account; anything that egresses is disclosed in writing. |
| Artifacts | Root Cause Report, Executive Incident Summary, Customer-Facing RCA, Evidence Pack, Change Attribution Record, Service and Ownership Snapshot, Confidence and Abstention Statement, Problem Record Payload, plus the periodic and trust artifacts. Generated today, not on a roadmap. |
| Contact | arun@onepane.ai |
Deployment details at Deploy in your VPC. Full artifact set at /artifacts.
What do we publish even when it doesn't flatter us?
The last generation of vendors in this space oversold. In a category with that history, transparency is the differentiator that compounds, so four numbers go to every customer monthly.
Accuracy against your own historical RCAs
In the replay and after: what we concluded versus what the human actually wrote, scored on the cause and on time-to-cause.
Abstention rate
How often we said 'insufficient evidence, here is what is missing' instead of guessing. A number that goes to zero is a warning sign, not a success.
Time-to-RCA against the committed SLA
The SLA Attainment Report is published to every customer monthly, whether or not it flatters us. It is what proves we are a service and not software.
Percentage of RCAs with zero human touch
Reported per account, trending up honestly. An expert pod behind the service early is normal; it must visibly decay over time and we will show that it does, or that it does not.
These are delivered as the SLA Attainment Report, the Coverage and Autonomy Report and the Replay Bake-off Report.
What we are not.
The words decide which buyer we meet and which budget pays us. So we are precise about them.
- 01 Not a chat-first incident-investigation tool sold to engineers under a software subscription.
- 02 Not a legacy AIOps correlation platform you deploy, tune and staff.
- 03 Not an observability product, and not a replacement for the monitoring you already own.
- 04 Not SaaS: we do not ask you to send us your logs.
- 05 Not autonomous action on production: we deliver evidence-backed decision support with human sign-off, and we do not promise autonomy percentages we have not earned.
What we are: a managed root-cause service, Autonomous Problem Management for ITIL-mature enterprises. Comparisons at /compare.
What are our rules of engagement?
No pricing before the replay
Pricing without proof anchors low and destroys the outcome narrative. We run the 90-day replay first because it tells both of us how much investigation and authoring labour we would actually displace, and that is what the price should be based on.
We never speculate about your outage
If we reach out after a public incident, it is one sentence and then the general problem. We do not guess at your cause in public or in private, and we do not use your incident as marketing.
We disclose egress in writing, unprompted
If anything at all leaves your environment, service heartbeats, aggregate metadata about our own service, you get the data-flow diagram before you sign, not after a reviewer asks.
Change is 'what changed', never 'who broke it'
The Change Attribution Record names the deployment, config change or cloud event and its approver. It is written to inform, not to assign blame, because a service that creates enemies inside your organisation does not last.
We say no early
Sub-scale estates, single-vendor stacks, teams with no one waiting on the RCA: we tell you in the first call rather than in month six. See who it's for.
Segments we work with, and the ones we turn away, at Who it's for.
Talk to us.
Email: arun@onepane.ai
Office: Onepane Inc., 355 Bryant St, Suite 403, San Francisco, CA 94107, United States
Presence: San Diego and the San Francisco Bay Area. US-timezone support.
Fastest way to start: the 90-day replay. Not a demo, and no pricing until it is done.
Company, the questions.
What does Onepane do?
Onepane is a managed root-cause service for enterprise IT operations. Software deployed in your VPC connects to the observability, change and ITSM tools you already own; agents investigate every Sev1; our engineers sign off; and you receive the finished, evidence-linked RCA artifacts inside a committed SLA. Priced per service under coverage plus accepted RCAs.
Where is Onepane based?
Onepane is US-headquartered, with the founder in San Diego and the commercial lead in the San Francisco Bay Area. Registered office at 355 Bryant St, Suite 403, San Francisco, CA 94107. Support and jurisdiction are US.
Is Onepane SaaS?
No. Onepane deploys into your own VPC on AWS, Azure or GCP. Telemetry, logs, traces and change data stay in your account under your keys; model inference runs inside the boundary; anything that egresses is disclosed in writing.
How do we start working with Onepane?
Send your last 90 days of Sev1 tickets through the replay page. We show what we would have found, how fast, and what the document would have looked like, scored against the RCA a human actually wrote. Two weeks, no cost, no pricing conversation first. Or email arun@onepane.ai.
Meet us on your own incidents.Not on a sales call.
Send us your last 90 days of Sev1 tickets. We show what we would have found, how fast, and the document you would have received. Two weeks, no cost.