Drop a Config. See Your Risk.

Upload your YAML or JSON service definition and get a scored reliability assessment in seconds — the same 8-rule engine that powers the dashboard. Open-source workflow for technical validation. Take it private for regulated environments.

📁

Drop your YAML or JSON file here

or click to browse (max 1MB)

Example Configuration — this config has 2 critical findings. Try it.

services:
  - name: order-router
    tier: 1
    az_count: 1
    has_failover: false
    has_circuit_breaker: true
    slo_target: 0.999
    dependencies:
      - market-data-gateway
      - risk-engine
  - name: market-data-gateway
    tier: 1
    az_count: 1
    has_failover: false
    slo_target: 0.9999

Need private deployment or data-isolation controls for a regulated environment? Start an enterprise pilot.

Analyzing your configuration...

Scanning services...

0

F

Risk Score

Critical Findings

Service Dependencies

Recurrence Warnings

Recommendations

See the full picture

The dashboard shows the same engine against a dependency-dense trading environment. For enterprise buyers, it becomes the leadership view of critical-path exposure, blast radius concentration, and remediation priority.