Incident Reasoning
“Why is this path down, what changed, and what is affected?” Evidence-backed root cause on replayed and live incidents, in the Investigation Window.
Incident ReasoningREAP facts
REAP, in checkable facts
For journalists, analysts and anyone summarizing REAP: what REAP is and is not, who it is for, what is available today and what is not, and whom to ask. Last reviewed October 7, 2026.
In one sentence
What REAP is
REAP is the agentic AI platform for network operations: the reasoning and assurance layer above the tools you already run.
REAP stands for Reasoning Enabled Agentic Platform. It observes a network and its IT systems, reasons over live evidence, acts under the customer’s governance and proves the outcome: Observe · Reason · Act · Prove, governed across all four steps. It is read-only by default, approval-gated when it acts, and every conclusion is traceable to its evidence. Its tagline is Agentic Network Assurance. Grounded in Evidence. Its category is network assurance: evidence that incidents are understood, that changes worked and that failover will work.
Is and is not
What REAP is, and what it is not
REAP is
- A reasoning and assurance layer that reads from monitoring, ITSM, PAM, on-call, automation and network platforms and writes evidence back into the tickets a team already uses.
- Read-only by default. Any write runs inside a runbook the customer approved, behind a confirmation, logged with the device output.
- Outside the data path. If REAP is unavailable, the network keeps running; investigations pause.
- Evaluated on the customer’s own network: a 45-day proof of value on one production domain that ends in BUY, EXTEND or STOP. MSP partners run a 60-day partner pilot.
REAP is not
- A replacement for monitoring, observability, AIOps, ITSM, automation or vendor AI assistants. Nothing is replaced.
- Autonomous. Autonomous execution without approval is Not offered, and REAP does not act on its own conclusions.
- A traffic-inspection or endpoint-security product. It reads flow records where you send them; it does not inspect payloads or capture traffic continuously.
- Priced per engineer or metered per query.
- Publicly referenced by customers yet. REAP runs today with design partners and has no public customer references.
Who it is for
Who REAP is for
Enterprises with multi-vendor estates, or single-vendor estates made complex by hybrid cloud (AWS (opens in a new tab) or Azure (opens in a new tab) network constructs alongside on-premises sites), where the network runs production and the team is small. Many sites, plants or business units, and more incidents and changes than senior engineers can check. Industries: manufacturing and multi-entity enterprises, healthcare, higher education, financial services, retail and distribution, data centers and neocloud providers, and MSPs and managed-network providers.
- Enterprises with many sites or business units, change control and audit scope.
- Mid-sized companies with 3 to 10 network engineers and no 24x7 NOC.
- MSPs and managed-network providers, and through them the smaller businesses whose networks they run.
Probably not a fit yet: a single-vendor estate with no cloud footprint that your vendor’s tools already cover, a platform team that builds its own agents, or a policy that nothing may leave your facility today (Customer On-Prem deployment is By arrangement).
The three doors
Every engagement starts through one door
Each door opens on one production domain and expands only when the customer pulls.
Change Assurance
“How do we know the change worked?” Impact analysis before execution, and a before-and-after comparison with the evidence in the change ticket.
Change AssuranceResilience Assurance
“Will failover actually work?” Standby sync, drift and contextual CVE (opens in a new tab) findings with evidence; backup-path capacity and continuous failover-readiness proof are In development.
Resilience AssuranceProduct status
Capability status, September 2026 release
Labels: Available · Pilot deliverable · In development · Planned · By arrangement · On request · Not offered. Nothing in development or planned is sold as available.
| Capability | Status | Note |
|---|---|---|
| Telemetry collection: SNMP, syslog, CLI, gNMI (opens in a new tab), and flow records (NetFlow or IPFIX) where configured | Available | Native collection through the connector cluster; no payload inspection and no continuous packet capture |
| Proactive monitoring: qualified incidents from REAP-collected telemetry | Available | Deterministic conditions raise incidents with a first analysis attached |
| Correlation and prioritization of third-party alert streams | In development | Today, incidents raised by your monitoring reach REAP through ServiceNow (opens in a new tab) or Jira (opens in a new tab) |
| Incident response & root-cause analysis (Investigation Window) | Available | Replayed and live incidents; engineers score evidence traceability in a pilot |
| Topology-aware assistant (chat) | Available | Answers from topology, configuration, telemetry and history, with the commands and outputs behind them |
| Path trace: forward, reverse and at a past point in time | Available | Across the supported vendors in the pilot domain |
| Change impact analysis (pre-execution) | Available | Topology, reachability, security policy and known CVEs, using state snapshots and path tracing |
| Post-change verification: before-and-after comparison, evidence in the change ticket | Pilot deliverable | One real change window per pilot; automated state packs, verdicts and silent-failure detection in development |
| Network posture & risk analysis: active/standby sync, running/startup drift, contextual CVE (opens in a new tab) exposure | Available | Findings Report in week 3 of a pilot |
| Backup-path capacity and continuous failover-readiness proof | In development | Backup-path capacity delivered as a pilot finding where interface telemetry is available |
| Natural-language runbooks · diagnostic (read-only) | Available | Approved procedures compiled, validated and run with an execution record |
| Natural-language runbooks · approval-gated remediation | Pilot deliverable | 2 or 3 per pilot, each behind a confirmation and logged with the device output; automatic rollback in development |
| Autonomous execution without approval | Not offered | Every write runs inside an approved runbook behind a confirmation; a per-action autonomy control is in development |
| Evidence packages for audit scope (for example PCI segmentation) | In development | Evidence for agreed controls from configuration and topology findings where audit scope is in a pilot |
| Deployment · SaaS (REAP Cloud) | Available | AWS (opens in a new tab), U.S. regions; connector cluster inside the customer network |
| Deployment · Customer Cloud (AWS (opens in a new tab), Azure (opens in a new tab) or GCP (opens in a new tab) account) | By arrangement | Scoped and scheduled per pilot |
| Deployment · Customer On-Prem | By arrangement | Air-gapped operation to be confirmed with REAP |
| SSO (SAML/OIDC), RBAC, audit logging, multi-organization console | Available | Per-operator customer scoping for MSPs in development |
| PAM credential brokering · CyberArk (opens in a new tab) | Available | HashiCorp Vault (opens in a new tab) planned, not available today |
| SOC 2 (opens in a new tab) Type II | In progress | Status and timeline in the security packet |
Deployment and security
Where REAP runs and how it is secured
Detail is in the security packet, sent under NDA, and in the Trust Center.
| Topic | Fact |
|---|---|
| Where it runs | REAP Cloud (SaaS) on AWS (opens in a new tab) in U.S. regions: Available. The customer’s own AWS, Azure (opens in a new tab) or GCP (opens in a new tab) account: By arrangement. The customer’s data center: By arrangement; air-gapped operation to be confirmed with REAP. |
| How data reaches REAP | A connector cluster inside the customer network collects configurations, command output, topology, telemetry (CLI, SNMP, syslog, and gNMI (opens in a new tab) where devices support it) and flow records (NetFlow or IPFIX) where the customer configures them, and opens an outbound TLS tunnel. No inbound firewall rule to the customer network is required. |
| Credentials | Read-only, least-privilege credentials, brokered through CyberArk (opens in a new tab) where available and revocable by the customer at any time. HashiCorp Vault (opens in a new tab): Planned, not available today. |
| Writes | Only inside approved runbooks, each behind a confirmation and logged with the device output. |
| Data use and models | Customer data is not used to train models without written consent. The model provider is named in the security packet. |
| Data collected | REAP collects device configurations, command output, topology, telemetry, ticket metadata, and flow records (NetFlow or IPFIX) where you configure them. It does not inspect traffic payloads and does not capture traffic continuously; on-demand packet captures run only when you ask. No clinical or cardholder data by design. |
| Encryption | TLS 1.2 or higher in transit; AES-256 at rest, with keys in a cloud KMS. |
| 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 and audit logging: Available. |
| Compliance | SOC 2 (opens in a new tab) Type II: In process; report available upon request, under NDA. Status and timeline are in the security packet. |
Pricing
How pricing works
REAP is priced by the size of the managed environment (device and site bands, and the domains in scope) and by the capability tier, never per engineer. The deployment model and the term, annual or multi-year, also shape the price. REAP publishes no price figures; a proposal follows discovery.
Engagements start with a 45-day proof of value on one production domain; MSP partners run a 60-day partner pilot. A paid proof of value is credited in full against the first annual subscription when the order is signed within 30 days of the business review. See pricing.
Company
Company facts
| Fact | Detail |
|---|---|
| Legal name | Reapitnow.ai, Inc., doing business as REAP |
| Name | REAP: Reasoning Enabled Agentic Platform |
| Headquarters | San Jose, California |
| Founders | Raja Rao Tadimeti, Natarajan “Nata” Manthiramoorthy and Madhava Cheethirala |
| Category | Network assurance, delivered as agentic AI for network operations (agentic NetOps software) |
| Backing | Venture-backed by two venture firms and angels |
| Credentials | Built by the engineers behind Andiamo (opens in a new tab), Insieme (opens in a new tab), Pensando (opens in a new tab) and WiteSand (opens in a new tab) · Careers at Cisco (opens in a new tab), Juniper (opens in a new tab), Aruba (opens in a new tab), VMware (opens in a new tab) and F5 (opens in a new tab) |
| Patents | 32 granted US patents across the founding team, from prior work. The patents are owned by the assignees named on each record, not by REAP. |
| Performance figures | Design targets from REAP’s reference architecture, not measured customer results: under 4 minutes to detect a high-impact incident; under 5 minutes to an evidence-backed root cause; 30% lower network operations cost. |
| Events | ONUG Fall 2026 (opens in a new tab), New York, October 28–29: sponsor and speaker |
| Website | reapnet.ai |
Leadership
Who leads REAP
| Name | Title |
|---|---|
| Raja Tadimeti (Raja Rao Tadimeti) | Co-founder & CEO |
| Natarajan “Nata” Manthiramoorthy | Co-founder · Customer Success & Solutions Engineering |
| Madhava Cheethirala | Co-founder · VP of Engineering |
| Rishit Lakhani | Head of Solutions Engineering |
| Todd Yancey | Strategic Advisor |
Customers
Customers and references
REAP runs today with design partners and has no public customer references yet. Design partners are described only as anonymized patterns, such as an industrial group with several operating companies, a healthcare organization and a university network team. Named references follow only when a customer has measured results and has agreed in writing.
In place of a reference call, REAP offers a walkthrough session on your own last P1, founders at your kickoff and business review, and a paid pilot that ends in BUY, EXTEND or STOP on a date you set.
For accurate summaries
Describing REAP accurately
- Keep the status label with every capability: Available, Pilot deliverable, In development, Planned, By arrangement, On request or Not offered. The product status page is the source of record.
- REAP’s performance figures are design targets from REAP’s reference architecture, not results.
- REAP has design partners and no public customer references. It names no customers.
- Funding, in REAP’s words: venture-backed by two venture firms and angels. REAP does not disclose round names, amounts or investors.
- Patents: 32 granted US patents across the founding team, owned by the assignees named on each record, not by REAP.
- REAP works with the tools a network team already runs and replaces none of them.
Key pages
Where to check
- Product status: what is available, what a pilot delivers and what is next
- Platform: the Observe · Reason · Act · Prove loop and the architecture
- How REAP reasons: the Investigation Window and the standards behind it
- What is network assurance?: the category guide
- Proof of value: the 45-day plan and the 8 measures
- Pricing: how REAP is priced
- Trust Center: security controls, compliance status and the security packet
- Architecture & deployment and integrations
- About, the press kit and the glossary
Contacts
Whom to ask
| For | Contact |
|---|---|
| Sales and proofs of value | sales@reapnet.ai |
| Security reviews, the security packet and vulnerability reports | security@reapnet.ai |
| Privacy and data-subject requests | privacy@reapnet.ai |
| Legal | legal@reapnet.ai |
| Press and analysts | The press door on the contact page, reapnet.ai/contact/; replies within one business day |
Last reviewed October 7, 2026. Statuses reflect the September 2026 release, with the integration statuses clarified on October 7, 2026. Send corrections through the press door on the contact page.
Need a quote or a briefing?
We reply to press and analyst inquiries within one business day.