Glossary · Architecture, deployment and data
Data classes
The kinds of data REAP collects: device configurations, command output, topology, telemetry, ticket metadata, and flow records (NetFlow or IPFIX) where you configure them. It does not inspect traffic payloads and does not capture traffic continuously; on-demand packet captures run only when you ask, are kept with that investigation and follow the retention terms. No clinical or cardholder data by design.
In REAP
Listed in the Trust Center; retention is configurable and deletion on request at the end of an evaluation.
Related terms
More in architecture, deployment and data
- Air-gapped
- Allow-list
- Connector cluster
- Customer Cloud
- Customer On-Prem
- Data residency
- Deployment models
- gNMI
- Integrations
- Model endpoint
- Model-training policy
- Multi-tenancy
- Read-only credentials and service accounts
- REAP Cloud (SaaS)
- Retention
- Secrets and tokens
- Single sign-on (SSO)
- Telemetry
- Tenant isolation
- TLS and the outbound tunnel
- Topology
- Virtual IP (VIP)
Bring us your last P1.
Keep the root cause to yourself; in a 30-minute session we walk through how REAP would have investigated it, evidence first. The replay on your own network happens inside the proof of value.