Spider already offers a grid for browsing communications one by one and a sequence diagram for reading call flows.
Neither of them answers the question at a glance: when exactly did this request happen, how long did it take, and what else was running at the same time?

The waterfall view is the answer.
It places every communication on a shared timeline as a horizontal bar.
The bar's left edge is the start time; its width is the duration. Slow requests are instantly visible as wide bars; gaps between bars reveal idle time; overlapping bars reveal parallel activity.

The centrepiece feature is lane grouping, which groups communications by endpoint pair and stacks concurrent ones vertically - turning the waterfall into a concurrency map.

Spider captures and parses several Layer 7 protocols at once: HTTP and PostgreSQL, both TLS encrypted or not.

Until now, each protocol lived in its own dedicated view.
That worked well for focused investigation - but it made it harder to reason about what a service was actually doing at a given moment, because you had to flip between tabs and correlate manually.

The Unified view (labelled "All" in the view selector) solves this.
It is a unified view that shows HTTP and PostgreSQL communications together in a single grid, sequence diagram, waterfall, and stats panel.

The Spider Controller is the Kubernetes-native agent that watches your cluster in real time: it tracks pods, services, deployments, and ownership chains, attaches capture agents to pods, answers DNS queries, and maintains a live WebSocket connection to the Spider backend. For the past few years it has been written in Node.js. That changes now.

Spider's interface has been with us for a while. It worked well — but the left sidebar navigation, dense filter panels, and compact top bar had started to feel dated. After years of incremental additions, the time was right for a proper rethink.

The result is now live as the default. Here is the story of how it got built.

Algolia has now integrated AI chat in their search features! :)

This version introduces PostgreSQL parsing as a first citizen of Spider.

Deep, protocol-level database observability — without instrumentation, without SQL logs.

I'm excited to announce a major new capability in Spider Analyzer: native PostgreSQL wire-protocol parsing!

This feature takes Spider’s network observability one step further by decoding actual PostgreSQL protocol messages directly from live traffic — giving you precise, structured insight into what your applications really do with your database, at runtime, and at scale. 💪

The new Spider release introduces a complete technical overhaul of all services.
This significant achievement was accomplished over just one month, thanks to the incredible assistance of AI agents!

This version is a technical release upgrading most components to reduce CVE and technical debt.
It also includes several bug fixes and performance improvements.

This release introduces Service Accounts for third party connection to Spider APIs.