ClericCleric · ops-agentvs
ResolveResolve · ops-agent
The two dedicated AI SREs. Both watch alerts, investigate across observability stacks, and hand on-call engineers a root-cause hypothesis; Resolve leans on its Splunk/observability pedigree, Cleric on Slack-native team feedback loops.
agentlist.io · spec diff · verified 2026-09-25 — list prices only, not benchmarks
Spec diff
Pick which
pick Cleric if
You want investigation anchored in Slack workflows and explicit learning from responder feedback.
pick Resolve if
You're a mature observability shop and want the ex-Splunk team's take on the problem.
watch out
Both are enterprise deals that live or die on integration depth — the demo is the easy part; wire them into real telemetry before judging.
Feature notes
- Cleric
- 01Alert investigation
- 02Cross-signal correlation
- 03Root-cause hypotheses
- 04Slack-native workflow
- 05Learns from team feedback
- 06Read-only by default
- Resolve
- 01Alert triage + dedup
- 02Autonomous investigation
- 03Remediation drafts
- 04Observability integrations
- 05Incident timelines
- 06Approval gates
Frequently asked
Cleric or Resolve — which should I pick?
The two dedicated AI SREs. Both watch alerts, investigate across observability stacks, and hand on-call engineers a root-cause hypothesis; Resolve leans on its Splunk/observability pedigree, Cleric on Slack-native team feedback loops. Pick Cleric if: You want investigation anchored in Slack workflows and explicit learning from responder feedback. Pick Resolve if: You're a mature observability shop and want the ex-Splunk team's take on the problem.
Is Cleric or Resolve cheaper?
Cleric: Enterprise (quote-based). Resolve: Enterprise (quote-based). List prices as of 2026-09-25; usage pools and seat terms change the real cost.
Does Cleric or Resolve run locally?
Cleric hosting: cloud. Resolve hosting: cloud. Interfaces differ too: Cleric exposes chat/api, Resolve exposes chat/api.
Are Cleric and Resolve still maintained?
Cleric: actively maintained. Resolve: actively maintained. Statuses are re-verified each catalog refresh (2026-09-25); see the changelog for the full history.