Know the blast radius before customers feel it
Raincurve scores emerging conditions, estimates what they will take down and ranks them by operational impact — so the right problem gets attention first.
Every dashboard is red. Which one matters?
Degradations rarely announce themselves as outages. A rising error rate on an optic, a slow drift in a queue, a GPU throwing correctable errors — most are harmless, a few are the start of an incident. Teams triage by severity labels that know nothing about what sits downstream.
Raincurve ranks conditions by consequence: which services, tenants and redundancy margins depend on the thing that is degrading, and how likely it is to fail.
From signal to impact
Score
Every signal gets a continuous risk score from the Curve-1 pre-filter, so rare, dangerous patterns stand out from routine noise.
Relate
Trajectory encoding compares the current sequence of events to known failure trajectories across layers.
Project
The dependency graph projects the condition forward: which paths, services and tenants lose redundancy or capacity.
Prioritize
Conditions are ranked by likelihood × impact, with the next responsible action attached.
Redundancy is a number, not a diagram.
For every endpoint Raincurve computes resilience — the number of device-disjoint paths to the core. A condition that takes a server from two paths to one is flagged before it becomes an outage, even when everything is still reachable.
Because the computation is a single linear-time graph pass, it stays current on estates with tens of thousands of devices.
0.9136 servers lose redundancy · 2 tenants
0.644 inference endpoints at risk
0.22base-rate event · no downstream impact
0.08single-homed test host
Research
Method, results and limits for the techniques on this page.
Curve-1: a reasoning architecture
The four-stage pipeline behind cross-layer root-cause ranking.
Read paper →ResearchProving a network action is safe before it runs
Exact graph checks: zero unsafe approvals, 14,680 devices in 0.19 s.
Read paper →DocumentationPlatform concepts
Topology graph, contracts, hypotheses, incidents and verification.
Open docs →