ClericCleric · ops-agentvsResolveResolve · 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 · documented attributes · sources and dates shown per value

Compare the same attributes

Every entry uses the same category fields. Open a source to check the scope and date behind a value. Not documented means we have no supported value, not that a feature is absent.

Cleric versus Resolve: shared and category-specific attributes
AttributeClericAwaiting documentation reviewResolveAwaiting documentation review
Common attributesDirectory metadata and source-documented values. Not documented is an evidence gap, not a negative claim.
CategoryAgentlist's buyer category; directory classification rather than a product capability.Operations and incidentsOperations and incidents
Entry typeDirectory classification distinguishing products, frameworks, infrastructure and protocols.productproduct
Directory coverageHow the entry entered this directory; not a quality rating or a claim that every field is verified.CatalogedCataloged
Recorded availabilityAvailability classification in the directory; check the source and review date before relying on current access.activeactive
InterfacesDocumented ways a person or application interacts with the entry.Not documented
Recorded sources

Recorded catalog specification; availability and terms may have changed.

Not documented
Recorded sources

Recorded catalog specification; availability and terms may have changed.

Execution / hostingWhere the documented service or workload runs; this is not a data-residency guarantee.Not documented
Recorded sources

Recorded catalog specification; availability and terms may have changed.

Not documented
Recorded sources

Recorded catalog specification; availability and terms may have changed.

Pricing basisSource-described price and billing basis. Different units and plans are not directly equivalent.Not documented
Recorded sources

Recorded catalog specification; availability and terms may have changed.

Not documented
Recorded sources

Recorded catalog specification; availability and terms may have changed.

LicenseDocumented license for the specified component or offering.Not documentedNot documented
Operations and incidentsComparable questions for this category. Sources and dates describe the evidence; no performance ranking is implied.
Incident responseSupports alert, on-call or incident investigation workflows.Not documentedNot documented
Named integrationsExplicitly documented integrations; not an exhaustive coverage claim.Not documentedNot documented
Approval gatesRequires a human decision before designated actions can proceed.Not documentedNot documented
Audit logsProvides recorded security or administrative events; scope and retention require evidence.Not documentedNot documented
Remediation actionsCan execute operational changes, not only recommend them.Not documentedNot documented
SEC.02

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.

SEC.03

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
FAQ

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). These are recorded catalog prices, not a fresh quote. Check vendor pricing for current plans, usage charges and seat terms.

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?

Recorded catalog status — Cleric: actively maintained. Resolve: actively maintained. Check the linked sources for current availability; the catalog's creation date is not a product verification date.

ALT

More comparisons