Traversal is an AI site reliability engineering platform aimed at enterprise teams drowning in incidents and alerts. With this launch, Incident Workers move to general availability alongside the public beta of Alert Workers and a new Workers console for deploying and managing a fleet of agents across Slack and Microsoft Teams . The pitch to on-call engineers is straightforward: an Incident Worker joins an incident channel the moment something breaks, decides for itself when to engage, and owns the investigation end to end , while Alert Workers cut noise by learning which alerts are routine, deduping repetitive noise, and surfacing the handful that are new or meaningful, with the reasoning attached .
The technical bet under the hood is causal reasoning over telemetry rather than a chat wrapper on top of dashboards. The Workers run on Traversal's Causal Search Engine and Production World Model, the same foundation behind the rest of the platform , which the company positions as a way to handle the messy, cross-service investigations that typically require a war room. This GA moment matters because it lands after real production use at scale. Since entering public beta on June 30, Workers have run across thousands of real incidents at some of the largest enterprises in the world, helping teams close incidents faster, pull fewer people into war rooms, and find the root cause before the full response team is paged , with American Express among the disclosed customers.
Traversal was founded by AI researchers from MIT, Columbia, Berkeley, and Cornell , with Anish Agarwal as CEO and co-founder alongside Raj Agrawal, Ahmed Lone, and Raaz Dwivedi (a Cornell Tech assistant professor). The company is backed by Sequoia and Kleiner Perkins , and this release signals a shift from reactive AI copilots toward agents that decide on their own when to start investigating, a design choice founders and operators building agentic products will want to study closely.
Comments (15)
Sign in to join the discussion.
P
Priya KadamSep 3, 2026
An SRE that pages itself instead of paging me at 3am. If this actually works I owe you a kidney.
Z
Zoya KhalilSep 3, 2026
A wise oncall told me once: the best incident is the one you slept through. Feels like that's the pitch here.
R
Rufus OkonkwoSep 3, 2026
ok wait, proactive agents is the whole unlock. every agent I've tried so far is basically a golden retriever waiting for a stick.
M
Max LindqvistSep 3, 2026
The tweet copy buries the lede under a t.co link. 'Workers know when to get to work' is the hook, lean on it harder next time.
S
sanaeSep 3, 2026
Curious about the trigger policy for kicking off an investigation. Are you doing anomaly scoring on signals or subscribing to specific alert channels and dedup'ing?
J
Jaime LoopSep 3, 2026
We shipped something adjacent inside Google in 2019 called Sherlock and it never left staging because nobody trusted it to touch prod. Curious what the trust ramp looks like here.
K
Karim FaroukSep 3, 2026
Every incident demo looks great until the day Kafka lies to you and half your traces are missing. Would love to see a postmortem where the Worker was actually wrong.
T
Tanya BeteilleSep 3, 2026
Been watching Anish cook on this since forever, GA feels underhyped in the copy honestly. This should have been a video not a screenshot.
H
Harish V.Sep 3, 2026
Hot take: 'AI SRE' is the new 'AI copilot'. The moat is whether it can actually resolve, not just narrate the outage in confident paragraphs.
P
Petra NovakSep 3, 2026
Been telling my LPs about Traversal for months, this GA post is the receipt. The bar for observability tooling just moved.
L
Livia OkonjoSep 3, 2026
On the procurement side, is there a SOC2 Type II report available and does the Worker run in our VPC or does telemetry leave the perimeter?
R
Rafa MendesSep 3, 2026
Rewriting the tagline for the group project: 'The AI SRE that pages itself.' You're welcome, invoice in DMs.
B
Benoît DuvalSep 3, 2026
How is this billed, per incident, per Worker, or per node monitored? Asking because 'proactive agent' and 'predictable burn' are historically not friends.
G
Grigori SolovyovSep 3, 2026
Surprised nobody has proposed a $SRE token yet where responders stake reputation on incident calls. I'll see myself out.
A
Amara OkaforSep 3, 2026
Are the Workers exposed via API with webhooks for state changes? Want to pipe investigations into our own runbook UI and not live in yet another dashboard.
Work With Us
Book an intro call to explore our suite of services. We might have a waitlist.
Traversal AI
The AI SRE for even the most complex incidents.
The AI SRE for even the most complex incidents.
Tags
TLVC Rating
Community Rating
No ratings yet
to rate this launch.
Traversal is an AI site reliability engineering platform aimed at enterprise teams drowning in incidents and alerts. With this launch, Incident Workers move to general availability alongside the public beta of Alert Workers and a new Workers console for deploying and managing a fleet of agents across Slack and Microsoft Teams . The pitch to on-call engineers is straightforward: an Incident Worker joins an incident channel the moment something breaks, decides for itself when to engage, and owns the investigation end to end , while Alert Workers cut noise by learning which alerts are routine, deduping repetitive noise, and surfacing the handful that are new or meaningful, with the reasoning attached . The technical bet under the hood is causal reasoning over telemetry rather than a chat wrapper on top of dashboards. The Workers run on Traversal's Causal Search Engine and Production World Model, the same foundation behind the rest of the platform , which the company positions as a way to handle the messy, cross-service investigations that typically require a war room. This GA moment matters because it lands after real production use at scale. Since entering public beta on June 30, Workers have run across thousands of real incidents at some of the largest enterprises in the world, helping teams close incidents faster, pull fewer people into war rooms, and find the root cause before the full response team is paged , with American Express among the disclosed customers. Traversal was founded by AI researchers from MIT, Columbia, Berkeley, and Cornell , with Anish Agarwal as CEO and co-founder alongside Raj Agrawal, Ahmed Lone, and Raaz Dwivedi (a Cornell Tech assistant professor). The company is backed by Sequoia and Kleiner Perkins , and this release signals a shift from reactive AI copilots toward agents that decide on their own when to start investigating, a design choice founders and operators building agentic products will want to study closely.
Comments (15)
An SRE that pages itself instead of paging me at 3am. If this actually works I owe you a kidney.
A wise oncall told me once: the best incident is the one you slept through. Feels like that's the pitch here.
ok wait, proactive agents is the whole unlock. every agent I've tried so far is basically a golden retriever waiting for a stick.
The tweet copy buries the lede under a t.co link. 'Workers know when to get to work' is the hook, lean on it harder next time.
Curious about the trigger policy for kicking off an investigation. Are you doing anomaly scoring on signals or subscribing to specific alert channels and dedup'ing?
We shipped something adjacent inside Google in 2019 called Sherlock and it never left staging because nobody trusted it to touch prod. Curious what the trust ramp looks like here.
Every incident demo looks great until the day Kafka lies to you and half your traces are missing. Would love to see a postmortem where the Worker was actually wrong.
Been watching Anish cook on this since forever, GA feels underhyped in the copy honestly. This should have been a video not a screenshot.
Hot take: 'AI SRE' is the new 'AI copilot'. The moat is whether it can actually resolve, not just narrate the outage in confident paragraphs.
Been telling my LPs about Traversal for months, this GA post is the receipt. The bar for observability tooling just moved.
On the procurement side, is there a SOC2 Type II report available and does the Worker run in our VPC or does telemetry leave the perimeter?
Rewriting the tagline for the group project: 'The AI SRE that pages itself.' You're welcome, invoice in DMs.
How is this billed, per incident, per Worker, or per node monitored? Asking because 'proactive agent' and 'predictable burn' are historically not friends.
Surprised nobody has proposed a $SRE token yet where responders stake reputation on incident calls. I'll see myself out.
Are the Workers exposed via API with webhooks for state changes? Want to pipe investigations into our own runbook UI and not live in yet another dashboard.