ServiceNow
Reads incidents and CMDB records (problem and change records where in scope); writes REAP’s findings and evidence links back to the ticket. Verdict fields on change records: in development
Integrations
Works with whatever you already have
REAP is the layer above your tools, not a replacement for them. Here is what it reads, what it writes, and how credentials work.
How credentials work. Read-only, least-privilege credentials for discovery, telemetry and reasoning, brokered through CyberArk (opens in a new tab) where available. Write access only for the runbooks you approve, each behind a confirmation and logged with the device output. You can revoke any credential at any time.
Everything below is in the September 2026 release unless it says “on request” (scoped per customer and confirmed before a pilot), “in development” or “planned” (not available today). See product status.
Planned, not available today: HashiCorp Vault (opens in a new tab), SolarWinds (opens in a new tab), Zabbix (opens in a new tab), PagerDuty (opens in a new tab), Opsgenie (opens in a new tab), Confluence (opens in a new tab) and SharePoint (opens in a new tab); tell us which you need. NetBox (opens in a new tab) reconciliation on request. REAP collects its own telemetry today, and incidents your monitoring raises reach REAP through ServiceNow (opens in a new tab) or Jira (opens in a new tab).
ITSM
Jira
Reads and updates issues; writes evidence links (verdict fields: in development)
ManageEngine
ServiceDesk tickets and CMDB records
Privileged access
CyberArk
Brokers device credentials for read-only collection; no standing device credentials in REAP where the broker is used
HashiCorp Vault
Planned, not available today; tell us if you need it
Monitoring & telemetry
Syslog · SNMP · gNMI · CLI · flow records
Native collection through the connector cluster: SNMP polling and traps, syslog, CLI over SSH, gNMI (opens in a new tab) where devices support it, and flow records (NetFlow or IPFIX) where you configure them. No payload inspection and no continuous packet capture
SolarWinds · Zabbix · other monitoring
REAP investigates the incidents your monitoring raises in ServiceNow (opens in a new tab) or Jira (opens in a new tab), with the network context it has discovered; direct SolarWinds (opens in a new tab) and Zabbix (opens in a new tab) connectors are planned, not available today
On-call & collaboration
Slack · Microsoft Teams
Investigation summaries and runbook results where your workflow lives; in-chat approvals confirmed per pilot
PagerDuty · Opsgenie
Planned, not available today; the Investigation Window reaches on-call through ServiceNow (opens in a new tab), Slack (opens in a new tab) or Microsoft Teams (opens in a new tab)
Knowledge
Runbooks and documents
Runbooks, SOPs, design documents and conventions ingested as citable reasoning context (file upload and agreed exports today)
Confluence · SharePoint
Planned, not available today: document spaces as reasoning context
NetBox
On request: reconciliation of discovered inventory against NetBox (opens in a new tab)
Identity
Okta
Microsoft Entra ID (formerly Azure AD)
SSO via SAML/OIDC; role mapping
Cloud & controllers
AWS · Microsoft Azure
Cloud network constructs (VPC/VNet, security groups, route tables, gateways, VPN) and hybrid path visibility
Juniper Mist · Aruba Central · Cisco Meraki
Controller-managed estates; the inventory, client and event data read is confirmed per pilot
Network infrastructure
Cisco · Arista · Juniper · HPE Aruba
Switching, routing and wireless estates
Palo Alto Networks
Firewall and policy context in investigations and change checks
Fortinet · SONiC · others
Coverage confirmed per pilot against your platforms and versions
Missing something?
Tell us the system and how it fits your workflow. Integrations are scoped in week 0 of a proof of value.