NinjaOne NMS is NinjaOne's network monitoring and management suite, built for equipment where the platform agent cannot be installed: managed switches, routers, firewalls, printers and storage answering SNMP. Collection runs through the NMS Delegate, installed on a Windows machine in the network, with Network Discovery, vendor OID mappings, Custom SNMP, NetFlow, Syslog and configuration backup. It is contracted as part of the platform, on an annual subscription.
NinjaOne NMS is NinjaOne's network monitoring and management suite, built for the equipment where the platform agent cannot be installed: managed switches, routers, firewalls, printers, storage arrays and any device that answers SNMP. Collection runs through a dedicated component, the NMS Delegate, installed on a Windows machine inside the customer network, which discovers the equipment and sends data to the NinjaOne console.
The problem it solves is the other half of the inventory. The platform covers agent-managed workstations and servers, but the link that dropped, the switch that saturated and the printer that stopped appear nowhere — and those stop everyone's work at once. Without SNMP, IT learns about the incident a user ticket rather than an alert.
NMS recognises any SNMP-managed device conforming to MIB-2, standardised in RFC 1213, delivering system description, uptime and network interfaces with no extra configuration.
Time to detect the cause drops because the alert comes the network equipment rather than the user: interface saturation, link loss and switch reboots raise an event in the console before becoming a ticket. Investigation is shorter because traffic flow, syslog and equipment inventory sit in the same base as workstation data, removing the need to cross two tools to tell whether the slowness was the computer or the network.
Change control improves because configuration backup keeps the equipment state before the change, allowing comparison and rollback when a VLAN or rule change takes a service down. And there is no extra console to operate, because NMS lives inside the platform the team already uses.
NinjaOne NMS serves infrastructure analysts and coordinators responsible for the network, teams supporting multiple sites, and managed service providers. Three scenarios: the head office with branches where nobody knows which link is degraded; the fleet of network printers noticed only when they stop; and the operation proving in an audit what the firewall configuration was before a change.
The shared console is the structural differentiator: the same dashboard showing a workstation's pending patch shows the switch's saturated interface, which changes incident diagnosis — the team stops treating network and endpoint as two worlds with separate tools.
The second differentiator is the openness of the collection model. Because Custom SNMP accepts customer-defined OIDs, equipment that does not follow the standard for CPU or memory can still be monitored, without waiting for NinjaOne to publish specific support for that model. That matters in a heterogeneous estate, which is the rule rather than the exception in corporate networks.
The NMS Delegate is a separate installation the NinjaOne monitoring agent, and the two can coexist on the same machine. According to NinjaOne, the component runs only on 64-bit versions of Microsoft Windows, with Windows Server recommended because of the load generated by discovery, log capture and SNMP monitoring. Requirements are a quad-core CPU at 3.0 GHz or higher, 8 GB of RAM — 16 GB recommended — and 50 GB of disk. From 100 monitored devices onward, NinjaOne advises performance tuning.
One topology constraint is decisive in project design: SNMP credentials work a probe on the same subnet and fail a different one. The official recommendation is one NMS Delegate per site rather than monitoring over VPN, because latency causes false alerts and discovery inaccuracy. The firewall must open the collection ports, among them UDP 514 for Syslog, UDP 2055 for NetFlow and UDP 6343 for sFlow; configuration backup uses SSH on port 22. Removing the NMS service requires NinjaOne Support action.
NinjaOne NMS is not sold in named editions. The variation lies in the collection scope enabled by policy and in the flow module: basic SNMP monitoring with MIB-2, vendor mappings, Custom SNMP, NetFlow and Syslog collectors, and configuration backup. Each discovered device receives a role that determines the applied policy.
One architectural point counts as scope: the Network Discovery utility, run the platform, replaced the legacy NMS download and installer. The NMS product remains active — what changed is how discovery is triggered, now native in the console, with the NMS Delegate still required for collection. For agent-managed workstations, laptops and servers the product is the NinjaOne platform; for phones and tablets, NinjaOne MDM.
NinjaOne NMS is contracted as part of the NinjaOne platform, on an annual subscription, and the billing base follows the platform's per-device count: each network device discovered and added to the console enters as one monitored device. NinjaOne does not publish a licensing page specific to NMS, so that count should be confirmed during scoping before a proposal is closed.
There is no single list figure because the investment depends on scope: how many network devices are monitored, how many sites — each site tends to require its own NMS Delegate — which collection modules are enabled, the base platform edition, and whether this is a new purchase or a renewal. An illustrative scoping example: a company with a head office and three branches totalling 60 SNMP devices must plan for four NMS Delegates, one per site, plus licenses for the 60 monitored devices. The composition is illustrative; the one-delegate-per-site recommendation is official.
To buy NinjaOne NMS in Brazil, OSB Software maps that scope with you, sends the commercial proposal, issues the Brazilian invoice and delivers the licenses — request a quote to get the exact figure for your scenario.
Which equipment can NinjaOne NMS monitor? Any SNMP-managed device conforming to MIB-2 RFC 1213 — switches, routers, firewalls, printers and storage. For a set of vendors there are additional OIDs surfacing CPU, memory and serial numbers; outside that set, Custom SNMP allows mapping your own OIDs.
Do I need an NMS Delegate at every company site? That is the official recommendation. SNMP credentials work on the probe's own subnet and fail on a different one, and monitoring over VPN causes false alerts latency. Plan one delegate per site.
Does the NMS Delegate run on Linux or any machine? No. Only 64-bit Windows is supported, with Windows Server recommended, a quad-core 3.0 GHz CPU, 8 GB of RAM and 50 GB of disk. Above 100 monitored devices, performance tuning is needed.
Was NMS discontinued when Network Discovery arrived? No. What was replaced was the legacy NMS download and installer: discovery is now triggered straight the platform. The NMS Delegate remains the component that collects data the equipment.
OSB Software is an official NinjaOne partner in Brazil and supplies 100% genuine NinjaOne NMS licenses to companies, with Brazilian invoicing, local contracting in Portuguese and full legal compliance — the safe way to buy imported software under a Brazilian corporate entity, with no risk of irregular licensing.
When you buy NinjaOne NMS OSB Software, you get:
If you are looking for where to buy NinjaOne NMS in Brazil with legal certainty and properly licensed imported software, request a quote: OSB Software delivers reliable technology, qualified support and a simple, transparent purchase.
You don't know what software you need or you haven't found what you were looking for? We have a team ready to help you choose the right software for your company.