NetCrunch is an agentless network and server monitoring platform from AdRem Software, built for IT teams and MSPs that want discovery, topology maps, performance monitoring and alerting from a single Windows server instead of a stack of separate tools. If you searched for a NetCrunch download, note that it is a commercial product: the installer is free to download and runs as a full-featured trial, but continued use requires a paid licence.
The current major release is NetCrunch 16. It installs on 64-bit Windows Server and monitors far more than Windows: Linux, macOS and BSD hosts, switches, routers, firewalls, printers, UPS units, virtualization hosts and cloud services, mostly over SNMP, WMI, SSH and vendor APIs. You manage it from a web console or a desktop console.
NetCrunch at a glance
| Item | Details |
|---|---|
| Latest version | 16.0.3 (29 September 2026) |
| Licence | Commercial, licensed by monitored nodes; trial available; no free edition of NetCrunch itself |
| Platforms | Server: 64-bit Windows Server 2016, 2019, 2022, 2025. Consoles: web browser, desktop console on Windows 10 or later |
| Developer | AdRem Software |
| Official website | adremsoft.com |
| Best for | Small and mid-size networks and MSPs that want one monitoring server with maps, flows and alerting out of the box |
What it does
- Discovers devices on IP ranges and builds automatic Layer 2 topology and VLAN maps, plus custom diagrams and dashboards.
- Monitors without agents using built-in monitoring packs (AdRem lists 680+ monitoring targets) over SNMP v1/v2c/v3, WMI, SSH, HTTP and REST APIs.
- Collects NetFlow-type traffic data to show which hosts and applications use bandwidth; version 16 adds a new distributed Flow Server.
- Tracks device configuration changes so you can spot unauthorized edits on network gear.
- Raises alerts with correlation, escalation and automation actions, and integrates with ticketing; v16 adds predictive thresholds and ServiceNow integration.
- Covers newer targets in v16 such as Proxmox VE clusters, Windows DHCP scope usage, Meraki cloud and multi-step web transactions.
- Scales out with remote monitoring probes, including load balancing, failover and an offline probe mode in v16.
- Offers remote access to the consoles through NetCrunch Connection Cloud, an outbound HTTPS tunnel, so you do not have to open inbound ports.
How sysadmins use it
Bring a new site under monitoring
- Install NetCrunch on a dedicated Windows Server VM and let the setup wizard scan the IP ranges you enter.
- Before the scan, add credentials: SNMP communities or v3 users for network gear, a domain account with WMI rights for Windows, SSH accounts for Linux.
- Review the discovered nodes; NetCrunch assigns monitoring packs by device type (Windows server, Linux, switch, printer and so on).
- Open the automatically generated Layer 2 map to confirm uplinks and find devices that were discovered without SNMP data.
Watch switch ports and bandwidth
- Enable SNMP on switches and routers and add them with the right SNMP profile.
- Configure the devices to export flow data to the NetCrunch server or a Flow Server.
- Use the interface views and flow reports to find saturated uplinks and top talkers, then set thresholds on interface utilization.
Tune alerting so it is useful
- Start from the default alerting scripts, then disable notifications for non-critical device groups.
- Use escalation: first a notification to the on-call technician, then email to the team if the condition persists.
- Use the node status policy and dependencies so a failed uplink produces one alert instead of one per device behind it.
Install and first run
Server. NetCrunch Server runs only on 64-bit Windows Server 2016, 2019, 2022 or 2025. AdRem’s minimum is two processors and 3.5 GB of RAM; on a VM give it at least 4 cores and 4 GB, and plan 8 or more cores for 1,000+ nodes. Use SSD storage. The server includes its own web server and event database (PostgreSQL in v16), so there is no separate database to install.
Consoles. The web console works in current Chrome, Edge, Firefox, Safari and Opera. The optional desktop console needs Windows 10 or later. A mobile progressive web app with push notifications is also available.
Ports and gotchas.
- The web console listens on port 80 by default and can be moved to 443 once you install a proper certificate; the desktop console connects on port 12009. Both ports can be changed.
- Do not expose port 12009 directly to the internet; AdRem recommends a reverse proxy, or use NetCrunch Connection Cloud for remote access.
- Exclude NetCrunch data folders from antivirus scanning and avoid running other monitoring or database services on the same machine.
- On a VM, reserve the memory; NetCrunch should not be swapping.
- WMI monitoring of Windows hosts needs a domain account with the right permissions and the Windows firewall rules for remote management.
Limitations
- It is commercial software. After the trial ends you need a licence; there is no permanent free tier of NetCrunch itself.
- The server is Windows-only. Linux-first teams that want to run everything on Linux will prefer other tools.
- It is a closed, vendor-supported product, so you depend on AdRem for new monitoring packs and fixes, although custom scripts and REST/OTLP data can fill gaps.
- Large networks need real hardware: CPU, RAM and fast disks matter once you monitor thousands of interfaces.
- AdRem’s separate free NetCrunch Tools (ping, traceroute, SNMP scanner, Wake-on-LAN and others) are handy but are a different product, not a free version of the monitoring server.
NetCrunch vs alternatives
| Tool | Licence | How it compares |
|---|---|---|
| PRTG Freeware | Free up to 100 sensors | Also a Windows-based all-in-one monitor; counts sensors rather than nodes, so the free tier covers roughly ten devices. |
| Checkmk Community | Free, open source | Runs on Linux, strong auto-discovery of services; more hands-on to set up, no node-based licensing. |
| PA Server Monitor | Free edition for 1 server | Windows server monitoring focus; the free edition is limited to basic checks. |
Choose NetCrunch when you want maps, flows and agentless monitoring working on day one and are prepared to pay per node. Choose an open-source tool such as Checkmk or Zabbix when budget matters more than setup time.
FAQ
Is there a free version of NetCrunch?
No. NetCrunch is commercial software that you can evaluate with a trial. AdRem separately offers free NetCrunch Tools, a set of desktop utilities such as ping, traceroute, SNMP scanner and Wake-on-LAN, which are not the monitoring server.
What do I need for a NetCrunch download and install?
A 64-bit Windows Server 2016, 2019, 2022 or 2025 machine with at least two processors, 3.5 GB of RAM (4 cores and 4 GB on a VM) and SSD storage. You then use the web console from any modern browser.
Can NetCrunch run on Linux or macOS?
The server cannot; it installs only on Windows Server. It can monitor Linux, macOS, BSD and network devices, and the web console works from any operating system.
NetCrunch vs PRTG: which should I pick?
Both are Windows-hosted all-in-one monitors. NetCrunch licenses by nodes and includes topology maps and flow analysis; PRTG licenses by sensors and has a free edition limited to 100 sensors. Test both on a slice of your network.
What are the NetCrunch Tools?
They are AdRem’s free admin toolset for Windows: scanners (ping, service, open TCP port, SNMP), TCP/IP tools and subnet utilities, including a MAC resolver that can send Wake-on-LAN packets.
Which ports does NetCrunch use?
By default the web console uses port 80 (or 443 with a certificate) and the desktop console uses port 12009. Monitoring itself uses the protocols of the targets: SNMP, WMI, SSH, HTTP and flow exports.
How do I access NetCrunch remotely?
Use NetCrunch Connection Cloud, where the server opens an outbound encrypted tunnel and clients connect through it, or publish the web console behind a reverse proxy. Avoid exposing the desktop console port directly.
Last checked against official sources: 1 October 2026 (developer website: adremsoft.com). Versions and licence terms change — confirm on the developer's site before deploying in production.






