What the sandbox can and cannot do
The sandbox is deliberately small. Read this first: it saves you from concluding that Spider is broken when it does what you asked.
- One node, no more. It runs on your laptop or a single-node test cluster. It shares a hosted instance with everyone else trying it, so it does not show a whole cluster's traffic.
- About 5 MB per minute. Traffic above that is dropped, not queued: lost, not delayed. You see incomplete sessions, not slow ones. Point it at a quiet test namespace, not a busy one.
- Capture stops after one hour. In Kubernetes the attachment expires; with Docker or binaries the Whisperer exits (Gossiper 7.17.0 and later). Attach again, or restart the Whisperer, to carry on.
- Data is kept for about two hours, then deleted.
- Nothing is captured until you attach a whisperer to something. In Kubernetes mode installing the agents alone records nothing; with Docker or binaries, the whisperer you start captures straight away.
- Non-production traffic only. Traffic is decrypted and stored on Floocus infrastructure.
- Linux only (amd64 or arm64). Gocipher is eBPF-based, so it needs a Linux kernel. macOS cannot run it natively, including on Apple Silicon: use a Linux VM.
By provisioning, you accept the test-agents terms: you warrant you may capture the traffic you point it at, and Floocus acts as processor for the decrypted data it stores.
Next, provision your sandbox.