Glossary · Architecture, deployment and data
Deployment models
The three ways to run REAP: SaaS in REAP Cloud, Customer Cloud (your AWS (opens in a new tab), Azure (opens in a new tab) or GCP (opens in a new tab) account) and Customer On-Prem (your data center).
In REAP
SaaS is Available today; Customer Cloud and Customer On-Prem are By arrangement, and air-gapped operation is confirmed per customer. The connector cluster inside the customer network is common to all three.
Related terms
More in architecture, deployment and data
- Air-gapped
- Allow-list
- Connector cluster
- Customer Cloud
- Customer On-Prem
- Data classes
- Data residency
- 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.