Coming Soon

Features to help you understand what happened and what changed.

Everything here answers a single question: what actually happened on the wire? toran can detect, analyze, and notify - but never mutate, block, or act automatically.

Alerts & Notifications

Get notified when patterns change or anomalies appear - without toran taking any automatic action.

Error Rate Anomalies

Get notified when error rates spike, drop, or exhibit unusual patterns compared to baseline behavior.

  • -Detect sudden error rate increases (2% → 30%)
  • -Identify new error types that haven't appeared before
  • -Track error rate by endpoint or request type
  • -Compare error patterns across time windows

Latency Degradation

Surface when upstream APIs slow down or response times exceed expected thresholds.

  • -Alert on p95 latency increases
  • -Detect gradual performance degradation
  • -Track TTFB and transfer time separately
  • -Compare latency before and after deploys

Traffic Pattern Changes

Know when request volume, frequency, or distribution shifts unexpectedly.

  • -Detect traffic spikes or drops
  • -Identify new endpoints being called
  • -Surface changes in request method distribution
  • -Alert on retry storms or looping behavior

Authentication & Rate Limit Warnings

Get notified about auth failures and approaching rate limits before they become critical.

  • -Track 401/403 error trends
  • -Monitor rate limit header values
  • -Alert when approaching vendor quotas
  • -Detect token expiration patterns

Response Shape Changes

Know when upstream APIs return different structures, missing fields, or unexpected data types.

  • -Detect new or removed fields in responses
  • -Identify type changes (string → null)
  • -Surface unexpected response formats
  • -Alert on breaking API changes from vendors

Core Insight

The first questions users ask after inspection. Applies to every use case.

Traffic Diffs (Change Detection)

Compare two time windows or segments to answer: what changed since the last time this worked?

  • -Surface new or missing paths
  • -Identify latency regressions
  • -Spot error rate changes
  • -Detect response size shifts

Request Grouping / Fingerprinting

Automatically group similar requests to reduce noise and identify patterns at scale.

  • -Identify repeated failures vs one-offs
  • -See which kind of request dominates traffic
  • -Understand spammy or looping behavior
  • -Especially valuable for agents and retries

Advanced Traffic Analysis

Segment traffic by explicit rules and get summaries for each segment.

  • -Top paths per segment
  • -Latency distribution (p50 / p95)
  • -Response size trends
  • -Error rate breakdown

Debugging Acceleration

Surfaces patterns and anomalies without inspecting every request.

Saved Response Replay

Replay captured requests using saved responses - no API call is made. Deterministic, zero side effects, and safe by default.

  • -Replay history without touching the upstream
  • -Test application logic with real captured responses
  • -Debug issues that are hard to reproduce
  • -Share reproducible scenarios with teammates

Shows you what already happened, again. Fully deterministic.

Error Taxonomy & Clustering

Group failures by type, not just status code. Users don't think in status codes.

  • -Auth failures
  • -Validation errors
  • -Vendor rate limits
  • -Timeouts and connection issues

Deterministic rules, not AI. Transparent classification.

Header & Field Frequency Analysis

See which headers or fields appear most often, are missing intermittently, or change values unexpectedly.

  • -Auth headers missing 5% of the time
  • -A specific header only present on failures
  • -Payload field suddenly null
  • -Surfaces subtle bugs without inspecting every request

Request Shape Change Detection

Detect when request structure changes - new fields added, fields removed, type changes.

  • -Catches accidental breaking changes
  • -Especially valuable for agents that construct payloads dynamically
  • -Observes and reports only
  • -Never blocks or enforces

Orientation & Closure

Context, collaboration, and closure for debugging sessions.

Time-Correlated Views

Slice traffic around a specific moment - a deploy, agent version change, or config update.

  • -Compare behavior before vs after a moment
  • -More intuitive than arbitrary time ranges
  • -Pairs naturally with annotations and diffs
  • -Purely visual and analytical - no automation

Dependency Health Snapshot

A compact summary for one upstream API when you open a toran.

  • -Request volume
  • -Error rate
  • -Latency trend
  • -Payload size trend

Answers 'is this API behaving normally?' - not monitoring, just a snapshot.

Safe Upstream Replay

Manually re-send a captured request upstream to validate vendor fixes or reproduce failures.

  • -Validate vendor fixes
  • -Reproduce flaky or auth-related failures
  • -Test edge cases without re-running the whole system
  • -Explicit, manual, and auditable

High impact when needed. Must remain explicit and manual to preserve trust.

Request Annotations & Tags

Add notes to requests, segments, or time ranges to capture context.

  • -Mark deploys and incidents
  • -Note agent versions
  • -Document vendor outages
  • -Especially valuable for teams

Evidence Bundles

Package requests, diffs, and annotations into a shareable artifact for support tickets or incident reviews.

  • -Export context for vendor support
  • -Share exact behavior with teammates
  • -Document incidents for postmortems
  • -Preserve debugging context

A Note on Replay

toran will support two distinct replay modes. They serve different purposes and must stay separate.

Saved Response Replay

Replay history without touching the upstream. No API call is made - toran returns the saved response instead.

  • - Zero side effects
  • - Fully deterministic
  • - Safe by default

"Show me what already happened, again."

Manual Upstream Replay

Explicitly re-send a captured request to the upstream API. Requires confirmation and is fully auditable.

  • - User-initiated only
  • - Clear warnings for side effects
  • - Pro tier and above

"Would this request succeed right now?"

What's Not Here

No automatic actions. No mutations. No policies.

toran can detect patterns, surface anomalies, and notify you - but it will never retry, block, or mutate your traffic.

toran must preserve epistemic integrity: what you see must be what actually happened. No hidden behavior. No side effects. No automatic actions.

Most tools fail because they try to observe, decide, and act all at once. toran separates observation from action. It can tell you what happened, detect changes, and surface patterns - but you decide what to do about it.

This gives you:

  • - Trust
  • - Simplicity
  • - Reversibility
  • - A clear mental model
  • - Lower blast radius

toran observes, detects, and notifies. It never mutates, blocks, or acts automatically on your traffic.

Which features would help you most?

Create a toran and let us know what you need.

Create your first toran