ABOUT US

Where cutting-edge AI research meets world-class engineering

Troubleshooting production incidents is one of the toughest challenges in software — petabytes of noisy data, each incident unique, and every minute costly. Solving it means pushing the limits of what LLMs can do.
Virtual panel with three men—Justine Moore, Anish Agarwal, and John Lee—discussing as part of Traversal Founder Live on TBPN.

00:00

/

00:00

Backed by the best

Testimonials

Perspectives from leaders in AI and observability

01

Traversal uses Elasticsearch innovatively with AI agents. Their agentic architecture and Elasticsearch let Traversal AI autonomously search massive telemetry data efficiently in critical enterprise settings, creating a new way to troubleshoot production incidents and improve software reliability.

Shay Banon, Founder and CEO at Elastic
Shay Banon
Founder & CTO, Elastic
TESTIMONIAL
02

Traversal leads the future of AI Agents with a swarm of expert engineers who quickly fix critical production issues. Their ambient agent system is always present, improving engineers' lives. I'm excited to see how Traversal and the industry evolve from this foundation.

Harrison Chase
Harrison Chase
CEO & Cofounder, LangChain
TESTIMONIAL
WHY TRAVERSAL

Tackling this problem requires a highly-skilled interdisciplinary team

Tackling this problem requires a highly-skilled interdisciplinary team

AI Researchers
AI Engineers
High-Stakes Operators
Devtool Builders

PhDs & professors with expertise in areas like causal machine learning, scalable data systems, and AI explainability

Engineers with experience building industry-defining AI features & products

Engineers & operators from mission-critical environments like high-frequency trading

PMs & designers from leading observability, DevOps, and infrastructure platforms

Meet our newest team members

What is the worst incident you handled before Traversal?

At my last company, when our largest customer’s environment went completely down for eight hours, we pulled together a 15-person war room and were troubleshooting nonstop. Eventually, an AWS Kubernetes engineer joined the call and identified the root cause – a misconfiguration in the EBS driver within our Kubernetes cluster.

Why did you join Traversal?

When I left Grafana in 2024, I told myself that AI-native companies would emerge over the coming years to disrupt the Telemetry Industrial Complex and if given the opportunity, I'd pursue a role in one of those firms. Traversal is the best positioned and resourced company to win this race...

Why did you join Traversal?

I’ve watched great engineers lose days stitching together raw telemetry during incidents. In a previous role building an identity threat investigation agent, I saw teams spend days reconstructing what actually happened because signals were scattered across auth policies, device context, and user behavior logs — with no single system showing the full picture. I joined Traversal because we’re building the reasoning system that should have existed in the first place — not just layering AI onto dashboards, but helping engineers make sense of complex systems.

Why did you join Traversal?

As a former practitioner, I know how tough it is to tackle this challenge at scale—and do it consistently. That’s why I’m so excited about what we’re building at Traversal. It’s a real breakthrough that will help organizations deliver more reliable results for their customers while enhancing the everyday experience of their employees.

Why did you join Traversal?

I’m most passionate about products that I would personally be excited to use daily. As a developer, I would love a product that automates tedious root cause investigations of tons of logs and code changes. Traversal already tackles this with incredible accuracy, and I’m confident that their highly talented team and research-first approach will push the product’s capabilities even further.

Why did you join Traversal?

Traversal passed my 3 criteria with flying colors: high talent density... solving an ambitious problem with AI... working shoulder-to-shoulder in NYC. (Plus lunch!)

Why did you join Traversal?

I joined Traversal because I’ve been on the other side of an incident, diving through logs and dashboards under a time crunch to figure out why our platform was down. It’s a real pain point and a tough problem that I’m confident this team can solve. I love tackling this problem with the talented people here – they make every day fun.

Why did you join Traversal?

It’s a fast-moving space — I like competition, and I believe we have the edge. I’m familiar with and deeply interested in this industry (ex-SignalFx/Splunk), excited about the product vision, and really hit it off with the team. The timing for disruption feels uncanny. This is my sixth startup, and I thrive in the 0 → 1 (and beyond) phase — here for the chaos, the fun, and the camaraderie.

Why did you join Traversal?

Because it marks a fundamental category shift — from observability dashboards and correlation to machine reasoning grounded in causal inference. Built by exceptional technical founders and launched at precisely the right technological inflection point, Traversal is redefining how enterprises understand and operate complex systems.

Why did you join Traversal?

I joined Traversal because it’s tackling a critical challenge for engineering teams, improving how incidents are identified, managed, and ultimately resolved. Honestly, getting the chance to build growth again alongside Nick Billy made the decision even easier.

Ready to put AI to work?