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 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 when a high severity incident is declared, Alert Workers on alert channels, and custom Workers on plain language missions and schedules. They read, reason and recommend; the vendor states Traversal will not change a customer's system without explicit permission. The Knowledge Bank holds the Wiki, team written skills, uploaded runbooks 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. It holds SOC 2 Type II and signs users in through OIDC or SAML SSO. Pricing is not published.
Vendor details
Canonical URL
https://traversal.com
Category
SRE / DevOps agent
Subcategory
AI SRE agent
Funding status
Independent, closed a $48 million Series A. Founded by AI researchers and professors from MIT, Columbia, Berkeley, and Cornell, backed by Sequoia Capital and Kleiner Perkins. Named deployments include American Express, Capital One, Kraken, Pepsi, and DigitalOcean.
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 |
|---|---|
|
A documented integration catalog of 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, queried with scoped read access. SourceTraversal docs llms.txt index and Knowledge Bank; docs.traversal.com/using-traversal/knowledge-bankread 2026-09-29 |
|
| 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. No multi step builder, branching or coordination between agents is documented; the investigation flow is the product's own. Sourcedocs.traversal.com/using-traversal/workersread 2026-09-29 |
|
| 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. Sourcedocs.traversal.com/using-traversal/knowledge-bankread 2026-09-29 |
|
| Human Oversight & Guardrails | Full |
|
'Traversal will not make changes to your system without your explicit permission', Workers are read only and 'never modify your alerting, paging, or routing', and memory proposals are kept only when a person approves ('a person decides every time'). The homepage's automated remediation line is not documented further. Sourcedocs.traversal.com/using-traversal/understanding-resultsread 2026-09-29 |
|
| 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; SCIM is not supported and no audit log is published. 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 | Partial |
|
A result shows the root cause with confidence, evidence citations linking to source tools, anomalies and an incident timeline. No record of the queries or steps the agent ran is documented, and trace retention is not stated. Sourcedocs.traversal.com/using-traversal/understanding-resultsread 2026-09-29 |
|
| Memory & State Persistence | Full |
|
Memories are learnings the agent drafts mid investigation when corrected or told to remember, kept only after a person approves, in an organization wide Knowledge Bank where 'Knowledge persists indefinitely'; a delete path is not stated. Sourcedocs.traversal.com/using-traversal/knowledge-bankread 2026-09-29 |
|
| Deployment & Data Residency | Full |
|
Private on premises deployment, Bring Your Own Cloud with 'data residency in your cloud account', single tenant SaaS and PrivateLink are documented deployment options. SourceTraversal security page and docs llms.txt index (deployment options); traversal.com/securityread 2026-09-29 |
|
| 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. A prompt library is listed, but no agent or template catalog is published. Sourcedocs.traversal.com/using-traversal/workersread 2026-09-29 |
|
| 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. Sourcedocs.traversal.com/using-traversal/workersread 2026-09-29 |
|
| Model Flexibility & Routing | Full |
|
Bring Your Own Model: 'Run Traversal with your preferred LLMs, including self-hosted or customer-managed models', so the customer chooses the model. Sourcetraversal.com/securityread 2026-09-29 |
|
| APIs, SDKs & MCP Extensibility | Full |
|
A documented API at api.traversal.com with API key authentication, where 'Anything a member can do in the Traversal web app, you can do over the API', with 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 | Not documented |
|
The only performance figure is the homepage benchmark across 25 production incidents, which is the vendor's own marketing. No evaluation harness, scored tests, rerun comparison or feedback loop is documented. Sourcedocs.traversal.com/using-traversal/understanding-resultsread 2026-09-29 |
|
| Browser & Computer Use | Not documented |
|
Works read only through observability and code integrations, Slack, Teams, an API and MCP; no browser, desktop or computer control is documented. Sourcedocs.traversal.com/using-traversal/workersread 2026-09-29 |
|
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
Recent platform changes
Traversal'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 sourceTraversal introduced Knowledge Bank 2.0, a workspace with a Wiki, Skills, uploaded documentation and Memories that feed its Production World Model and inform how its SRE agent reasons.
Bears on: Memory / state
View sourcePricing
Contact sales; enterprise contracts, with on premises, BYOC and bring your own model options
enterprise contract
Included quota
Contract covering the AI SRE on the Production World Model, Workers and Knowledge Bank; deployment model negotiated. No public tiers.
What is public
Nothing numeric; the deployment options, bring your own model and the enterprise sales route are public.
Billing mechanics
Enterprise contracts through sales, with on premise deployment and bring your own model as options that shape terms. Pricing not disclosed.
Cost watchouts
On premise deployment and bring your own model, while valuable for residency, typically add implementation and infrastructure cost versus pure SaaS. Longer setup as the Production World Model maps the environment.
Variable cost rationale
Enterprise platform licensing; no usage metering documented, though on premise infrastructure is a fixed added cost rather than variable.
Additional watchouts
The on premise and bring your own model options are the reason to choose Traversal for regulated environments, but they add deployment complexity and cost over SaaS.
Overage / add-ons
No public metering documented.
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
None public; enterprise contract only
Commercial notes
Independent, $48 million Series A, Sequoia and Kleiner Perkins backed, MIT and Columbia and Berkeley and Cornell founders. American Express reported 32 percent MTTR reduction and 82 percent RCA accuracy; DigitalOcean reported 38 percent MTTR reduction and 36,000 hours saved.
Key ambiguities
Nothing numeric is public, and on premise versus SaaS pricing differences are not documented.
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
- Middleware8.0 / 14A lighter documented profile than Traversal
- NeuBird11.0 / 14Adds documented Testing, Debugging & OptimizationTraversal vs NeuBird →
Similarity is computed from each vendor's Agentic Index coverage score evidence, axis by axis, not from the totals. How this evidence is graded