Documentation
REAP documentation
Deployment, the connector cluster, integrations, security and operations: the written answers that accompany a proof of value.
What is here
- Deployment: the three models (SaaS, Customer Cloud, Customer On-Prem), what each requires and what each changes.
- Connector cluster: the components inside your network, sizing, high availability, network requirements and credential brokering.
- Integrations, one page per system: prerequisites, permissions requested, setup, what REAP reads, what REAP writes, troubleshooting.
- Security: data classes, retention, encryption, model endpoints and the training policy, subprocessors, disclosure.
- Operate: runbooks, approvals and audit; release notes; API.
How to read the status labels
| Label | Meaning |
|---|---|
| Confirmed | Verified by REAP engineering or security for this page. Public-page statements are not by themselves confirmation. |
| Stated | Published by REAP in the Trust Center or the security packet; engineering verification for this page is pending. |
| Available · On request · In development · Planned · By arrangement | Product status, as defined on the product status page. Planned: on the roadmap, not available today and without a date. |
| Typical default | A value that is standard for the protocol or system and is used unless your deployment specifies otherwise. |
| to confirm | A placeholder REAP engineering must verify or replace before this page is published. |
Relationship to other documents
- The Trust Center is the public summary; this documentation is the operational detail.
- The security packet (sent under NDA in week 0) remains the controlled document of record; where the two differ, the packet governs until this site is updated.
- The product status page governs whether a capability is available, in pilots or on the roadmap.
Last reviewed: October 7, 2026 (draft) · Owner: solutions engineering · Corrections: security@reapnet.ai