Home / Directory / AI SaaS tooling / AI incident & on-call / Cleric

Cleric

AI site reliability engineer that checks each production change, investigates alerts down to root cause, and opens fix pull requests for approval.

7.7/10
Overall Score
Recommend

Cleric follows each change into production and investigates regressions while the change is still fresh, so on-call engineers get a cause and a fix instead of a raw alert.

Best for

Platform and SRE teams running Kubernetes and cloud services who want an AI agent to triage alerts and verify releases in Slack.

Not ideal for

Small teams with few alerts, or organizations that will not let an AI agent read production telemetry.

Verdict

Cleric is an AI site reliability engineering company led by co-founder and chief executive Shahram Anver, who earlier led engineering for the MLOps, DevOps, and FinOps platforms at Gojek, and co-founded with Willem Pienaar, creator of the Feast feature store. Engineering teams connect it to their observability tools and Slack so it can verify each deploy, investigate alerts, explain the root cause, and open a fix for a human to approve. It matters because AI coding tools ship more changes than on-call engineers can watch, and Cleric checks each one in production.

Score Breakdown

How Cleric scores in the categories that matter to its buyers.

Buyer outcomes

Root-cause accuracy
8.0
Change verification
7.9
Integrations and memory
7.8
Cost predictability
6.9

Company & commercial

Innovation & product leadership
7.8
Project management & communication
7.7
Pricing
7.5
Contract fairness
7.6

Pricing

Cleric prices in credits for completed work. Credits cost $0.50 on monthly plans, and every plan includes unlimited users and all integrations.

PlanPriceWhat stands out
Team$700 / month1,400 credits, change regression checks, investigations in Slack and web
Pro$1,500 / month3,000 credits, scheduled agents, private resource connector, SAML
Scale$3,000 / month6,000 credits, shared Slack channel with Cleric engineers
EnterpriseCustomAnnual credit pool, custom retention and region, DPA

The Field at a Glance

How Cleric compares with other AI incident & on-call vendors we reviewed, by Overall Score and relative typical engagement cost.

6 7 8 9 Overall Score $ $$ $$$ $$$$ Relative typical engagement cost incident.io Rootly ilert Cleric 7.7
Cleric incident.io Rootly ilert

Cleric scores 7.7 in AI incident & on-call, under incident.io (8.2) and Rootly (8.0), and ahead of ilert (6.9). Relative cost lands upper-mid for this subcategory.

Use-case matrix

Use caseFitNotes
Alert triage and root causeStrongInvestigations trace alerts across logs and dependencies.
Verifying deploysStrongEach change costs 2 credits to verify in production.
Teams working in SlackStrongFindings and fixes post in the incident channel.
First response on callStrongCleric takes the pager, dismisses false positives, and proposes fixes for confirmed issues.
Fixed monthly budgetsMixedCredits make heavy weeks cost more.
Teams with few servicesWeakThe Team plan starts at $700 a month.

Who it’s for

Good fit

  • SRE teams buried in alerts
  • Companies shipping many AI-written changes
  • Platform teams on Kubernetes

Poor fit

  • Small teams with quiet systems
  • Buyers who want a flat per-seat price
  • Shops that block AI access to telemetry

Review Excerpts

Below are excerpts from public reviews. Our team scoured public reviews, forums, and chat rooms to get a balanced view of customers' experience with this company. Paid reviews and pay-for-play sites such as Clutch were excluded.

How it's used

“No one’s going to the Cloudflare dashboard anymore. No one’s going to the Datadog dashboard anymore, even though they’re set up. The go-to is Cleric.”

Affaf Ahtisham, Head of Engineering, LaunchGood · source
What people like

“The team loves Cleric. The biggest challenge isn’t finding ways to use it, it’s deciding where to use it next. It consistently helps us uncover issues faster and shorten the path from problem to solution.”

Priya Sawant, SVP of Engineering, ASAPP · source
What people don't like

Cleric bills in credits: 10 for each issue investigation, 2 for each verified change, and 1 per started minute of chat, so a busy incident week uses more of the monthly allowance.

Product fact · Cleric pricing

Methodology

This page is an independent evaluation of Cleric for buyers comparing options in ai incident & on-call. AI Industry Reviews accepts no sponsorships, advertising, or pay-for-placement fees. Cleric did not pay for this review.

What we scored

The headline number is an Overall Score on a 0-10 scale. Eight criteria sit under it in two groups.

  • Buyer outcomes (for ai incident & on-call)
    • Root-cause accuracy
    • Change verification
    • Integrations and memory
    • Cost predictability
  • Company & commercial
    • Innovation & product leadership
    • Project management & communication
    • Pricing
    • Contract fairness

Pricing measures whether the price looks fair for the value delivered, including packaging and renewal friction that show up in real buying cycles.

Score Composition

InputWeightWhat it covers
Reviews40%A proprietary read of what practitioners say about likes, complaints, and day-to-day use, including public review sites, forums, and private chat rooms. Paid reviews and pay-for-play sites such as Clutch are out of scope.
Product35%Hands-on look at screens and workflows.
Pricing15%Whether the price looks fair for what you get.
Docs & training10%Docs, tutorials, and training material.

How we balanced the evidence

The Overall Score is the simple average of the eight criteria. Recommendation language follows that score and the fit pattern described above.

Scope

Cleric is graded here as ai incident & on-call. Criteria scores can move as more review volume and product checks are added.

← Back to AI incident & on-call