Cleric
AI SRE for investigating production incidents, proposing fixes, and verifying outcomes inside an existing operations stack.
About Cleric
Cleric is an AI SRE built for production operations. It turns alerts, support tickets, and ad hoc requests into structured investigations, then groups alerts that share a root cause. The agent tests hypotheses against logs, metrics, traces, deployments, and prior incidents. Its output includes evidence, a proposed fix, and verification steps that fit into an existing engineering workflow. Cleric connects through standard CLIs and APIs, including Datadog, PagerDuty, GitHub, Slack, AWS, GCP, and Kubernetes. Access is read-only by default; selected actions, such as creating a Jira issue, can require write permission. Completed investigations feed an operational knowledge graph, giving later investigations context about recurring failures and system behavior. Pricing is based on completed Issues and Custom Work rather than token consumption. Teams can run a 14-day pilot in their own production environment before signing an annual agreement. Team costs $2,000 per month, billed as $24,000 per year, and provides 1,000 monthly credits for up to 100 Issues or a mix of Issues and Custom Work. Enterprise pricing and credit allocation are negotiated. The annual commitment and integration work make Cleric a closer fit for organizations with sustained on-call pressure than for teams seeking a lightweight alert summary tool.
Best for
Best use cases
An alert fires and the team needs hypotheses tested against logs, metrics, and traces.
Several alerts point to one failure and need to be grouped into a single investigation.
A proposed production fix needs evidence and verification before the incident can be closed.
Compare before choosing
Costs are tied to completed Issues and Custom Work instead of metered token consumption.
Read-only access is the default, with selected write permissions reserved for enhanced actions.
The annual Team commitment is substantial compared with lightweight alert summarizers or manual tooling.
Features
Alert investigation
Start an investigation when an observability, cloud, or CI/CD alert fires and return evidence with next steps.
Root-cause analysis
Test competing hypotheses against logs, metrics, traces, deployment context, and previous incidents.
Production fix verification
Propose a fix and carry the investigation through verification within the team’s normal operating workflow.
Pros
- Groups related alerts and tests causes against multiple telemetry sources, reducing repeated manual triage.
- Uses common infrastructure integrations and defaults to read-only access, which can simplify initial deployment.
- Charges for completed Issues and Custom Work instead of token usage, making the unit of work easier to evaluate.
Cons
- The Team plan requires a $24,000 annual commitment, which may be difficult for smaller operations teams.
- Useful investigations depend on credentialed access to production systems and careful integration setup.
- Some enhanced actions require write permissions, adding security review and access-control work.
Pricing Plans
Team
- 1,000 credits per month
- Up to 100 Issues per month, or a mix of Issues and Custom Work
- Investigation agent, knowledge graph, and verification engine
- Datadog, PagerDuty, GitHub, Slack, and additional integrations
- Custom Agents, Scheduled Monitors, and Slash Commands
- Google Workspace SSO and business-hours email support
Enterprise
- Custom credit allocation
- Negotiated credit rate sized for an organization-wide rollout
- Deployment across many teams
* Pricing information is for reference only. Please refer to the latest announcement on Cleric's official website.