Agentic Index
Cleric vs Resolve AI (2026)
Cleric and Resolve AI are both AI SREs that investigate production alerts, and they are close on the grid, 10 of 14 for Cleric against 10.5. That verdict is the Agentic Index coverage score, graded from each vendor's own published materials.
Cleric verifies each change after it merges against live production, investigates alerts read only, and hands fix pull requests to engineers, with memories that carry context between investigations; its credit plans start at 100 dollars a month. Resolve AI goes on call with a team of specialized agents that triage alerts and investigate incidents in parallel, and every mitigation waits for human approval; it sells credit metered contracts through sales. On the grid Resolve is Full on human approval, knowledge grounding, prebuilt agents, evaluation and orchestration, where Cleric is Partial; Cleric is Full on deployment and memory and Partial on model choice, where Resolve is lower. Choose Cleric to check changes after merge at a published price; choose Resolve for a coordinated team of agents with approval before any mitigation.
On the Agentic Index production ops ranking, Resolve AI clears the bar and Cleric does not. Resolve AI documents all five resolution loop capabilities in full; Cleric does not document workflow orchestration in full, nor human oversight and guardrails. 14 of the 37 vendors in the lane clear it. See the production ops ranking
This comparison is published by Agentic Index, an independent agentic AI vendor research platform. Cleric and Resolve AI are each graded against the same 14 capability Agentic Index taxonomy, from the vendor's own public materials under the Agentic Index verification standard, alongside 955 researched vendors. No vendor pays for placement and no vendor has reviewed this page. How this evidence is graded
Choose Cleric if
- Every change should be verified against live production after it merges.
- Context from past investigations should carry into the next one.
- You want a published price, from 100 dollars a month, and deployment options documented in full.
Choose Resolve AI if
- A team of specialized agents should work an incident in parallel.
- Every mitigation should wait for a person's approval.
- Documented evaluation and orchestration matter; Resolve is Full on both.
| Feature | C Cleric |
R Resolve AI |
|---|---|---|
| Action & orchestration | ||
|
Integrations & Tool Calling Ability to connect agents to real systems through native integrations, OAuth-authenticated actions, custom tools, APIs, webhooks, or MCP-compatible tools. |
||
|
ClericIntegrations & Tool Calling Cleric has named integrations across observability, infrastructure, code and documentation (AWS, Azure, Datadog, Grafana, PagerDuty, Slack, Atlassian, GitHub), with scoped access for each. The agent runs its own commands and queries against them and opens pull requests with fixes. Sourcecleric.airead 2026-09-29 |
||
|
Resolve AIIntegrations & Tool Calling An integration catalog of about 40 systems covers AWS, GCP, Datadog, Dynatrace, Splunk, Grafana, New Relic, PagerDuty, ServiceNow, Sentry, Snowflake, GitHub, Atlassian, Slack and Teams. On approval the agent creates silences, downtimes or mutes in Grafana, Datadog, AlertManager, Kloudfuse and Sumo Logic and triggers commit reverts and GitHub Actions. SourceResolve docs llms.txt index and Mitigation Actions, and Incidents page; docs.resolve.ai/mitigation-actionsread 2026-09-29 |
||
|
Workflow Orchestration Ability to sequence, branch, retry, route, and combine deterministic workflow nodes with autonomous agent steps. |
||
|
ClericWorkflow Orchestration One investigating agent plans tasks, runs queries and adjusts its plan. Custom agents are a name plus a free text prompt fired by a trigger, with no steps, branching or handoffs between agents, and the built in investigate agent cannot be edited. Sourcedocs.cleric.ai/setup/agents-and-triggersread 2026-09-29 |
||
|
Resolve AIWorkflow Orchestration A team of domain-specialized agents investigates in parallel, pursuing hypotheses that engineers can redirect, and verifies findings against production evidence, with a dedicated reviewer validating them. Custom agents compose Resolve's MCP, API and skills into the customer's workflows, and Temporal connects orchestration platforms. Sourceresolve.ai/product/incidentsread 2026-09-29 |
||
|
Triggers & Channel Coverage How agents wake up and where they work: schedules, webhooks, message events, CRM events, inbox events, chat, email, voice, and collaboration tools. |
||
|
ClericTriggers & Channel Coverage Agents fire on bot messages posted in Slack channels that match trigger keywords (alert bots such as PagerDuty and Datadog) and on recurring cron schedules, and change verification follows each change after merge. Scheduled agents and monitors are on the Pro plan. Sourcedocs.cleric.ai/setup/agents-and-triggersread 2026-09-29 |
||
|
Resolve AITriggers & Channel Coverage The On-call Agent goes on-call on the customer's behalf, holding the pager and triaging alerts. Alerts arrive by PagerDuty, Splunk On-Call and alert webhooks from any source, tasks run on schedules, and billing meters triages, investigations and incidents Resolve manages. Sourceresolve.airead 2026-09-29 |
||
| Knowledge & context | ||
|
Knowledge Grounding & RAG Ability to ground agent behavior in company data through document ingestion, retrieval, external knowledge APIs, semantic search, or RAG layers. |
||
|
ClericKnowledge Grounding & RAG Documentation integrations (Atlassian, GitHub) let the agent search and retrieve documentation during investigations, and customers add Global Guidance in settings. Context is assembled for each run, and there is no maintained index over the customer's documents. Sourcedocs.cleric.ai/setup/providing-contextread 2026-09-29 |
||
|
Resolve AIKnowledge Grounding & RAG Team Knowledge is a maintained store of runbooks, docs, dashboard guidance and skills at organization and team level that Resolve activates dynamically during investigations, examining all knowledge tied to the alert and its owning teams. Hivemind adds production state awareness across alerts and incidents. Sourcedocs.resolve.ai/team-knowledgeread 2026-09-29 |
||
|
Memory & State Persistence Ability to persist context across a run, conversation, workflow, user, team, or longer-term memory layer. |
||
|
ClericMemory & State Persistence Memories are facts Cleric proposes from conversations or users add with '@Cleric Remember', organized by service and environment, searched automatically during investigations, kept until deleted or removed by automatic cleanup when stale or contradicted, and viewable, editable and deletable in the Knowledge section. Sourcedocs.cleric.ai/learning/memoriesread 2026-09-29 |
||
|
Resolve AIMemory & State Persistence The agent writes nothing for itself as memory. Team Knowledge is written by people as runbooks, docs and skills, which the product applies as instructions during investigations, and feedback ratings are an evaluation input. There is no self learning knowledge graph. Sourcedocs.resolve.ai/team-knowledgeread 2026-09-29 |
||
| Control & trust | ||
|
Human Oversight & Guardrails Approval steps, consent checkpoints, escalation rules, structured guardrails, policy constraints, and pause/resume controls. |
||
|
ClericHuman Oversight & Guardrails Access is read only, enforced by RBAC and access scopes. Cleric does not make changes to customer infrastructure but may propose them, and all remediation actions are performed by the customer's team. People keep the decisions, and the agent's reach is scoped. Fix pull requests are approved in the customer's own code host. The approve button in the homepage mockup is not explained as a Cleric approval step. Sourcedocs.cleric.ai/security/security-data-privacyread 2026-09-29 |
||
|
Resolve AIHuman Oversight & Guardrails Every action requires explicit human approval before execution. Proposals are approved or rejected in the Resolve UI or Slack, Resolve never has direct access to execute write APIs, and write permissions are enabled per integration. Sourcedocs.resolve.ai/mitigation-actionsread 2026-09-29 |
||
|
Security, Identity & Governance RBAC, SSO, auditability, encryption, least-privilege tool access, compliance posture, and data handling policy. |
||
|
ClericSecurity, Identity & Governance Customers control access through RBAC and access scopes for each integration, and code access can be limited to one repository. Every plan has Google Workspace sign in, and Pro adds Okta, custom SAML or OIDC and an organization audit log. Cleric holds SOC 2 Type II, has a Trust Center and runs annual penetration testing, with AES-256 encryption at rest. Sourcedocs.cleric.ai/security/security-data-privacyread 2026-09-29 |
||
|
Resolve AISecurity, Identity & Governance Customers get SSO (Google, Okta, Azure AD), SCIM directory sync with sign in enforcement, RBAC, access limited to roles, environments or namespaces, and audit logs. Compliance covers SOC 2 Type II, GDPR and HIPAA, backed by a trust center. SourceResolve security page and docs llms.txt index (Security and Administration pages); resolve.ai/securityread 2026-09-29 |
||
|
Observability & Auditability Traces, logs, execution histories, metrics, audit events, and debugging detail for production agent behavior. |
||
|
ClericObservability & Auditability Each investigation keeps an activity log recording the plan, the tools used, the specific commands and queries executed, the raw output from each tool and the reasoning behind conclusions, viewable in the web app. Retained investigation data includes queries, reasoning traces and cited evidence. Sourcedocs.cleric.ai/usage/reviewing-the-activity-logread 2026-09-29 |
||
|
Resolve AIObservability & Auditability Each investigation shows an Evidence Trail with timestamps and verification and a Workbench of what each agent is doing. An Activity Dashboard records every action, including who proposed it, who approved or rejected it, when, and what was affected. Sourcedocs.resolve.ai/mitigation-actionsread 2026-09-29 |
||
|
Deployment & Data Residency Deployment modes and options, including SaaS, dedicated cloud, VPC, on-prem, hybrid, local runtime, and self-hosting. |
||
|
ClericDeployment & Data Residency EU hosted instances run the application, database and model inference in Europe, beside the default GCP hosting, and Enterprise offers custom data retention and region. Operational logs, traces and product analytics are still processed centrally in the US. A private network connector reaches private resources but does not change where Cleric runs. Sourcedocs.cleric.ai/security/eu-hosting-data-processingread 2026-09-29 |
||
|
Resolve AIDeployment & Data Residency Customers choose between a shared multi tenant cloud and a dedicated single tenant cloud deployment with bring your own keys. The Satellite agent runs in the customer's Kubernetes or ECS, keeps credentials local and proxies queries into Resolve's cloud. There is no region list or customer environment option. Sourcedocs.resolve.ai/resolve-satelliteread 2026-09-29 |
||
| Solution readiness | ||
|
Prebuilt Agents, Templates & Packs Ready-made workflows, packaged employees, templates, blueprints, industry solutions, and role-specific agents that reduce time-to-value. |
||
|
ClericPrebuilt Agents, Templates & Packs One built in investigate agent ships and cannot be edited. Further agents are ones the customer writes as a name and a prompt, and there is no template or agent catalog. Sourcedocs.cleric.ai/setup/agents-and-triggersread 2026-09-29 |
||
|
Resolve AIPrebuilt Agents, Templates & Packs Separately named agents ship for their own jobs, namely the On-call Agent that holds the pager and triages alerts, the Incident Resolution Agent for root cause and mitigation, and Issue Remediation for recurring problems. There is no cost optimization or feature development agent. Sourceresolve.airead 2026-09-29 |
||
| Platform extensibility | ||
|
Model Flexibility & Routing Ability to work across multiple foundation models, route tasks to different models, or let buyers bring their own providers and keys. |
||
|
ClericModel Flexibility & Routing Cleric names Anthropic, Google Gemini and OpenAI as its model providers, under zero training and zero retention terms. Cleric uses them internally, and customers and admins cannot choose a model. Sourcedocs.cleric.ai/security/security-data-privacyread 2026-09-29 |
||
|
Resolve AIModel Flexibility & Routing Resolve uses frontier LLM models combined with domain-specific models, without naming a provider, and customers cannot choose a model. Sourceresolve.airead 2026-09-29 |
||
|
APIs, SDKs & MCP Extensibility Composability layer: stable APIs, SDKs, MCP tool consumption/serving, custom tools, and integration into internal systems. |
||
|
ClericAPIs, SDKs & MCP Extensibility Outside callers drive Cleric through its own MCP server, on every plan. It has a per tenant endpoint at <company>.app.cleric.ai/mcp, bearer authentication with personal API keys and an enumerated tool list, and its create_issue tool starts a new investigation, a core platform object. There is no REST API or SDK. Sourcedocs.cleric.ai/integrations/mcpread 2026-09-29 |
||
|
Resolve AIAPIs, SDKs & MCP Extensibility A REST API at app0.resolve.ai with bearer personal or organization tokens triggers, lists and reads investigations, alongside a Resolve MCP server and AI assistant plugins. SourceResolve docs, Resolve REST API and llms.txt index; docs.resolve.ai/resolve-rest-apiread 2026-09-29 |
||
|
Testing, Debugging & Optimization Testing, debugging, scoring, retries, fallbacks, quality gates, and optimization loops for improving agent workflows before and after deployment. |
||
|
ClericTesting, Debugging & Optimization A learning loop calibrates the agent through explicit feedback (1 to 5 message ratings and corrections), implicit feedback from actions taken, and analysis of past investigations. There is no evaluation harness, scored test or quality metric for findings. Change verification tests the customer's releases, not the agent. Sourcedocs.cleric.ai/learning/how-cleric-learnsread 2026-09-29 |
||
|
Resolve AITesting, Debugging & Optimization A change can be evaluated against an earlier result. After updating knowledge or integrations, Reinvestigate alert re-runs the same alert so the new result can be compared against the original, and thumbs up or down verdicts on each report collect under Analytics, Feedback. Sourcedocs.resolve.ai/tuning-accuracyread 2026-09-29 |
||
| Specialist automation | ||
|
Browser & Computer Use Browser, desktop, or remote/local computer control for workflows that cannot be handled through stable APIs alone. |
||
|
ClericBrowser & Computer Use Work runs through scoped integrations, commands and queries, Slack and an MCP server, with no browser, desktop or computer control. Sourcedocs.cleric.ai/usage/reviewing-the-activity-logread 2026-09-29 |
||
|
Resolve AIBrowser & Computer Use Work runs through integrations, a Satellite proxy, Slack, a REST API and an MCP server, with no browser, desktop or computer control. SourceResolve docs llms.txt index and Incidents page; resolve.ai/product/incidentsread 2026-09-29 |
||
Pricing snapshot
Sourced from the Index pricing dataset · open each vendor's profile for full detail.
| Pricing | C Cleric |
R Resolve AI |
|---|---|---|
|
Entry price Lowest public entry point |
From $700 per month on Team, with 1,400 credits. Pro is $2,000 and Enterprise is custom. | Contact sales. Contracts are metered in credits, and no rates are published. |
|
Pricing confidence How public the numbers are |
Public, exact | Contact only |
|
Billing Primary billing axis |
Monthly credit plans. A change verification or an investigation draws 10 credits and chat 1 credit per minute, and Enterprise runs on a custom annual credit pool. | Credits per unit of work, consumed by chats and tasks, investigations, incidents and triages. The credit cost of each is defined in the contract. |
|
Variable cost Workload / overage exposure |
Medium variable cost | Medium variable cost |
|
Free tier / trial Try before you buy |
No free tierTrial
|
No free tierTrial
|
|
Buying motion Self-serve vs sales call |
Mixed | Sales call |
Cleric publishes credit plans; Resolve AI sells credit metered contracts with no public rates.
More comparisons with Cleric or Resolve AI
Other matchups in SRE and DevOps agents
Not the pairing you were after? These compare a different set of SRE and DevOps agents on the same 14 capabilities.