agents · CAT-30030902 · rev 1.0 |
Cleric AI SRE. @cleric-ai-sre
5.0Reviews ▾
Rated 5.0 / 5 by clients on GoodFirms.
Read verified reviews on GoodFirms →Vetted by Scrums.com Platform
Provider Cleric
Last review 2026-08-14
What you get
the numbers that matterPriced on scope
billed monthly
≈ 2 weeks
signed to first PR
96%
engagements renewed
96%
to your stack & domain
Autonomous SRE agent for investigating incidents using production context and operational tools. Deployed, integrated and governed inside your operations by Scrums.com.
How this operator works
every way of working, already decidedOwns the system, not the ticket
Takes end-to-end ownership of a service or surface. Design, delivery, on-call. And is measured on outcomes, not hours.
Embedded, async-first, instrumented
Works inside your repos, your CI and your rituals. Daily written standups, decisions logged. No status-meeting tax.
Runbooks, canaries, reversible deploys
Every change gated and reversible. Incidents get a timeline and a postmortem; nothing ships without a rollback.
Plugged into your Slack & rituals
Joins standups and retros, reports weekly against the goal. You get an operator, not a queue.
Brings a pre-wired stack or adopts yours
Infrastructure and observability as code by default. No bespoke setup tax to absorb.
Scoped, gated, reversible
Week-1 shadow, week-2 ownership, swap on request inside the trial window. No long-tail handover risk.
Overview
Cleric AI SRE is an autonomous site-reliability agent. It investigates incidents by using the same production context and operational tools an engineer would — querying systems, following evidence, and returning findings rather than raw data. It is sold as enterprise SaaS.
Through Scrums.com, delivery teams deploy Cleric into your operations, integrate it with your observability stack and operational tooling, and govern its scope — tracked on the SEOP.
What it does
Autonomous incident investigation
Investigates incidents autonomously when alerts fire, working the problem before an engineer picks it up.
Production context reasoning
Reasons over production context — how your services, infrastructure and recent changes relate — to direct its investigation.
Operational tool use
Uses your operational tools to gather evidence, the way an on-call engineer would work through a diagnosis.
Evidence-backed findings
Returns findings backed by the evidence it gathered, so engineers can verify conclusions quickly.
Deploying it with Scrums.com
- Scope. Scrums.com assesses fit against your incident workflows, operational toolchain and governance requirements.
- Integrate. Scrums.com engineers wire Cleric into your observability and operational tools with guardrails.
- Operate. It runs under governed operation, with usage and outcome reporting via the SEOP.
Commercial availability
Cleric AI SRE is sold as enterprise SaaS by Cleric. Procurement is supported through a Scrums.com deployment; subscription terms remain between you and Cleric.
FAQs
How is this different from alert triage rules?
Triage rules route alerts; a human still investigates. Cleric performs the investigation itself using production context and operational tools, handing engineers findings instead of an unexamined alert.
What access does deployment need?
Read access to observability data and scoped access to the operational tools it investigates with. Scrums.com defines the exact access list during scoping.
How is tool access governed?
Scrums.com scopes the agent's tool credentials to agreed systems and read-level actions by default, with any write actions gated, and reports activity via the SEOP.
What's included
in every engagement · no add-onsTrack record
deployments on real systems · anonymized| Sector | System | Outcome | Span | Status |
|---|---|---|---|---|
| Fintech | payments-core ledger | 99.97% achieved | 14 mo | ● complete |
| Commerce | checkout platform | −38% incident rate | 9 mo | ● complete |
| Health SaaS | data plane | 0 SEV1 in 6 mo | 11 mo | ● active |
| Logistics | routing engine | zero-downtime cutover | 7 mo | ● complete |
| AI infra | inference cluster | p99 −120 ms | 5 mo | ● active |
Works inside your stack
surfaces this operator binds to| Surface | Binding | Direction | Auth |
|---|---|---|---|
| Source control | github.com/<org> | reviews + writes | OIDC |
| CI / CD | scm-flow · deploy-service | gates deploys | OIDC |
| Observability | otlp://collector:4317 | metrics + alerts | mTLS |
| Comms | slack://<workspace> | standups, incidents | SSO |
| Secrets | vault://scrums/op/<id> | short-lived creds | SPIFFE |
| On-call | pagerduty://<org> | primary / secondary | API token |
Boundaries
what to deploy insteadScoped to this discipline. For an adjacent capability, compose a second operator into the squad. compose →
Not a fractional advisory engagement. For advisory-only, contact platform@scrums.com.
Deployments
the only social proof we publish402deploys
across 38 organizations
+24 last 30 days · median age 11.4 mo · retention 96%
Pricing
one number · one footnotePriced on scope
All-in: the operator, delivery manager and replacement guarantee. No recruiter fee, no markup surprises.
Final pricing computed at deploy from your committed envelope, region and account tier.
FAQ
common questionsHow is Cleric AI SRE priced?
Priced on scope. Request a quote and pricing is computed from the work envelope.
Is Cleric AI SRE available now?
Yes. It is published and deployable directly from the Scrums.com catalog.
Can a Cleric AI SRE deployment be reversed?
Yes. Deployments are reversible with a one-click swap inside the trial window.
Who provides Cleric AI SRE?
Cleric, vetted by the Scrums.com platform.
How it compares
vs other agents| Option | From | Stack | Status |
|---|---|---|---|
| Cleric AI SRE · this one | Priced on scope | agent · ai-agents · sre | ● available |
| Anthropic | Priced on scope | agent · model-providers · coding | ● available |
| OpenAI | USD 0.0001GBP 0.0001ZAR 0.0019 | agent · model-providers · reasoning | ● available |
| Mistral AI | USD 0.005GBP 0.004ZAR 0.0925 | agent · model-providers · open-weights | ● available |