Observe · Posture for each customer
Standby pairs out of sync, running/startup drift and CVEs that apply because of the features each customer runs.
For MSPs and managed-network providers
Evidence you can show your customers, from one console
REAP gives your tier 1 evidence-backed investigations and lets your engineers switch between customer estates from one console. Smaller businesses rarely run their own networks; through you, they get the same evidence an enterprise network team would.
Who this is for
Many customer estates, one senior team
Regional MSPs and managed-network providers run many customer estates with lean senior teams, and consistency, evidence and tier-1 capability are the margin. Every customer has a different estate. Every escalation costs a senior engineer. Proving to a customer what happened means reconstructing evidence after the fact, and growth means hiring ahead of revenue.
With REAP, when a customer asks what happened, the answer is already in the ticket: the Investigation Window, the evidence behind it and the execution record of any runbook REAP ran. The number to measure is customer networks per senior engineer.
Smaller businesses
How REAP reaches businesses that do not run their own networks
A business with a handful of sites and no network team rarely runs network operations software itself, and it should not have to. Its network is run by an MSP. So REAP reaches smaller businesses through the MSPs that run their networks, not around them.
What the business gets is the difference between “resolved” and an explanation: what changed, why it broke, what was affected and what was done, with the evidence, in the tickets its provider already keeps. What the MSP gets is one way of working across every customer estate, instead of one per senior engineer.
The daily loop
Observe · Reason · Act · Prove, across customer estates
Each capability with its status in the September 2026 release.
Reason · Tier 1 that resolves
The Investigation Window gives tier 1 what changed, why it broke and what is affected, with the evidence, so experts review instead of collect.
Act · The same procedure across estates
Your SOPs compiled into diagnostic runbooks that run the same way across customer estates, each with an execution record.
Prove · Evidence on the changes you make
A before-and-after comparison of a real change window, with the outcome in the change ticket. Automated verdicts are In development.
One console, many estates
A multi-organization console: operators switch between customer estates without switching tools.
Per-operator customer scoping
Limiting each operator to named customers is In development. The isolation controls in place today are described in the security packet.
Tenancy today. REAP Cloud is multi-tenant, with tenant isolation enforced at the application layer. The multi-organization console is Available; per-operator customer scoping for MSPs is In development. Confirm the current controls with REAP before a partner pilot; the security packet describes them.
How to start
Start with one customer estate
Prove the pattern on real customers before you build the practice.
Bring one customer estate
Pick a customer with a recent P1. Describe it and 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 that customer’s network happens inside the partner pilot.
Run the partner pilot
60 days across 3 to 5 of your customers, one production domain each, measured on the same 8 categories as an enterprise pilot and reported per customer.
Choose how you offer it
Resell REAP, refer it, or run it inside your managed service. The partner model and margin are set in the partner agreement.
The partner pilot
60 days, 3 to 5 customers
The standard terms. Details are on the partner program page.
| Element | Standard |
|---|---|
| Scope | 3 to 5 partner customers, one production domain each; the ITSM and one telemetry source per customer |
| Deployment | REAP Cloud with a connector cluster in each customer network; the partner’s own cloud account by arrangement |
| Measures | The same 8 scorecard categories as an enterprise pilot, reported per customer |
| Commercial | Resell, refer or run REAP inside your managed service, with margin set in the partner agreement; the pilot fee credited against the first-year agreement |
| Enablement | Solutions-engineering support, demo paths, the champion business-case template and the value calculator |
Questions
MSP questions
Can a small business buy REAP directly?
Usually, no. REAP is built for teams that run their own networks across many sites and 3 or more vendors, and pilots start on a production domain of 50–250 devices. A smaller business is better served through the MSP that runs its network; ask your provider to talk to us.
Which networks and tools does REAP support?
Cisco (opens in a new tab), Arista (opens in a new tab), Juniper (opens in a new tab), HPE Aruba (opens in a new tab) and Palo Alto Networks (opens in a new tab) estates; AWS (opens in a new tab) and Azure (opens in a new tab) network constructs; Juniper Mist (opens in a new tab), Aruba Central (opens in a new tab) and Cisco Meraki (opens in a new tab); ServiceNow (opens in a new tab), Jira (opens in a new tab) and ManageEngine. Fortinet (opens in a new tab), SONiC (opens in a new tab) and other platforms: coverage is confirmed per pilot. See integrations.
Is per-operator customer scoping available?
Not yet; it is In development. The multi-organization console is Available today, and the security packet describes the isolation controls in place. Confirm them with REAP before the pilot.
What does an MSP pay?
Partner pricing covers deployments across your customer networks from one console, with a partner-led 60-day pilot option. REAP is never priced per engineer, and no price figures are published. See the partner program.
Download the one-pager: REAP for MSPs and managed-network providers PDF · one page · to share with your team
Bring one customer estate.
A partner pilot proves the pattern on real customers before you build the practice.