Agentic Index
Cleric vs Traversal (2026)
Cleric and Traversal are both AI SREs that keep memories between investigations and can be deployed beyond the vendor's cloud, and Traversal edges the grid, 10.5 of 14 against 10. That verdict is the Agentic Index coverage score, graded from each vendor's own published materials.
Cleric verifies each change after merge against live production, investigates alerts read only and hands fix pull requests to engineers, with published credit plans from 100 dollars a month. Traversal builds a continuously updated causal Production World Model, runs proactive Workers in Slack and Teams, and offers bring your own model and on premises or BYOC deployment through enterprise sales. Traversal is Full on human approval, knowledge grounding and model choice, where Cleric is Partial; Cleric is Full on its audit trail and Partial on evaluation, where Traversal is Partial and None. Choose Cleric to verify changes after merge at a published price; choose Traversal for a causal model of production and your own model choice.
On the Agentic Index production ops ranking, neither Cleric nor Traversal clears the bar, which asks for all five resolution loop capabilities documented in full. Cleric does not document workflow orchestration in full, nor human oversight and guardrails; Traversal does not document workflow orchestration in full, nor observability and auditability. 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 Traversal 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.
- You want a published price and an evaluation program with credits and no time limit.
- A full audit trail of each investigation must be documented.
Choose Traversal if
- Investigations should reason over a causal model of your production estate.
- You need to bring your own model.
- Memories and actions should wait for approval before they take effect.
| Feature | C Cleric |
T Traversal |
|---|---|---|
| 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 |
||
|
TraversalIntegrations & Tool Calling Traversal connects to about 30 observability tools (Datadog, Dynatrace, Splunk, Grafana, Prometheus, CloudWatch, AppDynamics, Sentry) plus AWS, GitHub, GitLab, Confluence, Notion, Jira, Linear, ServiceNow, PagerDuty, incident.io, FireHydrant, Slack, Teams and external MCP servers, which it queries with scoped read access. SourceTraversal docs llms.txt index and Knowledge Bank; docs.traversal.com/using-traversal/knowledge-bankread 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 |
||
|
TraversalWorkflow Orchestration The Causal Search Engine walks the Production World Model across many hops, and Workers take plain language instructions and schedules per channel. There is no multi step builder, branching or coordination between agents, and the investigation flow is Traversal's own. Sourcedocs.traversal.com/using-traversal/workersread 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 |
||
|
TraversalTriggers & Channel Coverage Workers act without being asked. Incident Workers activate when high severity incidents are declared, Alert Workers monitor alert channels continuously, and custom Workers run on plain language missions and schedules, in Slack and Microsoft Teams. Sourcedocs.traversal.com/using-traversal/workersread 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 |
||
|
TraversalKnowledge Grounding & RAG The Production World Model is a continuously updated, AI readable, causal representation of the production system, exposed as a Wiki regenerated as the environment changes with history kept, beside searchable uploaded docs and runbooks in the Knowledge Bank. Sourcedocs.traversal.com/using-traversal/knowledge-bankread 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 |
||
|
TraversalMemory & State Persistence Memories are learnings the agent drafts mid investigation when corrected or told to remember, and they are kept only after a person approves, in an organization wide Knowledge Bank where knowledge persists indefinitely. Traversal does not say how a memory is deleted. Sourcedocs.traversal.com/using-traversal/knowledge-bankread 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 |
||
|
TraversalHuman Oversight & Guardrails Traversal will not make changes to a customer's system without explicit permission, Workers are read only and never modify alerting, paging or routing, and memory proposals are kept only when a person approves, with a person deciding every time. Automated remediation appears in Traversal's marketing without further detail. Sourcedocs.traversal.com/using-traversal/understanding-resultsread 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 |
||
|
TraversalSecurity, Identity & Governance Customers sign in with SSO over OIDC or SAML 2.0, with Member and Admin roles and invite only or domain based access. SCIM is not supported, and Traversal publishes no audit log. SOC 2 Type II sits alongside GDPR and HIPAA alignment and a trust center. Sourcedocs.traversal.com/get-started/authenticationread 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 |
||
|
TraversalObservability & Auditability A result shows the root cause with confidence, evidence citations linking to source tools, anomalies and an incident timeline. There is no record of the queries or steps the agent ran, and no trace retention period is given. Sourcedocs.traversal.com/using-traversal/understanding-resultsread 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 |
||
|
TraversalDeployment & Data Residency Deployment options are private on premises, Bring Your Own Cloud with data residency in the customer's cloud account, single tenant SaaS and PrivateLink. SourceTraversal security page and docs llms.txt index (deployment options); traversal.com/securityread 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 |
||
|
TraversalPrebuilt Agents, Templates & Packs Incident, Alert and Custom Workers are variants of one worker product deployed to different channels, and Skills are procedures the customer's team writes. Traversal offers a prompt library but no agent or template catalog. Sourcedocs.traversal.com/using-traversal/workersread 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 |
||
|
TraversalModel Flexibility & Routing With Bring Your Own Model, customers run Traversal with their preferred LLMs, including self hosted or customer managed models. Sourcetraversal.com/securityread 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 |
||
|
TraversalAPIs, SDKs & MCP Extensibility An API at api.traversal.com uses API key authentication and covers anything a member can do in the web app, including a Sessions API (create, list, get, stream, follow up) and a Knowledge Files API (create, replace, delete), plus MCP access. SourceTraversal docs, API Overview and llms.txt index; docs.traversal.com/api/overviewread 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 |
||
|
TraversalTesting, Debugging & Optimization Traversal's only performance figure is its own benchmark across 25 production incidents, published as marketing. There is no evaluation harness, scored test, rerun comparison or feedback loop. Sourcedocs.traversal.com/using-traversal/understanding-resultsread 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 |
||
|
TraversalBrowser & Computer Use Traversal works read only through observability and code integrations, Slack, Teams, an API and MCP, with no browser, desktop or computer control. Sourcedocs.traversal.com/using-traversal/workersread 2026-09-29 |
||
Pricing snapshot
Sourced from the Index pricing dataset · open each vendor's profile for full detail.
| Pricing | C Cleric |
T Traversal |
|---|---|---|
|
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. Enterprise contracts, with on premises, BYOC and bring your own model options. |
|
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. | An enterprise contract, with terms shaped by the deployment model and bring your own model. |
|
Variable cost Workload / overage exposure |
Medium variable cost | Low 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; Traversal sells enterprise contracts with no public price.
More comparisons with Cleric or Traversal
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.