Overview
Product Information on NinjaOne
What is NinjaOne?
NinjaOne Pricing
NinjaOne Product Images


NinjaOne unifies IT to simplify work for 35,000+ customers in 140+ countries. The NinjaOne Unified IT Operations Platform delivers endpoint management, autonomous patching, backup, and remote access in a single console to improve efficiency, increase resilience, and reduce spend. Intelligent automation and human-centered AI gives employees a great technology experience.
Do You Manage Peer Insights at NinjaOne?
Access Vendor Portal to update and manage your profile.
Three things stand out to me that make NinjaOne a winning product: 1) A simple, consistent user interface - especially impressive given how many areas of IT it covers. Other platforms I've used often feel disjointed, overly gimmicky (force A.I. or other features without a solid foundation), and poorly organized. 2) A clear roadmap, along with concise and regular product updates that show steady meaningful progress in product improvement. 3) A strong online presence (Online documentation, YouTube training, etc.) that supports ongoing training and help IT staff stay current and trained on new features.
Dashboard single-pane-of-glass visibility. Ease of deployment for smaller implementations. Image restorations are straightforward.
Reliability - reaches our endpoints and accurately reports when actions weren't taken because of a lack of connectivity. Automation - allows us to schedule actions or have actions automatically taken based on conditions that the platform monitors for. Responsiveness - when we do have a problem, support is quick to respond and provide an answer, even if the answer is not what we were hoping to hear, it's clear they know the product and are getting you in touch with internal teams who know it as well, not script-readers who can't even understand your issue. When you get an answer, it's clear, precise, and accurately describes how the product works, even if you wish it worked differently. Short development lifecycle - issues our team has brought up in tickets have shown up as bug fixes or new features in subsequent releases, sometimes just a few weeks after pointing them out, as opposed to years later as with other vendors.
In terms of areas for improvement, the NinjaOne ticketing module is solid overall, but where NinjaOne has the most opportunity to evolve: 1) Greater customization of the technician interface, such as easily showing/hiding fields, the ability to modify basic default drop downs (like status, ticket type, priority, severity, etc.), and enabling role-based technician/manager permissions for actions like the ability to modify or delete comments. 2) An improved end-user experience, such as including more flexible and customizable ticket intake forms, support for multiple intake forms (i.e. IT support, feature requests, hardware/software requests) that may have different fields, and enhancements to both the system tray app and client portal to better support these use cases. 3) Better handling of user mistakes, in example end users sometimes reply to the wrong ticket or include sensitive information (like passwords). There should be a way for a IT leader (CTO, VP, Director, Manager) to have permissions to remove or redact these comments when necessary. 4) Email notifications - while the notification templates themselves are customizable, the notification workflows currently are not, and often there are duplicate notifications such as when an end user replies by email back to the ticket, we will get their original ticket reply, and the update to the ticket, which means we basically get the same reply from the end user twice vs. if they clicked the link and updated the ticket, directly - in that case we'd only get a notification of the update once, this is both annoying and redundant.
Staggering backup times is cumbersome. Not great visibility into different backup schedules and configurations. Support is lacking, and the documentation isn't great.
Sometimes it seems as if new features are prioritized over quality of life improvements that could save us vast amounts of time every day we use the product. Lack of granularity in technician permissions can lead to unwanted overprovisioning in order to allow technicians to work effectively. Ticketing system could use a few improvements to the ticket routing workflow that other, more-developed ticketing systems have, such as per-team ticket queues that tickets can be routed to without assigning the tickets to specific individuals.