Skip to main content
Traversal doesn’t install anything on your hosts, applications or production services. The optional Traversal Connector and Traversal Processor are services you deploy and manage yourself. The Connector reaches private data and observability sources, and the Processor reduces egress volumes and applies data redaction before data leaves your environment.
Read-only by default. Traversal only reads from your systems unless you give it write access, for example a token with write scope or an MCP tool that can change things. The exception is Slack and Microsoft Teams, where Traversal posts its findings.
Both the Traversal Connector and Traversal Processor run in any environment: AWS, GCP, Azure, OCI, or on-prem. Traversal publishes Helm charts for both, so Kubernetes is the easiest path. The Connector can also run as a container on any container runtime. Traversal offers three deployment options: SaaS to get going in minutes with Traversal’s cloud, single-tenant SaaS for a dedicated, isolated deployment fully managed by Traversal in Traversal’s own cloud, or BYOC (Bring Your Own Cloud) for a dedicated, single-tenant, fully-managed deployment in your own cloud account.

SOC 2 Type II

Traversal maintains a SOC 2 Type II attestation report that covers all deployment options.
The easiest way to get started in minutes with Traversal is by signing up on Traversal’s SaaS/cloud offering. Traversal connects to your observability providers over encrypted connections, whether they are cloud vendors or hosted in your own infrastructure.Communication from the Traversal Connector and Traversal Processor to the Traversal SaaS travels over the public internet and is secured with mTLS. Both sides authenticate with certificates, and all traffic is encrypted in transit.Traversal SaaS Architecture DiagramTraversal SaaS Architecture Diagram

Tenant isolation

Customer data is separated by organization, with access controls and privacy safeguards.

Zero data retention

On LLM calls, under zero-data-retention agreements with Traversal’s LLM providers.

Secure access

Connect to your private data sources and systems with the Traversal Connector.

Minimal egress

Reduce data leaving your environment with the Traversal Processor.

Data redaction

Customer-configured data redaction and obfuscation at the edge.

SSO sign-in

Sign in through your identity provider, so your SSO and MFA policies apply.

Who does what — Responsibility matrix

Traversal   Shared   You