Observe
Posture findings for every domain in scope: standby pairs out of sync, running/startup drift and CVEs that apply because of the features you run.
For enterprises
One standard of evidence across every business unit
For enterprises with many sites or business units, 3 or more network vendors, change control and audit scope. REAP explains incidents with evidence, assesses changes before they run and finds standby pairs and configurations that have drifted, above the tools each team already runs.
The enterprise problem
Every business unit starts from zero
Each business unit runs its own network, vendors and habits. In one design-partner pattern, an industrial group with several operating companies, a P1 in one company took a week to explain because the context lived in 3 teams’ heads. The leadership question was simple: why does every incident start from zero?
Change control has the same gap. The change advisory board approves on judgment, the record says “no impact expected”, the change closes as completed, and the P1 that follows at 02:00 is never connected to it. Audit evidence is gathered by hand, over weeks, from screenshots.
The stakes are measurable. New Relic (opens in a new tab)’s 2026 Observability Forecast (opens in a new tab) puts the mean cost of a high-impact outage at $1.85M per hour, and 57% of respondents to Uptime Institute (opens in a new tab)’s Annual Outage Analysis 2026 (opens in a new tab) said their most recent major outage cost more than $100,000.
The daily loop
Observe · Reason · Act · Prove, in every business unit
What your teams do with REAP on an ordinary day, with each capability’s status in the September 2026 release.
Reason
Incidents your monitoring raises reach REAP through ServiceNow (opens in a new tab) or Jira (opens in a new tab) and open with the Investigation Window: what changed, why it broke and what is affected, with the evidence. Direct correlation of third-party alert streams is In development.
Act
Proposed changes are assessed before execution (Available). Approved runbooks run behind a confirmation: diagnostic runbooks are Available, remediation runbooks a Pilot deliverable.
Prove
Every conclusion links to its evidence; approvals and runbook runs are logged with the device output. Before-and-after verification of a real change window is a Pilot deliverable.
Follow a day with REAPChange control and audit
Evidence your CAB and your auditors can read
Before the change: Available. Change impact analysis assesses a proposed change against topology, reachability, security policy and known CVEs, using state snapshots and path tracing. A change that would collapse redundancy or open a policy path is flagged with its reasons before approval.
After the change: Pilot deliverable. In a pilot today, one real change window is verified with your team, for changes made anywhere: CAB-approved, vendor or emergency. The configuration is compared with a pre-change snapshot, the paths the change touched are traced again and the posture checks run again. The change gets one outcome (Verified, Degraded, Rolled back, Inconclusive or Blocked), recorded with the evidence in the change ticket. Automated state packs, verdicts and silent-failure detection are In development.
For audit. Intent, pre-state, diff, evidence and approver are recorded for each verified window, and audit logging is Available. Evidence packages for audit scope, such as PCI segmentation, are In development; where audit scope is in a pilot, evidence for the controls you agree with us comes from configuration and topology findings.
Security review
What your security team will ask first
The full answers are in the security packet, sent under NDA.
| Question | Answer |
|---|---|
| Will an agent change our network? | Not until you say so. REAP is read-only by default; writes run only inside approved runbooks, behind a confirmation, logged with the device output (remediation runbooks: Pilot deliverable). Autonomous execution without approval: Not offered. |
| How are credentials handled? | Least-privilege, read-only credentials, brokered through CyberArk (opens in a new tab) where available (Available) and revocable by you at any time. HashiCorp Vault (opens in a new tab): Planned, not available today. |
| What about identity and audit? | SSO (SAML/OIDC) through Okta (opens in a new tab) or Microsoft Entra ID (opens in a new tab), role-based access, audit logging and a multi-organization console: Available. |
| Where does it run? | REAP Cloud on AWS (opens in a new tab) in U.S. regions (Available), with a connector cluster inside your network and an outbound TLS tunnel. Your own AWS, Azure (opens in a new tab) or GCP (opens in a new tab) account, or your data center: By arrangement. |
| Which models see our data? | Customer data is not used to train models without your written consent. The model provider is named in the security packet. |
| Where is the SOC 2 (opens in a new tab) Type II report? | SOC 2 (opens in a new tab) Type II is in process; the report is available upon request, under NDA. Status and timeline are in the security packet. A read-only pilot can be approved on the packet while production waits; your process decides. |
How enterprises start
One business unit, 45 days, a decision
Start where the cost is. Expand only when you pull.
Start the security review in week 0
Request the security packet and name your questionnaire. Security review of the production deployment and legal review of the order form run during the pilot, not after it.
Pick one business unit
One plant group, region or business unit as the pilot domain: typically 50–250 devices, 2 or 3 vendors on REAP’s supported list, ServiceNow (opens in a new tab) or Jira (opens in a new tab), and one telemetry source.
Measure against your baseline
Replay 5–10 incidents whose root cause you know and REAP doesn’t, review findings with your architect in week 3, compare one real change window before and after, and put runbooks under approval.
Decide with the economic buyer
The week-6 business review ends in BUY, EXTEND or STOP. Additional domains and assurance modules can be written into the order form as the expansion path.
Questions
Enterprise questions
Does REAP replace our monitoring, ITSM or automation?
No. Nothing is replaced, including the AI assistants your network vendors and your ITSM ship. REAP reasons across all of them and writes its findings and evidence back into the tickets you already use.
Can we talk to a customer?
Not yet, and we will not pretend otherwise. REAP runs today with design partners and has no public customer references; named references follow only when a customer has measured results and has agreed in writing. Instead: a walkthrough session on your last P1, founders at your kickoff and business review, and a paid pilot with a decision date you set.
How is REAP priced across business units?
By the size of the managed environment and the capability tier, never per engineer, so every engineer and approver can use it. REAP publishes no price figures; a proposal follows discovery.
Sources
- New Relic, 2026 Observability Forecast (press release, September 22, 2026). https://secure.businesswire.com/news/home/20260922268747/en/New-Relic-Report-Finds-High-Impact-IT-Outages-Drain-$74-Million-Annually-from-Businesses (opens in a new tab)
- Uptime Institute, Annual Outage Analysis 2026. https://uptimeinstitute.com/resources/research-and-reports/annual-outages-analysis-2026 (opens in a new tab)
Download the one-pager: REAP for enterprises PDF · one page · to share with your team
Open one door on one business unit.
A 45-day proof of value on one production domain: your baseline in week 0, 8 measures, and BUY, EXTEND or STOP in week 6.