No more typing reviews! Try our Samantha, our new voice AI agent.

Loom Systems vs NetCrunch comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 9, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Loom Systems
Ranking in IT Infrastructure Monitoring
61st
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
4
Ranking in other categories
Anomaly Detection Tools (5th)
NetCrunch
Ranking in IT Infrastructure Monitoring
64th
Average Rating
8.0
Number of Reviews
3
Ranking in other categories
Network Monitoring Software (79th), Server Monitoring (27th), Log Management (54th)
 

Mindshare comparison

As of April 2026, in the IT Infrastructure Monitoring category, the mindshare of Loom Systems is 0.5%, up from 0.2% compared to the previous year. The mindshare of NetCrunch is 0.7%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Infrastructure Monitoring Mindshare Distribution
ProductMindshare (%)
Loom Systems0.5%
NetCrunch0.7%
Other98.8%
IT Infrastructure Monitoring
 

Featured Reviews

Keerthi Kumar Sangaraju - PeerSpot reviewer
Technology Manager at a tech services company with 10,001+ employees
Stable, easy to set up, flexible, and has multiple functionalities, but needs to define priority levels for each incident
What's lacking in Loom Systems is the level of priority for each incident. For example, after implementation and there was a huge impact on the client, and the client comes back to you and says that there's an incident, that there needs to be an immediate resolution for it, you'll see severity one, severity two, etc., in Loom Systems, rather than priority levels. It would be better if the incidents can be defined as low priority, medium priority, or high priority.
it_user1038504 - PeerSpot reviewer
Senior Systems Administrator, Technical Lead at Connectivity Wireless
A network monitoring platform with a useful reporting feature, but permission-based options could be better
The initial setup is fairly easy. Most of it's wizard-based. You don't have to be a rocket scientist to set it up. But if you don't know certain things related to protocols and everything else, it might be difficult. If you know how SNMP works, it'll be fairly simple to set up.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The solution is very scalable; a company wouldn't have any issues expanding it if they needed to, and we have a few thousand users on the solution."
"What I like best about Loom Systems is that you can use it for infrastructure monitoring. I also like that it's a flexible solution."
"The RFS portion of the solution is the product's most valuable feature."
"The solution is absolutely scalable."
"You can develop your own apps within Loom, and they can be configured very simply."
"Bringing Loom in ensures that the incident process, request process, change, all of these processes are improved."
"What I like best about Loom Systems is that you can use it for infrastructure monitoring and that it's a flexible solution."
"The solution is absolutely scalable. If an organization needs to expand it out they definitely can."
"Reporting on NetCrunch is pretty good; it's very similar to SolarWinds, just with a different interface, and the majority of everything there was beneficial."
"The setup is very intuitive and quick - it all just took a few minutes we were done."
"Reporting on NetCrunch is pretty good. It's very similar to SolarWinds. It's just a different interface. The majority of everything there was beneficial."
 

Cons

"What's lacking in Loom Systems is the level of priority for each incident. For example, after implementation and there was a huge impact on the client, and the client comes back to you and says that there's an incident, that there needs to be an immediate resolution for it, you'll see severity one, severity two, etc., in Loom Systems, rather than priority levels. It would be better if the incidents can be defined as low priority, medium priority, or high priority."
"The change management within the solution needs to be improved. There needs to be more process automation."
"The reporting is a bit weak. They should work to improve this aspect of the product."
"The discovery and mapping still takes a lot of human intervention, it's quite resource heavy,"
"The discovery and mapping still takes a lot of human intervention, it's quite resource heavy, especially in the initial setup which can take six months of work, especially when you have a large estate that you're dealing with."
"What's lacking in Loom Systems is the level of priority for each incident."
"The change management within the solution needs to be improved. There needs to be more process automation."
"The reporting is a bit weak."
"I didn't care for the role-based, permission-based options, which were not the best."
"Our network is made up of a lot of Cisco devices, and it needs improvements."
"I didn't care for the role-based, permission-based options, which were not the best."
report
Use our free recommendation engine to learn which IT Infrastructure Monitoring solutions are best for your needs.
885,667 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Construction Company
24%
Comms Service Provider
11%
Manufacturing Company
8%
Agriculture
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
No data available
 

Overview

 

Sample Customers

Citrix, Amdocs, Sysaid, Hexaware, Effibar, Revtrak, Taptica
manufacturing, banking, utilities, energy, universities, healthcare institutions, school districts, military and police entities, non-profit organizations, 
Find out what your peers are saying about Loom Systems vs. NetCrunch and other solutions. Updated: March 2026.
885,667 professionals have used our research since 2012.