Traversal
Enterprise AI SRE built on a continuously updated causal Production World Model, with proactive Workers in Slack and Teams, approval gated memories, bring your own model and on premises or BYOC deployment.
Traversal builds an AI SRE for large enterprises that triages alerts, finds root cause and works incidents on top of the customer's existing observability tools, read only by default and without agents or sidecars. Its core is the Production World Model, a continuously updated causal representation of services, infrastructure and their dependencies, which a Causal Search Engine walks across many hops to isolate a cause and which the product exposes as a Wiki regenerated as the environment changes. Results give a root cause with a confidence level, evidence citations linked back to the source tools, anomalies, an incident timeline and an impact estimate.
Workers join Slack and Microsoft Teams channels and act without being asked. Incident Workers start when a high severity incident is declared and draft the post-mortem at the end, Alert Workers give a verdict on every alert in an alert channel, and Custom Workers follow plain language missions and schedules. Each Worker keeps a scratchpad of findings with citations and an activity feed of its channel and the tool calls it makes.
Traversal will not change a customer's system unless the customer grants it write access, and a self healing option, once a customer turns it on, drafts a fix as a pull request for review and checks it against production. Coding agents connected over MCP can ask whether a change is safe before it merges. The Knowledge Bank holds the Wiki, team written skills, uploaded runbooks and PDFs, and memories the agent drafts when corrected, kept only after a person approves.
Traversal runs as SaaS, single tenant SaaS, in the customer's own cloud account or on premises, supports bring your own model including self hosted models, and exposes an API that mirrors the web app plus MCP access, with service accounts for scripts and pipelines.
Admins deploy its Connector and Processor components from the web app, check each integration stage by stage and see which datasets Traversal can reach, and AWS access runs through a cross account IAM role with short lived credentials. It holds SOC 2 Type II, aligns with GDPR and HIPAA and signs users in through OIDC or SAML SSO. Every investigation is metered in credits, admins set limits for the organization, each member and each Worker, and pricing is quoted through sales.
From our comparison video
Resolve AI vs Traversal (2026): Which Should You Choose?
Our 5 minute video puts Traversal side by side with Resolve AI. It covers what each one does and how each is priced, then when to choose which.
Recorded in October 2026. The profile here is live and updates as research is verified.
Vendor details
Canonical URL
https://traversal.com
Category
SRE / DevOps agent
Subcategory
AI SRE agent
Funding status
Independent. Traversal announced a $120 million Series B at a $1 billion valuation on November 3, 2026, co-led by Kleiner Perkins, Redpoint Ventures and Khosla Ventures with Sequoia and Battery Ventures taking part. It had closed a $48 million Series A and took a strategic investment from Amex Ventures in March 2026. Founded by AI researchers and professors from MIT, Columbia, Berkeley, and Cornell. Named deployments include American Express, Capital One, Kraken, Pepsi, DigitalOcean, and Cloudways.
Company status
independent
Use cases & customers
Primary use cases
Target customers
Deployment options
Integrations
Reads from about 30 observability tools, including Datadog, Dynatrace, Splunk, Grafana, Prometheus, CloudWatch, AppDynamics and Sentry, plus AWS, GitHub, GitLab, Confluence, Notion, Jira, Linear, ServiceNow, PagerDuty, incident.io and external MCP servers, with no agents or sidecars. Works in Slack and Microsoft Teams and exposes an API and MCP access.
In practice
You run in financial services and production telemetry cannot leave your environment. Traversal deploys on premises or in your own cloud account and runs with your own models.
A latency spike cascades across ten services. Traversal's Causal Search Engine walks its Production World Model across many hops to isolate the cause with a confidence level.
Your on call engineers are buried in alert channels. Traversal's Alert Workers watch those channels and investigate without being asked.
Sources & related URLs
Agentic Index coverage score
10.5 / 14 capabilities · 75%
| Integrations & Tool Calling | Full |
|---|---|
|
Traversal connects to about 30 observability tools (Datadog including RUM and Flex Logs, Dynatrace, Splunk, Grafana, Prometheus, CloudWatch, AppDynamics, Sentry) plus AWS, Azure Resource Manager and Monitor, Azure DevOps, Kubernetes through scoped read only kubectl, 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 changelog; docs.traversal.com/changelogread 2026-10-22 |
|
| Workflow Orchestration | Partial |
|
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-10-22 |
|
| Knowledge Grounding & RAG | Full |
|
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. Uploaded PDFs are read including their diagrams, and a Skill can be attached to any investigation. Sourcedocs.traversal.com/using-traversal/knowledge-bankread 2026-10-22 |
|
| Human Oversight & Guardrails | Full |
|
Traversal cannot change a customer's systems or data unless the customer grants it write access, and integrations are read only by default. Self healing is an option a customer turns on, after which Traversal drafts a fix as a pull request for review and checks it against production. Workers never modify alerting, paging or routing, and memory proposals are kept only when a person approves. Sourcedocs.traversal.com/responsible-use/securityread 2026-10-22 |
|
| Security, Identity & Governance | Full |
|
Customers sign in with SSO over OIDC or SAML 2.0, with Member and Admin roles and invite only or domain based access. Service accounts give scripts and MCP clients an organization owned identity with a role and rotating keys. SCIM is not supported, and Traversal publishes no audit log. SOC 2 Type II sits alongside GDPR and HIPAA alignment, third party penetration testing and a trust center. Sourcedocs.traversal.com/get-started/authenticationread 2026-10-22 |
|
| Observability & Auditability | Partial |
|
A result shows the root cause with confidence, evidence citations linking to source tools, anomalies and an incident timeline. Each Worker keeps an activity feed of its channel's messages and the tool calls it makes, and admins can review service account sessions from the last seven days. Traversal publishes no audit log of actions and no retention period for these records. Sourcedocs.traversal.com/using-traversal/worker-featuresread 2026-10-22 |
|
| Memory & State Persistence | Full |
|
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-10-22 |
|
| Deployment & Data Residency | Full |
|
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-10-22 |
|
| Prebuilt Agents, Templates & Packs | Partial |
|
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-10-22 |
|
| Triggers & Channel Coverage | Full |
|
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. Auto deploy rules start Workers in new channels, and in Teams a Worker can join meetings whose names match a rule. Sourcedocs.traversal.com/using-traversal/workersread 2026-10-22 |
|
| Model Flexibility & Routing | Full |
|
With Bring Your Own Model, customers run Traversal with their preferred LLMs, including self hosted or customer managed models. Sourcetraversal.com/securityread 2026-10-22 |
|
| APIs, SDKs & MCP Extensibility | Full |
|
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 that lets coding agents check a change against production. Service accounts hold keys for scripts and pipelines. Sourcedocs.traversal.com/api/overviewread 2026-10-22 |
|
| Testing, Debugging & Optimization | Not documented |
|
Traversal publishes its own benchmarks on high severity production incidents as marketing. Customers get no evaluation harness, scored test or rerun comparison. Sourcedocs.traversal.com/using-traversal/understanding-resultsread 2026-10-22 |
|
| Browser & Computer Use | Not documented |
|
Traversal works 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-10-22 |
|
The Agentic Index coverage score grades every vendor Full, Partial or Not documented against the same 14 buyer facing capabilities, from public evidence only. Each capability links to how all vendors in the index score on it. How this evidence is graded
Product updates
Traversal investigations can now connect to Azure Resource Manager and Azure Monitor through one connection, covering resource inventory and configuration, change history, health, identity metadata and Azure Monitor logs and metrics, authenticated through Microsoft Entra Workload Identity Federation with reader roles on chosen subscriptions. A separate Azure DevOps connector, for the cloud service and on premises Server, lets the agent correlate incidents with repositories and pull requests.
Bears on: Security / enterprise
View sourceTraversal's investigation agent can now query Datadog Real User Monitoring to count affected users and isolate a regression by route, release, browser, device or region, then follow the trail into backend traces and logs. It is rolling out to organizations with an existing Datadog connection.
Bears on: Integrations
View sourceTraversal launched a Microsoft Teams integration that brings its AI SRE into Teams, connected to the same Production World Model as its web and Slack surfaces.
Bears on: Integrations
View sourcePricing
Contact sales. Investigations are metered in credits, and no rates are published.
Credits per investigation. The credit cost and contract terms are set through sales.
Included quota
A credit allowance and deployment model set in the contract. No public tiers.
What is public
The credit meter is public, meaning every new investigation is metered, and so are the limits admins can set. No dollar figures, tiers or credit costs are.
Billing mechanics
Enterprise contracts through sales. Every new investigation is metered in credits, follow-ups are not metered again, and on premises deployment and bring your own model are options that shape terms.
Cost watchouts
Investigations started by alerts and Workers draw credits alongside the ones people start, so alert volume and the number of Workers drive spend. On premises deployment and bring your own model usually add implementation and infrastructure cost that pure SaaS does not carry.
Variable cost rationale
Traversal meters every investigation in credits, whether a person, an alert, a schedule, a service account or a Worker starts it, and follow-ups to an investigation are not metered again. Spend grows with investigation volume and with how many Workers run. Admins can cap it. Organization limits for human, automatic and Worker investigations, one limit per member and daily and monthly limits for each Worker stop new investigations once reached, while work already running finishes. On premises deployment adds infrastructure the customer runs, and bring your own model moves model inference to the customer's own provider account.
Additional watchouts
Cost follows how many investigations run, and Workers and alert triggered investigations keep drawing credits up to the limits an admin sets. The on premises and bring your own model options add deployment complexity and cost over SaaS.
Overage / add-ons
No overage rate is published. Usage limits stop new investigations once reached, and work already running finishes.
Sales call required
Yes, required for paid access
Free / trial
Enterprise evaluations and paid proofs of value through sales. No self serve trial.
Lowest paid plan
Not published. Enterprise contracts only.
Commercial notes
Traversal is independent, backed by Sequoia and Kleiner Perkins with a $48 million Series A and a strategic investment from Amex Ventures, and its founders come from MIT, Columbia, Berkeley and Cornell. American Express cites a 32 percent MTTR reduction and 82 percent RCA accuracy, and DigitalOcean a 38 percent MTTR reduction and 3,600 engineering hours saved a year.
Key ambiguities
The credit meter is published, but credit prices, any included allowance and any price difference between on premises and SaaS deployment are not.
Related vendors
- AlertD — AI agents for AWS operations that run read only in the customer's…
- Anyshift — AI SRE built on a versioned knowledge graph of infrastructure, apps…
- Avesha — Obliq, Avesha's autonomous AI SRE for Kubernetes and agentic…
- Better Stack — Better Stack offers incident management with built in on call,…
- Bluebricks — Context and control layer that lets AI agents operate cloud…
- Cased — AI workflows for infrastructure and platform engineers: default and…
Alternatives to Traversal
The closest documented capability profiles to Traversal among SRE and DevOps agents tracked by Agentic Index, ordered by similarity on the same 14 point evidence the rankings use. No vendor pays for placement.
- Corelayer11.5 / 14Fuller documented coverage on Workflow Orchestration and Observability & Auditability
- Doctor Droid11.5 / 14Adds documented Testing, Debugging & Optimization
- Cleric10.0 / 14Adds documented Testing, Debugging & OptimizationTraversal vs Cleric →
- Edge Delta12.0 / 14Adds documented Testing, Debugging & Optimization
- Komodor13.0 / 14Adds documented Testing, Debugging & Optimization
- Metoro9.0 / 14Fuller documented coverage on Workflow Orchestration
Similarity is computed from each vendor's Agentic Index coverage score evidence, axis by axis, not from the totals. How this evidence is graded