External reviews
4,127 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Easy to Use, Quick to Deploy, and Great for Automation
What do you like best about the product?
It’s easy to use, quick to deploy, and handles automation
What do you dislike about the product?
Ticketing system feels underdeveloped compared to dedicated tool
What problems is the product solving and how is that benefiting you?
Brings monitoring, patching, and remote access into one place
Easy to Use, Quick to Deploy, and Strong Automation for IT Management
What do you like best about the product?
It’s easy to use, quick to deploy, and handles automation (patching, monitoring, alerts) really well—so you get strong IT management without the usual complexity.
What do you dislike about the product?
Ticketing system feels underdeveloped compared to dedicated tool
What problems is the product solving and how is that benefiting you?
Automates repetitive tasks
Easy to Use, Quick to Deploy, and Great for Automation
What do you like best about the product?
It’s easy to use, quick to deploy, and handles automation
What do you dislike about the product?
Limited granularity in permissions/roles in certain cases
Slow rollout / deployment can be frustrating
Slow rollout / deployment can be frustrating
What problems is the product solving and how is that benefiting you?
Automates repetitive tasks
Catches issues early
Catches issues early
Quick, Responsive Interface with Regular Updates
What do you like best about the product?
The interface is quick and responsive. Loading between pages and across devices is fast, which really matters when I’m using it every day.
Feature and bugfix updates come often and regularly.
Feature and bugfix updates come often and regularly.
What do you dislike about the product?
When I use the "Remote" functionality and run into an issue, the message is not informative and simply says "error". It would be much more helpful if it provided a bit more context, such as whether the device is responding but still waiting for agent installation, or what step it’s failing on.
What problems is the product solving and how is that benefiting you?
For monitoring and patching servers and network equipment. I also run custom scripts across multiple servers, either to check specific things (like expiring secrets) or to make changes when needed.
Easy to Navigate, Responsive, and Integrates Smoothly with Halo
What do you like best about the product?
Easy to navigate with links to other features, recent tab is very useful
easy to create custom scripts and polices
integrates well with Halo ticketing system
system is very responsive
was given informative training session before first using
easy to create custom scripts and polices
integrates well with Halo ticketing system
system is very responsive
was given informative training session before first using
What do you dislike about the product?
The dashboard view shows critical issues less clearly than other monitoring systems.
What problems is the product solving and how is that benefiting you?
Reliable remote control software with granular control, making it easy to set up custom settings for different customers and devices.
Unified Interface with Exceptional Remote Management and MSP Documentation
What do you like best about the product?
Single unified interface with excellent remote management capabilities, and the documentation that supports MSPs is exceptional.
What do you dislike about the product?
I would like to hide closed tickets by default and be able to save the filters. I do still need to complete the course, so this may be my fault that I'm not using the product correctly.
What problems is the product solving and how is that benefiting you?
We need a ticketing and RMM system. Of all of the ticketing and RMM tools that I've used, NinjaOne is one of the best, by far.
NinjaOne: Responsive, Easy to Use, and Scales to Thousands of Endpoints
What do you like best about the product?
NinjaOne is very responsive and easy to work with , it can easily handle a few thousand endpoints
What do you dislike about the product?
altough improvements have been made, reporting for patch management could be better
What problems is the product solving and how is that benefiting you?
Managing large amount of endpoints across multiple customers
Gathering insights in health of those endpoints
Remote controll
Gathering insights in health of those endpoints
Remote controll
Easy to Use, Quick to Deploy, and Strong Automation for IT Management
What do you like best about the product?
It’s easy to use, quick to deploy, and handles automation (patching, monitoring, alerts) really well—so you get strong IT management without the usual complexity.
What do you dislike about the product?
Limited granularity in permissions/roles in certain cases
Slow rollout / deployment can be frustrating
Ticketing system feels underdeveloped compared to dedicated tool
Slow rollout / deployment can be frustrating
Ticketing system feels underdeveloped compared to dedicated tool
What problems is the product solving and how is that benefiting you?
Brings monitoring, patching, and remote access into one place
Automates repetitive tasks
Catches issues early
Automates repetitive tasks
Catches issues early
All-in-One Monitoring and Enforcement in One Tool
What do you like best about the product?
We are getting both monitoring and enforcement (software, policies) in one tool.
What do you dislike about the product?
It would be better to provide more detailed information about the remediation steps.
What problems is the product solving and how is that benefiting you?
NinjaOne performs automated patching to ensure device compliance, reducing the need for additional staffing to manage this responsibility.
Clean, Fast UI and Reliable Remote Access That Keeps Our Distributed Team Moving
What do you like best about the product?
The UI is the standout for me. It's clean, fast, and organized in a way that actually matches how you think about managing endpoints — device groups, policies, and scripting are all a click or two away without digging through nested menus. New techs on my team get productive quickly, which matters when you're running IT for a distributed construction workforce where field supervisors don't have time to wait on tickets.
The remote access is genuinely fast. Even when I’m connecting to a device on a job site with marginal connectivity, it still works reliably, and that alone has saved me hours each week.
The remote access is genuinely fast. Even when I’m connecting to a device on a job site with marginal connectivity, it still works reliably, and that alone has saved me hours each week.
What do you dislike about the product?
Reporting is the weak spot for me. The built-in reports cover the basics, but they consistently don’t surface the level of detail I actually want—whether that’s deeper hardware inventory fields, more granular patch history, or simply the ability to pull exactly the columns I need without having to wrestle with filters. As a result, I end up exporting data and massaging it elsewhere more often than I should. Custom report building exists, but it still isn’t as flexible as I’d expect from a platform that feels this polished in other areas.
What problems is the product solving and how is that benefiting you?
NinjaOne brings together three things we used to manage separately: ticketing, patch management, and our knowledge base. Having everything in one pane of glass means my team isn’t constantly context-switching between tools just to resolve an issue. When a ticket comes in, we can immediately see the endpoint’s patch status and pull up the relevant KB article without ever leaving the console.
Patch management on its own has been a major win for us. Automated deployment across our fleet keeps systems current without anyone manually chasing down machines, which matters a lot when a good portion of our endpoints are out on job sites instead of sitting in an office.
Because ticketing is integrated with the RMM side, techs get device context right inside the ticket. There’s no digging around for asset details or jumping between remote session tools, and it’s noticeably reduced our resolution time.
Keeping the knowledge base in the same platform also means documentation actually gets used. When the KB is a click away from the ticket, techs reference it instead of reinventing the solution every time.
Patch management on its own has been a major win for us. Automated deployment across our fleet keeps systems current without anyone manually chasing down machines, which matters a lot when a good portion of our endpoints are out on job sites instead of sitting in an office.
Because ticketing is integrated with the RMM side, techs get device context right inside the ticket. There’s no digging around for asset details or jumping between remote session tools, and it’s noticeably reduced our resolution time.
Keeping the knowledge base in the same platform also means documentation actually gets used. When the KB is a click away from the ticket, techs reference it instead of reinventing the solution every time.
showing 61 - 70