Cleric
Cleric is an AI SRE that investigates production alerts, performs root cause analysis, and builds a knowledge graph from every resolution so future incidents finish faster. Built for SREs, engineers, and engineering leaders managing Kubernetes, microservices, and cloud infrastructure.
Use Cases
Investigate production alerts and surface root cause analysis
Automate on-call triage and incident escalation
Diagnose Kubernetes and microservice failures
Debug deployment and CI/CD failures
Capture institutional knowledge from past incidents
Recommend fixes inside Slack during active investigations
Pros
Read-only by default with explicit write-access opt-in
Builds a knowledge graph of services and dependencies automatically
Tests hypotheses in parallel rather than guessing one cause
Every resolution feeds team-wide institutional memory
SOC 2 Type II with regular manual penetration testing
Cons
Demo-only signup with no free or self-serve tier
Read-only default means fixes still need human review to ship
Limited public pricing information until you book a demo
Knowledge graph value depends on alert volume to compound
Competes with native AWS, Datadog, and PagerDuty SRE agents in those stacks
Platforms
Web
Chatbot
Compliance & Certifications
SOC 2
AICPA
What makes Cleric different from the AWS or Datadog SRE agents is that every investigation feeds a knowledge graph, so the second time the same alert hits your team you've already solved it. Read-only by default is the right call, but it means every fix still needs a human to push the button.
Solid Choice