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.
SOC 2 Type II
Traversal maintains a SOC 2 Type II attestation report that covers all deployment options.
- SaaS
- Single-tenant SaaS
- BYOC (Bring Your Own Cloud)
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.



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.



