Distributed-systems analyzer

See every request that crossed the wire. Decrypted, and kept.▌

Spider takes the packets off the wire with AF_PACKET, decrypts them using TLS keys eBPF lifts out of process memory, and reconstructs them into one correlated trace that is still there next week, when you find out you needed it.

Try Spider See pricing Explore the docs site →

◆ AF_PACKET capture · eBPF TLS keys · no code changes · HTTP · gRPC · Redis · PostgreSQL · Kafka

Spider Analyzer communication grid: protocols correlated into one timeline
0 code changes × 5 wire protocols → 1 correlated timeline

What Spider does

Built to end the guesswork

[ tls ]

Decrypt the packets, not a copy

eBPF uprobes lift TLS and goTLS session keys from memory, and Spider decrypts the packets it captured. The handshake, the certificate and the connection that failed survive next to the plaintext.

[ trace ]

One trace, five protocols, kept

HTTP, gRPC, Redis, PostgreSQL and Kafka reconstructed into a single correlated timeline, stored and searchable for as long as you set retention.

[ map ]

Automatic cluster map

eBPF traces and resolves every network call in the cluster, so you see what talks to what with no configuration.

[ ebpf ]

Agentless by design

AF_PACKET takes the packets, eBPF takes the keys. No instrumentation, no libraries, no language lock-in. Deploy agents from the UI in a few clicks.

[ infra ]

Runs on your infra

Helm and Docker, on-prem or SaaS, with IAM and data segregation. Your traffic never leaves your cluster.

[ business ]

Search it in your language

Tags and plugins resolve raw wire data into customers, orders and products, pulled from your own business APIs.

See how →

How it works

Four steps, no instrumentation

  1. 1

    Capture

    AF_PACKET takes the packets off the wire across your pods. No agents in your code.

  2. 2

    Decrypt

    TLS keys lifted from OpenSSL and Go memory by eBPF decrypt those packets.

  3. 3

    Parse

    Protocol parsers rebuild every request and response, correlated end to end.

  4. 4

    Visualize

    Timelines, maps and a searchable trace of what actually happened.

The signature move

From raw wire to business meaning

Five protocols converge into one correlated trace. Then tags and plugins resolve every raw identifier into the customers, orders and products your business actually thinks in.

Every protocol, one trace

HTTPS gRPC Redis PostgreSQL Kafka + more

These five are just the start - more protocols are on the way.

↓
search ▸ clientId:  c-452002 Acme corp 5 matches
time proto contenttemplate clientId orderId
10:24:07 gRPC orderservice.createOrder Create an Order c-452002 Acme corp o-125689 Blue pin - x12 - €149.00
10:24:07 PSQL INSERT INTO ORDERS Save order c-452002 Acme corp o-125689 Blue pin - x12 - €149.00
10:24:08 Redis SET cart.cache.4567 Update cart c-452002 Acme corp o-125689 Blue pin - x12 - €149.00
10:24:08 HTTPS POST /transactions/ Send payment c-452002 Acme corp o-125689 Blue pin - x12 - €149.00
10:24:09 Kafka Produce order.placed Confirm fulfilment c-452002 Acme corp o-125689 Blue pin - x12 - €149.00

◆ resolved live by tags + plugins, against your own business APIs

Ready to see it on real traffic?

Spin up the live demo and watch your protocols correlate into one trace.

Try Spider Explore the docs site