Documentation
SaaS (REAP Cloud)
Multi-tenant REAP operated on Amazon Web Services (opens in a new tab) in U.S. regions with multi-availability-zone failover.
Architecture
- Tenant isolation enforced at the application layer with per-tenant access; multi-tenancy is a platform service.
- No inbound firewall rule to your network is required: connectors open an outbound TLS tunnel to REAP Cloud, and once it is established the platform reaches devices only through the connector endpoints.
- Data classes collected and their retention are on the data classes page; the storage design is documented in the security packet.
Requirements
| Requirement | Value |
|---|---|
| Outbound connectivity from connectors | HTTPS 443 to REAP Cloud endpoints endpoint list |
| Regions | U.S. regions name the regions |
| Availability | Multi-AZ; RPO/RTO state figures from the security packet |
| Identity | SAML/OIDC SSO with your IdP; role mapping |
Operations
- Upgrades are rolling and without downtime confirm maintenance windows.
- Status and incident communication: status page or email process.
- Support access to your tenant is least-privilege, logged and reviewed quarterly.
Engineering to confirm
- REAP Cloud endpoint hostnames and IP ranges for allow-listing
- Named AWS (opens in a new tab) regions
- RPO / RTO figures
- Maintenance-window policy and status-communication channel
Last reviewed: October 7, 2026 (draft) · Owner: solutions engineering · Corrections: security@reapnet.ai