Glossary / RMM (Remote Monitoring and Management)
Software that lets an MSP monitor device health and perform remote management tasks — patching, scripting, remote control — across every client site from one console.
An RMM agent runs on managed endpoints (workstations, servers, sometimes network gear) and reports health data — CPU, disk, uptime, security posture — back to a central console, while also giving a technician remote hands: run a script, deploy a patch, open a remote-control session, without a truck roll.
The two things that separate a good RMM from a risky one are usually the same two things: how it reaches the device (does it require an open inbound port, or does the agent phone home outbound-only?) and how it authorizes a command (does the device trust anything that arrives over the right connection, or does it verify a cryptographic signature first?).
Most MSPs run RMM alongside a PSA for ticketing — historically two separate tools connected by an integration, which is exactly the seam a combined PSA+RMM platform is built to remove.
How Nexus handles this
Nexus runs a native outbound-only agent for Windows and Linux with Ed25519-signed remote jobs, plus one console over Jamf, Intune, NinjaOne, and Action1 for whatever else you already run.
A company that remotely manages a client's IT infrastructure and end-user systems on an ongoing, proactive basis — usually a flat-fee contract, not break-fix billing.
Software that runs the business side of MSP operations — ticketing, SLAs, billing, contracts, and client records — the system of record most MSP work flows through.
AI that can take multi-step action toward a goal — diagnose, draft, and (within a defined policy) act — rather than just respond to a single prompt.
Join the design-partner cohort and we'll show you exactly where this lives.