Built for sensitive packet evidence.
Sensitive captures should not need to leave the analyst's machine just to get useful answers. PacketSense is designed so the capture stays with the analyst unless an enterprise explicitly enables a workflow that sends selected data elsewhere.
What stays local, and what crosses a boundary.
A clear separation between the evidence that stays on the analyst's machine and the small, non-capture checks the app makes to stay licensed and up to date.
Local by default
Raw captures are processed on your machine by default. Sessions and reports are local files you control.
No capture upload for licensing
Activating or renewing a license never requires uploading a capture — only a check that your license is active.
Updates, not captures
Threat-intelligence updates keep your detections current without sending your capture data anywhere.
Enterprise-controlled cloud AI
Cloud AI is optional and enterprise-controlled. Policy can enforce local-only operation and approved providers.
A trust boundary you can point to.
Your machine is where analysis happens and where captures stay. License checks and intelligence updates only ever exchange small, non-capture data — never your packets — and optional cloud AI stays off unless enterprise policy enables it.
PacketSense app
Where analysis happens
Captures & reports
Stored locally, by you
Your raw captures never leave this boundary. Analysis runs on your machine.
Confirms your license is active. No capture data is uploaded.
Keeps detections current, verified before use — your captures stay put.
Stays off unless an enterprise explicitly enables and approves it.
Fresh detections — without sending your captures.
PacketSense Intelligence Cloud keeps threat detections current. Updates are integrity-checked before they are used, and if the update service is unavailable, PacketSense keeps working with what it already has.
- Keeps threat detections current
- Curated from trusted public and vendor sources
- Integrity-checked before it is applied
- Keeps working if the update service is offline
Keep the capture with the analyst.
PacketSense is designed so raw captures stay local by default. Request pilot access to evaluate the full local-first workflow.