Dashboard Run Audit Enterprise Help

How ReliOp Works

Find the risks most likely to cause your next production incident — before they spread.

1
See Your Highest-Risk Failure Point

Upload a YAML or JSON service definition.

ReliOp scores it and surfaces the issues most likely to trigger an incident — with clear fix hints.

2
See the Blast Radius

Map dependencies across your service chain.

Understand exactly how far a single failure spreads — and which systems are at risk.

3
Fix What Matters First

Findings are ranked by impact, not noise.

Focus engineering time on the issues that reduce the most risk, fastest.

No agents · No production access · Config-first · Built for regulated environments
What You Get
Identify Hidden Failure Risks
Surface configuration gaps, missing safeguards, and single points of failure before they break production.
Turn Risk into a Response Plan
Generate actionable remediation steps before incidents happen — not during them.
Learn from Past Incidents
Capture and reuse reliability patterns so the same failure doesn't repeat.
Quantify Outage Exposure
Understand potential blast radius and business impact — so leadership can prioritize effectively.
FAQ
ReliOp is a pre-incident reliability intelligence platform. It analyzes service configurations to identify what is most likely to break — and how far failures will spread — before incidents occur.
Observability tells you something is wrong after it happens. ReliOp shows:
  • what breaks next
  • why it breaks
  • how far it spreads
ReliOp uses configuration and infrastructure definitions such as:
  • YAML / JSON service configs
  • Kubernetes manifests
  • Terraform / IaC
  • Architecture docs (enterprise)
No runtime telemetry is required.
No. ReliOp is fully config-first:
  • No agents
  • No instrumentation
  • No production access
You can get value in minutes by uploading configs.
Yes.
  • No direct production access
  • Works on declarative configs
  • Can run in your environment (enterprise)
Designed for regulated environments like financial services.
ReliOp produces:
  • Risk findings (ranked by impact)
  • Dependency / blast radius mapping
  • Fix recommendations
  • Prioritized remediation list
  • SRE teams
  • Platform / infrastructure engineers
  • Engineering leadership
  • Regulated environments (finserv, fintech, etc.)
Minutes. Upload a config and get a risk report immediately.

Enterprise deployments typically show value within weeks.
No. Even partial configs provide meaningful insight. A small set of services can reveal critical risks and dependency gaps.
Not by severity alone. Issues are ranked based on:
  • Blast radius
  • Likelihood of failure
  • Downstream impact
This focuses effort on what actually reduces risk.
ReliOp has an open-source core you can self-host, inspect, and extend. The core is portable so teams can validate the workflow without lock-in. Companies that need private deployment, rule calibration, or regulated-environment delivery can engage on an enterprise basis. See Enterprise for details.
Yes (Enterprise). Outputs can align with:
  • Incident tools
  • Runbooks
  • Internal workflows
Using ReliOp
The Operational Reliability Risk score ranges from 0 (no issues) to 100 (critical). It's severity-weighted — CRITICAL findings contribute far more than LOW ones. Under 30 is healthy, 30–59 is moderate and worth reviewing, and 60+ means findings that need prompt attention.
Blast radius measures how many downstream services would be affected if a given service fails. ReliOp traces the dependency chain and counts every system that depends — directly or transitively — on that service. A blast radius of 8 means an outage would ripple across 8 other services.
The graph maps every service-to-service dependency in your architecture. Node color reflects risk level — green is clean, yellow has medium findings, red has critical issues. You can drag nodes, zoom, and hover for details. The layout reveals which services are tightly coupled and where a single failure could cascade.
ReliOp runs 8 rules against your services: SLO breach trending, missing cross-AZ failover, missing circuit breakers, retry storm risk, single-owner risk, incident recurrence, missing saturation metrics, and dependency fan-out limits. Each rule produces findings at CRITICAL, HIGH, MEDIUM, or LOW severity.
Go to Run Audit in the navigation. Drop in a YAML or JSON file describing your services. Include fields like name, tier, owner, SLO targets, and dependencies. ReliOp runs the full rules engine and returns a scored report with actionable findings.
YAML or JSON with a list of service definitions. Each service should include: name, tier (e.g. tier-1), owner, slo_target, slo_current, dependencies (a list of service names), and optionally deployment info like az_count.
Tiers reflect business criticality. Tier 1 is revenue-critical or customer-facing infrastructure — services where downtime directly impacts users or revenue. Higher tier numbers indicate supporting or internal services. ReliOp weighs findings on Tier-1 services more heavily since their failures have the broadest impact.
When you click "Generate Response Plan" on a critical issue or blast-radius hotspot, ReliOp builds a structured incident runbook for that service. It includes immediate response steps, blast-radius containment actions, a communication template, and a post-incident checklist — actionable steps, not a generic playbook.
Only if you opt in to an external AI provider. Even then, ReliOp strips all service names, owner info, and internal identifiers before sending. The LLM only sees anonymized patterns. For full data isolation, use the local provider — zero data leaves your network. AI insights are off by default.
Find Your Risk in Minutes
Upload a service config and see what breaks next.
Run Audit →
Monitoring tells you something broke. ReliOp tells you what breaks next.