Traversal

Name: Traversal
Brand: Traversal

AI Native

The AI SRE for the enterprise.

Est 2023|Valuation $309.5M|Raised $53M|2 Ref Customers

LinkedIn 7K|Web traffic 9K|FTEs 106|HQ New York, NY

MarketsIncident Management & On-Call

01Competitive Landscape

Narrative analysis

Where Traversal may provide value: - If its cross-system RCA functions as described, it may provide deeper correlation across heterogeneous data sources than tools focused primarily on alert routing or runbook automation. Where competitors may be preferable: - PagerDuty: organizations needing a mature incident process layer (on-call schedules, escalations, stakeholder comms) may prefer an established vendor with broad integrations. - Shoreline: teams focused primarily on deterministic, scriptable automation and clear pricing may find Shoreline’s automation-first approach more suitable. - Observability-suite vendors (Datadog, New Relic, Splunk): buyers that have standardized on a single observability vendor may prefer integrated intelligence within that vendor’s suite. Adoption trend (directional): - The AI-for-SRE category is emerging and competitive; buyers should assume vendor differentiation claims and validate with pilots and benchmarks.

	Traversal (vendor)	Shoreline.io	PagerDuty (Incident Mgmt + AIOps)
Starting Price	Not publicly listed (sales-led)	Free plan; enterprise pricing publicly documented	Free tier available; paid per-user tiers + paid AIOps add-on
Typical use case	RCA across fragmented observability for complex incidents; assistant-style workflows described by vendor	Automation/remediation and ops notebooks with explicit automation control	Incident management, on-call scheduling, routing, and stakeholder communications; broad integrations
Key strengths (observed)	Correlation-driven RCA approach and emphasis on flexible deployment options (per vendor materials)	Explicit pricing, automation focus, self-host options	Market maturity, process tooling, broad integrations, on-call management
Key weaknesses (observed)	Limited public security/compliance documentation and limited independent user reviews; pricing opaque	May require adopting Shoreline’s operational model; may not fit all remediation models	Can be expensive at scale; RCA depth depends on available integrations and telemetry

01Competitive Landscape

Narrative analysis

Where Traversal may provide value:

If its cross-system RCA functions as described, it may provide deeper correlation across heterogeneous data sources than tools focused primarily on alert routing or runbook automation.

Where competitors may be preferable:

PagerDuty: organizations needing a mature incident process layer (on-call schedules, escalations, stakeholder comms) may prefer an established vendor with broad integrations.
Shoreline: teams focused primarily on deterministic, scriptable automation and clear pricing may find Shoreline’s automation-first approach more suitable.
Observability-suite vendors (Datadog, New Relic, Splunk): buyers that have standardized on a single observability vendor may prefer integrated intelligence within that vendor’s suite.

Adoption trend (directional):

The AI-for-SRE category is emerging and competitive; buyers should assume vendor differentiation claims and validate with pilots and benchmarks.

	Traversal (vendor)	Shoreline.io	PagerDuty (Incident Mgmt + AIOps)
Starting Price	Not publicly listed (sales-led)	Free plan; enterprise pricing publicly documented	Free tier available; paid per-user tiers + paid AIOps add-on
Typical use case	RCA across fragmented observability for complex incidents; assistant-style workflows described by vendor	Automation/remediation and ops notebooks with explicit automation control	Incident management, on-call scheduling, routing, and stakeholder communications; broad integrations
Key strengths (observed)	Correlation-driven RCA approach and emphasis on flexible deployment options (per vendor materials)	Explicit pricing, automation focus, self-host options	Market maturity, process tooling, broad integrations, on-call management
Key weaknesses (observed)	Limited public security/compliance documentation and limited independent user reviews; pricing opaque	May require adopting Shoreline’s operational model; may not fit all remediation models	Can be expensive at scale; RCA depth depends on available integrations and telemetry