Cleric is an AI‑driven SRE assistant that automatically investigates alerts, maps services, dependencies, and ownership, and delivers evidence‑backed root‑cause analyses to engineering teams within minutes. It presents a transparent hypothesis tree of its reasoning, integrates via read‑only APIs into existing tooling such as Slack, and continuously learns from past incidents to improve diagnostic accuracy.
Funding
Funding not disclosed
Founders
Product
Problem
Engineering teams spend extensive time manually investigating alerts, correlating logs, metrics, and service dependencies to identify root causes, which delays incident resolution and reduces productivity.
Solution
Cleric provides an AI-driven SRE assistant that automatically initiates investigations as soon as an alert fires. It builds a real‑time map of services, dependencies, and ownership, then formulates and tests multiple hypotheses using logs, metrics, traces, and historical incident data. The system captures its reasoning in a transparent hypothesis tree and delivers an evidence‑backed diagnosis directly to the team’s messaging platform (e.g., Slack) within minutes. Over time, Cleric extracts diagnostic patterns from each incident, continuously improving its accuracy across services and teams without manual rule updates. The solution runs in a read‑only mode, integrates via APIs, and keeps all data within the customer’s environment.
Target Audience
Primary customers are Site Reliability Engineering (SRE) teams, DevOps engineers, and platform engineering groups that manage complex, microservice‑based production environments.
Features
- Automatic, real‑time mapping of services, dependencies, and ownership from logs, metrics, traces, Kubernetes state, and internal documentation
- Hypothesis‑driven investigation engine that forms, tests, and ranks multiple root‑cause theories using data across the stack
- Transparent hypothesis tree showing step‑by‑step reasoning for each diagnosis
- Immediate delivery of evidence‑backed root‑cause reports to Slack (or other messaging platforms) tagged to the responsible service owner
- Continuous learning that captures reusable diagnostic patterns from past incidents and applies them across services and teams
- Secure, read‑only deployment via API integration; no agents or code changes required and no data leaves the customer environment