Demo Captures
Open a runnable demo capture
Open the public investigation and launch its example capture directly in the analyzer.
Demo captures are small, focused traces that show how PacketSafari behaves on real packet evidence. Use them to validate the product flow before uploading customer or production captures.
To see the expected outcome first, read the sample Agent report. It shows a completed investigation with preliminary direction, independent verification, exact packet evidence, and explicit uncertainty.
Inside the authenticated workspace, the demo gallery is available at Workspace demos.
Recommended demo set
| Scenario | What it proves | Best first action |
|---|---|---|
| TCP packet drops during a large download | Packet loss, retransmissions, and throughput symptoms | Open packet statistics, then ask Agent to explain the loss pattern |
| HTTP proxy gateway timeout | Application error with a compact web trace | Review HTTP packets, then use Copilot for the status-code sequence |
| Bad mail transaction | Mail protocol failure and clear client/server exchange | Filter on mail protocols and inspect response codes |
| Website timeout from two capture points | Client, firewall, and server-side evidence comparison | Compare endpoint behavior, then ask Agent to rank the strongest evidence |
| NAT fast versus slow web server | Same-path comparison with clear latency contrast | Review TCP timing and response behavior across both traces |
| Routing failover during transfer | Path change and service continuity under network maintenance | Open protocol hierarchy, then inspect the affected transfer window |
How to run a demo
- Open Workspace demos or upload one of the demo captures manually.
- Wait for Open ready.
- Open the analyzer and read the summary surfaces.
- Open Quick Insights if available.
- Validate one finding in the packet list or protocol summary.
- Start Agent with a focused request.
For Agent runs, add Case context before submitting if the scenario includes a measurement point or operational symptom. Keep the prompt narrow enough that the first run can produce a useful answer:
Explain the likely root cause. Rank the strongest packet evidence and tell me
which frame range or connection I should inspect next.
What to expect by plan
Free and lower-tier SaaS flows are useful for upload, packet inspection, summary surfaces, and bounded AI assistance. Agent Pro is the right path for deeper autonomous investigation, longer-running analysis, and evidence-backed reports.
If a demo is large, prefer a targeted prompt and wait for open-ready status instead of waiting for every refining dashboard to finish.
Auto-import paths
Runnable SaaS demos currently open an existing public example capture. They do not upload a fresh copy for every visitor.
For live or probe-driven capture workflows, PacketSafari can auto-import published probe artifacts into the capture library. In the workspace, use Capture probes when that feature is enabled for your deployment. Probe auto-import is separate from the public demo gallery and is normally used for controlled collection, not marketing demo content.
Good demo questions
- What is the first packet-level symptom?
- Is this network loss, application delay, rejection, or policy behavior?
- Which endpoint appears to trigger the failure?
- Which connection, stream, endpoint, or frame range should I inspect first?
- What would I tell an operator as the next action?