1 million+ businesses helped. Get advice
Get Free Advice
Nlyte DCIM vs runZero
User Ratings & Reviews
Reviews are generated by real users. When reviewing a product, users are asked to assess the product’s overall quality, which includes assigning specific ratings for ease of use, value for money, customer support, and functionality.
Ease-of-Use
3.9 / 5
4.9 / 5
Value for Money
4.1 / 5
4.9 / 5
Customer Support
4.4 / 5
4.9 / 5
Functionality
4.2 / 5
4.8 / 5
Last Review Written
September 17, 2021
August 23, 2023
Pros/Cons
Pros
- Out of many, the most impressive feature I found is Nlyte Asset Optimizer (NAO) that makes asset lifecycle management very efficient.
- I am quite happy with the nlyte product, even if to use it at its best, there is an need for an efficient organization of people who keep everything up to date.
- I have both integrated into my CMBD allowing me to pass CI data and providing updated records for ticket resolution. I like the easy of use related to customizing the applications.
Cons
- Conversion was very painful. Some data was not populated correctly, other data was dropped.
- Converting from previous DCIM tool was painful. After the conversion, the users are content with it.
- If you have a problem, they might call it a feature request and it will never get looked at again. If you see something in their demos, it will probably cost another 50k.
Pros
- I like the ease of deployment and the versatility of the agents. I'm running on multiple operating systems and hardware platforms and they all work amazing.
- Ease of operationAbility to accurately fingerprint assets with better contextUnauthenticated approach to asset discovery and fingerprinting.
- The visibility that this tool provides is fantastic. It was an easy sell to me for features and an easy sell to my boss as far as cost.
Cons
- During the beta testing of the application the only grip I had was when the scanner would fall off line, you would have to start over. The devices it has already scanned would be lost.
- I initially index data in. Jsonl file with Elasticsearch (ES) It works well with a small dataset, but for large dataset, it fails miserably b/c of the number of fields in the jsonl file.
- No option for scanning for additional information with a password.
Pricing
Pricing Range
$
$
$
$
$
$
$
$
$
$
Product Demo & Screenshots
Product Demo
N/A
N/A
Advisor Recommendations & User Awards
FrontRunners
The top products based on usability and customer satisfaction, as rated by user reviews. Check out our full methodology description for more detail.
N/A
N/A
Advisor Recommendations
Our industry-specific advisors recommend products based on specific business needs. Connect with us to get your personalized recommendations.
N/A
N/A
Additional Info
Ideal Customer Size
Small
Medium
Large
Small
Medium
Large
Deployments
Cloud, SaaS, Web-Based
Desktop - Mac
Desktop - Windows
Desktop - Linux
Desktop - Chromebook
On-Premise - Windows
On-Premise - Linux
Mobile - Android
Mobile - iPhone
Mobile - iPad
Cloud, SaaS, Web-Based
Desktop - Mac
Desktop - Windows
Desktop - Linux
Desktop - Chromebook
On-Premise - Windows
On-Premise - Linux
Mobile - Android
Mobile - iPhone
Mobile - iPad
Support and Training
Support
Email/Help Desk
FAQs/Forum
Knowledge Base
Phone Support
24/7 (Live Rep)
Chat
Email/Help Desk
FAQs/Forum
Knowledge Base
Phone Support
24/7 (Live Rep)
Chat
Training
In Person
Live Online
Webinars
Documentation
Videos
In Person
Live Online
Webinars
Documentation
Videos
