Overview
Alert breaches become a written root-cause analysis: timeline, span table, remediation commands and prevention. It reads traces, logs and metrics, then the codebase, your cloud and cluster, and configuration and flag state. Advisory by design — it never executes anything itself.
Key features
- Reads traces, logs and metrics for the breach
- Then the codebase, your cloud and cluster, and feature-flag state
- Writes a timeline, span table, remediation commands and prevention
- Advisory by design — a human runs every command
Example: frontend product view failure
Generated in 11s from a SEV-2 alert on frontend. Verdict: deliberate failure from an enabled feature flag. What it read before writing:
Traces
6-span failure chain
Logs
explicit error message
Metrics
error rate per service
Codebase
GetProduct call path
Cloud & cluster
AWS · GCP · Azure · Kubernetes
Feature flags
flagd state — the actual cause
- alert
- STATUS_CODE_ERROR in frontend
- trace
- 5f77bac6a9c6c988fa87b46ee353f07f
- failing span
- oteldemo.ProductCatalogService/GetProduct
- endpoint
- /api/products/[productId]
- status message
- Product Catalog Fail Feature Flag Enabled
- feature flag
- flagd · product-catalog-fail = true
- infrastructure
- ruled out — not infra, not a code bug
Delivery
AI Remediation & RCA is part of the full platform in both delivery models — there is no cut-down edition.
SaaS · Fully managed
We run the platform, handle upgrades, scaling and backups. You point your collectors at an endpoint and start asking questions the same afternoon.
PaaS · Your infrastructure, our platform
The full platform deployed into your own Kubernetes clusters or VMs, with telemetry never leaving your network boundary. We operate and support it where you host it.