Cleric is live · pricing from $700/mo · last verified 24 Oct 2026 · viability healthy
Cleric
Cleric is an AI SRE agent that verifies production changes for up to 14 days and opens fix PRs when they regress.
Most AI SRE tools stop when the diagnosis lands. Cleric keeps watching the change for up to 14 days and then re-checks the deployed fix against live metrics, which is the part that decides whether you get paged again. At $1 per verified change and $5 per Issue on a $0.50 credit, the metering matches the work rather than a token bill. If bad merges cost you real money and you already run Datadog or Prometheus with PagerDuty, the 1,000 evaluation credits are a cheap test; compare against PagerDuty SRE Agent, Bits AI SRE and Azure SRE Agent if you mainly want triage.
Verdict generatedVerified 6d ago · liveness 79/100 · cite: rightaichoice.com/tools/cleric
- SRE and platform teams shipping often who need regressions caught days after deploy
- Organizations drowning in alerts where most pages close as false positives
- Teams that want per-work credit pricing ($1 per change, $5 per Issue) instead of token bills
- Engineering orgs that want incident knowledge to compound through operational memory
- Teams without observability signal for Cleric to investigate or verify against
- Small shops with low change frequency where 1,400 monthly credits is overkill
- Anyone wanting a basic paging tool rather than AI investigation and fix PRs
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Cleric if you deploy a few times a month, have no Datadog or Prometheus signal for it to read, or need private-endpoint access and SSO but won't fund the $1,500/mo Pro tier.
Chats bill one credit per started minute after the first 30 seconds free, so a long back-and-forth investigation can cost more than the $5 Issue that spawned it.
Fits mid-size platform teams: $700/mo buys 1,400 credits (roughly 1,400 verified changes or a mix of ~140 Issues), which is sane for a team shipping dozens of times a week. Small shops are better served by the 1,000 free evaluation credits or by PagerDuty's bundled AI add-ons; large orgs needing SSO, private networking and audit logs should budget $1,500/mo Pro or Scale at $3,000/mo rather than trying to hold Team.
In short
Cleric — Cleric is an AI SRE agent that verifies production changes for up to 14 days and opens fix PRs when they regress. Best for SRE and platform teams shipping often who need regressions caught days after deploy, Organizations drowning in alerts where most pages close as false positives, Teams that want per-work credit pricing ($1 per change, $5 per Issue) instead of token bills. Plans from $700/mo.
No head-to-head comparison for Cleric yet — the alternatives below are the closest matches we list.
What is Cleric?
Cleric — Cleric is an AI SRE agent that verifies production changes for up to 14 days and opens fix PRs when they regress. Best for SRE and platform teams shipping often who need regressions caught days after deploy, Organizations drowning in alerts where most pages close as false positives, Teams that want per-work credit pricing ($1 per change, $5 per Issue) instead of token bills. Plans from $700/mo.
Cleric is an AI SRE agent for platform, SRE and on-call teams who want fewer pages and proof a fix actually held. It splits each release into production changes — usually one per pull request — and follows each one for up to 14 days, watching product metrics such as cart load p95 alongside system signals and infrastructure limits. Each change costs 2 credits ($1) and an Issue investigation costs 10 credits ($5). When a change drifts, Cleric opens a fix PR for review with every line tied to the production data behind it, then re-checks the deployed fix against live metrics until recovery. Issue investigations run the same loop in reverse: an alert, scheduled monitor or failed deploy becomes an Issue where Cleric returns a root cause with correlated signals attached as evidence and a proposed fix. Repeat alerts join the open Issue at no extra charge. Cleric cites 58% of alerts closed without an engineer and 51% of resolutions that applied its fix. Operational memory stores service relationships, infrastructure patterns, team guidance and prior results so later investigations start with context. Custom agents carry their own instructions and alert routing rules; scheduled agents post results into Slack. The product runs in Slack, Microsoft Teams or the web app, and MCP works both ways — drive Cleric from Claude Code or Cursor, or connect your own MCP servers. The Cleric Connector runs inside your network for approved private endpoints. Read-only by default, every action logged, SOC 2 Type II with regular manual pen testing, and EU hosting available. Cleric was named a Gartner Cool Vendor in AI for SRE and Observability.
Key features
- Change verification: follows each production change for up to 14 days
- Splits each release into per-PR changes and verifies each one
- Regression detection across product metrics, system signals and infra limits
- Fix PRs where every line links to the production data behind it
- Post-deploy verification of the fix against live metrics until recovery
- Issue investigation from an alert, scheduled monitor or failed deploy
- Automatic alert investigation that closes false positives before they page
- Root cause analysis with correlated signals attached as evidence
- Repeat alerts join an open Issue at no extra charge
- Operational memory of service relationships, infra patterns and prior results
- Custom agents with their own instructions and alert routing rules
- Scheduled agent runs that post results into Slack
- Slack and Microsoft Teams interfaces plus a web app
- MCP both ways: drive Cleric from Claude Code or Cursor, or connect your own MCP servers
- Cleric Connector runs inside your network for approved private endpoints
Behind the verdict
Cleric's pitch is narrow and specific, which is a good sign. The unit of work is the production change, not the chat session: it reads a merged PR, splits the release into per-PR changes, and keeps checking for up to 14 days — the demo on the site shows cart load p95 going from 182 ms to 511 ms after PR #1849, a fix PR reverting CHECKOUT_V2_STRICT_TIMEOUT opened in about nine minutes, and p95 back to 180 ms after deploy and verification. That close-the-loop step is where most AI SRE products quit, and it is the one that changes your page volume. The alert side is the same loop reversed. The homepage shows 47 alerts reaching Cleric in 24 hours, 41 closed as false positives, 5 investigated and fixed, and 1 escalated — with an INV ticket carrying seven attached signals so the engineer wakes up with findings rather than a blank dashboard. Because repeat alerts join an open Issue at no extra charge, the metered cost falls as incidents cluster rather than spiking. The honest weaknesses are about scope and money. This is not a code-authoring tool and it is not a paging replacement — you still want PagerDuty or similar routing underneath. Your value depends on having signal: Cleric collects evidence via kubectl, Datadog APIs, Prometheus queries and source code, so teams without an observability stack get little back. And the genuinely useful operational features — scheduled agents, the Cleric Connector for private endpoints, Okta/custom SAML, the audit log — start at Pro at $1,500/mo monthly, so small shops paying $700/mo on Team can hit that wall fast. Enterprise is annual-only. Engineering depth is visible in the blog: Cleric wrote up ranking agent investigation traces with pairwise Elo scoring after finding per-trace grading scored worse than chance, and posted on constraining agent action spaces just-in-time to cut agent cost and latency. That is the work of a team that runs agents in production, not a prompt wrapper. Fit it if you ship often, run Kubernetes with Datadog or Prometheus, and care whether the fix held; skip it if you're a five-engineer team with a handful of deploys a month.
Models under the hood
as of 2026-10-23
Limitations
- Pricing is credit-based and metered: 2 credits ($1) per verified change, 10 credits ($5) per Issue, 1 credit per started chat minute after the first 30 seconds free.
- Team is $700/mo for 1,400 credits/month, Pro $1,500/mo for 3,000, Scale $3,000/mo for 6,000 — all monthly; Enterprise is negotiated and annual billing only.
- Monthly credits roll over one month at up to twice the allocation; annual plans use a single annual pool, so a quiet month still spends down the pool.
- Several capabilities are gated: scheduled agents and monitors, the Cleric Connector for private resources, Okta/custom SAML/OIDC and the organization audit log start at Pro ($1,500/mo); a shared Slack channel with Cleric engineers starts at Scale; custom retention/region and a named CSM are Enterprise-only.
- Chat sessions auto-investigate and any other agent session bills per started minute, so heavy ad-hoc questioning adds up.
- Cleric is an AI SRE agent focused on change verification and incident investigation, not a code-authoring tool or a paging replacement.
as of 2026-10-24
Researching Cleric? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Is Cleric still active?
Cleric is live · pricing from $700/mo · last verified 24 Oct 2026 · viability healthy.
Viability score
How well maintained and how widely used is Cleric? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: October 2026
How we score →What's new in Cleric
Checked 10 days agoAcross the latest 3 updates: 3 news mentions.
Jev the Decider: JIT for Agents
Cleric blog post on constraining agent action spaces just-in-time to make agents faster and cheaper.
Roll for initiative: our week at AI Engineer World's Fair 2026
Cleric recounts its week at AI Engineer World's Fair 2026, framed around what happens after agent-written code is merged.
How Cleric ranks agent investigation traces with pairwise Elo scoring
Cleric describes ranking agent investigation traces by pairwise comparison and Elo score; per-trace grading scored worse than chance.
What do users say about Cleric?
What people actually say about Cleric — is it worth it?
We scanned public community sources for Cleric on Aug 24, 2026 and could not establish that the discussion we found is about this tool rather than something else sharing its name. Our own analysis of that scan says the posts were off-subject. Rather than publish a sentiment score built on the wrong subject, we publish nothing here and re-run the scan.
How we verified this
Every listed fact about Cleric— pricing, features, links, status — is re-read from the vendor's own pages by our verification pipeline and each change is logged with a date; the last pass ran on 24 Oct 2026. Pages mix model-assisted synthesis with human review; see how we verify.
Verification history
We have re-verified Cleric 21 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — changed pricing tiers, description, switching out, who should skip it, who it suits, setup time, our verdict, pricing fit, features, hidden costs, limitations, use cases, switching in
- — changed pricing page, limitations, platforms
- — changed integrations, pricing tiers, description, features, our verdict
- — changed pricing tiers, our verdict, features, who it suits, who should skip it, description, summary
- — changed pricing page
- — changed our verdict, who should skip it, pricing tiers, summary, who it suits, features, description
Showing the 6 most recent of 21 verification passes.
Free to cite with attribution — this page re-verifies continuously.
How much does Cleric cost in 2026?
Cleric: Plans from $700/mo. Pricing last verified 24 Oct 2026.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Where the pricing makes sense
The company stage and team size where Cleric's pricing actually pencils out — and where peers do it cheaper.
Fits mid-size platform teams: $700/mo buys 1,400 credits (roughly 1,400 verified changes or a mix of ~140 Issues), which is sane for a team shipping dozens of times a week. Small shops are better served by the 1,000 free evaluation credits or by PagerDuty's bundled AI add-ons; large orgs needing SSO, private networking and audit logs should budget $1,500/mo Pro or Scale at $3,000/mo rather than trying to hold Team.
Has Cleric's pricing changed?
Cleric has had 5+ price changes since Aug 2026.
| Date | Change |
|---|---|
| Team: $600 → $700 /mo | |
| Pro: $2,000 → $1,500 /mo | |
| Plan removed: Starter | |
| New plan: Free trial ($0) | |
| New plan: Scale ($3,000/mo) |
Who should pick Cleric?
Pick Cleric if you are SRE and platform teams shipping often who need regressions caught days after deploy, Organizations drowning in alerts where most pages close as false positives, Teams that want per-work credit pricing ($1 per change, $5 per Issue) instead of token bills, Engineering orgs that want incident knowledge to compound through operational memory.
Look elsewhere if you are Teams without observability signal for Cleric to investigate or verify against, Small shops with low change frequency where 1,400 monthly credits is overkill, Anyone wanting a basic paging tool rather than AI investigation and fix PRs, Teams unwilling to grant a production agent read access to metrics and deploy messages.
Skip it if Skip Cleric if you deploy a few times a month, have no Datadog or Prometheus signal for it to read, or need private-endpoint access and SSO but won't fund the $1,500/mo Pro tier.
GeneratedReal-world workflow fit
Concrete scenarios for the personas Cleric actually fits — and what changes day-one when you adopt it.
A checkout PR merges Friday. Cleric splits it out as a change, watches cart load p95 through the weekday peak, flags a jump from 182 ms to 511 ms and opens a revert PR tied to the metric, then verifies p95 back at 180 ms after deploy.
Outcome: The regression is caught and fixed before it becomes a weekend page, and the fix PR carries its own evidence into review.
47 alerts hit Cleric in 24 hours. It closes 41 as false positives, investigates and fixes 5, and escalates one payment-api p99 regression with seven correlated signals attached.
Outcome: The one engineer woken has the cause, the evidence and a proposed fix PR instead of a blank dashboard at 02:31.
A query fix solved on one service is stored in operational memory; when an identical alert fires on another team's service, Cleric starts from that prior result and routes the investigation to the right custom agent.
Outcome: Solved problems stop being re-solved, and junior engineers learn from the attached reasoning.
Use cases
- Follow a merged release for 14 days and catch a regression that only shows up at weekday peak traffic.
- Let Cleric pick up a Slack or PagerDuty alert, confirm whether it is real, and page an engineer only when a decision is needed.
- Get a fix PR opened against the config change that caused an error spike, with each line tied to production evidence.
- Ask production questions in Slack instead of opening Datadog and Cloudflare dashboards.
- Verify a deployed fix actually resolved the issue rather than assuming the deploy worked.
- Run scheduled monitors for slow queries or anomalies and post the result to Slack.
- Reuse a solved alert from one team as guidance for an identical alert in another service.
- Coach junior engineers by walking them through Cleric's step-by-step reasoning and attached evidence.
Setup time & first value
How long it actually takes to get something useful out of Cleric — broken out by persona, not the marketing-page minute.
With Datadog or Prometheus and Slack or Teams already in place, first value typically lands the same day: connect the observability stack, add the Slack app so release messages become changes, and Cleric starts verifying and investigating. Okta/SAML, the private-network Connector or EU hosting add a few days and require Pro.
Switching to or from Cleric
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From manual PagerDuty triage: connect PagerDuty and let Cleric investigate matching alerts, keeping PagerDuty for routing and escalation.
- →From Grafana Assistant or Azure SRE Agent: keep your alert sources and add Cleric for the post-deploy verification step those tools don't run.
- →From ad-hoc Datadog dashboard checks: point Cleric at the same Datadog APIs and ask production questions in Slack instead.
- →From tribal incident knowledge: seed operational memory with service relationships and team guidance so new investigations start with context.
- ↗To PagerDuty SRE Agent or Bits AI SRE: if you mainly want triage and diagnosis, your existing alert routes move with you, but you lose the 14-day post-deploy verification loop.
- ↗To Grafana Assistant: if your stack is Grafana-native, pairing it with Grafana's assistant may reduce overlap, though scheduled verification of merged changes is the piece you give up.
- ↗To plain PagerDuty plus humans: viable only if regression volume is low, since Cleric's value is concentrated in closing the loop after deploy.
Integrations
Resources & guides
- Documentationcleric.io
Overview
Your AI SRE teammate
- Documentationcleric.io
Overview
Full product docs from cleric.io
- Conceptscleric.io
Concepts
Core ideas explained from cleric.io
- Quickstartcleric.io
Quick Start
Get up and running fast from cleric.io
- Documentationcleric.io
How Investigations Work
Full product docs from cleric.io
- Documentationcleric.io
Setting Up Sso
Full product docs from cleric.io
- Documentationcleric.io
Configuring Automations
Full product docs from cleric.io
- Documentationcleric.io
Integrations
Full product docs from cleric.io
- Documentationcleric.io
Security
Full product docs from cleric.io
- Documentationcleric.io
Faq
Full product docs from cleric.io
Tutorials & Learning
YouTube returned 6 videos for “Cleric”, and we withheld 6: 6 could not be judged, because “Cleric” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about Cleric.
Official links
What are the best Cleric alternatives?
The closest alternatives to Cleric we list are Metoro, Deeptrace and Doctor Droid. Ranked by direct product-type match, not category overlap.
| Alternative | Pricing | Starts at | Last verified |
|---|---|---|---|
| Metoro | Freemium | Pricing not published | — |
| Deeptrace | Freemium | Pricing not published | — |
| Doctor Droid | Paid | Pricing not published | — |
Alternatives to Cleric
View all
Metoro
Metoro is a Kubernetes observability and AI SRE agent that watches your cluster with eBPF and opens fix PRs for production issues.
Deeptrace
AI SRE agent that investigates every production alert and posts evidence-backed root causes in Slack in 2–3 minutes.
Doctor Droid
DrDroid is an AI SRE agent that maps your stack into a live knowledge graph so every on-call investigation starts with real production
Tools that pair well with Cleric
Common stack mates teams adopt alongside Cleric, with the specific reason each pairing earns its keep.
Metoro
Metoro is a Kubernetes observability and AI SRE agent that watches your cluster with eBPF and opens fix PRs for production issues.
Deeptrace
AI SRE agent that investigates every production alert and posts evidence-backed root causes in Slack in 2–3 minutes.
Doctor Droid
DrDroid is an AI SRE agent that maps your stack into a live knowledge graph so every on-call investigation starts with real production
Frequently asked questions
Categories
Topics
Used Cleric? Help shape our editorial sentiment research.