FortiGate, Omada, Meraki & UniFi

Whatever network gear you've already standardized on across client sites, Nexus folds its monitoring into the same console as everything else — no separate vendor portal per brand.

How it works

FortiGate, TP-Link Omada, Meraki, and UniFi network monitoring inside the same endpoint management console as your Windows/Linux fleet
Network status and firewall posture surface next to device health, not in a fourth tab you have to remember to check
Findings feed the same ticket and alert pipeline as every other monitoring source — an issue on a client's firewall becomes a ticket with full context, not a notification in a vendor app
Part of the same outbound-only monitoring architecture as the rest of the platform — no additional inbound access requested at the client site to support it

Live as part of the endpoint management & RMM module, which runs in our own practice today.

Other integrations

Syncro

Moving off Syncro doesn't have to mean a hard cutover date. Nexus pulls your existing Syncro tickets in on a schedule so both systems can run in parallel until you're ready to switch.

Jamf

For clients on Apple hardware, Jamf-managed devices show up in the same unified console as everything else Nexus manages — one pane of glass across a mixed fleet.

Microsoft Intune

If a client is already on Microsoft 365 and managing devices through Intune, that fleet joins the same console as everything else instead of requiring a second admin center to check daily.

See FortiGate, Omada, Meraki & UniFi inside Nexus.

Join the design-partner cohort and we'll show you exactly how your existing stack folds into the console.