Product status
What is available, what a pilot delivers, what is next
We label capabilities the way we label numbers: available today, a pilot deliverable built on shipped capabilities, in development, or by arrangement. Nothing in development is sold as available.
Labels. Available: in the September 2026 release and shown on request. Pilot deliverable: delivered inside a proof of value using shipped capabilities. In development: scheduled and shown under NDA; design partners shape it first. By arrangement: scoped per customer. Planned: an integration on the roadmap, not available today and without a date. Nothing in development or planned is sold as available.
Last reviewed October 7, 2026 · Owner: REAP product management · Send corrections to security@reapnet.ai
| Capability | Status | Notes |
|---|---|---|
| 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; in a pilot your engineers score evidence traceability |
| 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 | Assesses a proposed change against 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 verified with your team in every 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 is 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 | Two or three runbooks 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 produced 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 your network |
| Deployment · Customer Cloud (your AWS (opens in a new tab), Azure (opens in a new tab) or GCP (opens in a new tab) account) | By arrangement | Kubernetes-based platform deployable in your account; scoped and scheduled per pilot |
| Deployment · Customer On-Prem | By arrangement | Kubernetes (opens in a new tab) on your compute, scoped per customer; air-gapped operation to be confirmed with REAP |
| SSO (SAML/OIDC), RBAC, audit logging, multi-organization console | Available | Platform services; per-operator customer scoping for MSPs in development |
| PAM credential brokering · CyberArk (opens in a new tab) | Available | Where the customer runs CyberArk (opens in a new tab); HashiCorp Vault (opens in a new tab) planned |
| SOC 2 (opens in a new tab) Type II | In process | Report available upon request; status and timeline in the security packet |
Statuses reflect the September 2026 release.
Want to see a capability on your network?
Every pilot is scoped to the use cases that matter to you and measured against your baseline. Need something marked in development? Design partners shape it and see it first; ask for a seat.