Portfolio fact
Names, scope, supported workflows, and product relationships come from current official pages and documentation.
This ledger records the official source, source type, verification date, and the reason it is used. Design advice and field interpretation are labeled as such rather than presented as product fact.
Validation method
Official does not automatically mean timeless. Product availability, OS support, Early Access status, integrations, packaging, and compliance can change, so the source date is part of the claim.
Names, scope, supported workflows, and product relationships come from current official pages and documentation.
Marketing outcomes would need a date and study context. This guide intentionally avoids using them as knowledge-check facts.
Discovery, architecture, demo, and POC advice is the field guide's interpretation and is labeled “From the SE chair.”
License-, OS-, release-, or integration-specific behavior is qualified and should be re-verified before a live customer commitment.
Conflicts resolved
These are deliberate editorial decisions, not omissions. Narrow, current language is safer than repeating a larger stale claim.
No commercial SKU count is published. The site separates products, bundles, add-ons, included apps, capabilities, use cases, and services.
NinjaOne's header, footer, demo catalog, lifecycle docs, and portfolio index overlap but are not identical.
No numeric catalog claim appears in the curriculum.
The current official patch page contains conflicting application counts. OS, release, license, and catalog scope are qualified instead.
Taught as release-status-dependent and Early Access in the latest July 24, 2026 documentation.
Broad marketing language is less specific than the current platform documentation.
The guide avoids claiming macOS or Linux image recovery. It uses workload-specific language and recommends current-doc validation.
Current setup and release material supersedes older FAQ language, while image modality still differs by OS.
The field guide teaches Microsoft 365 and Google Workspace as the core pair and treats current additional workloads as page- and license-specific.
Current product pages have advanced beyond an older official FAQ that described a narrower lineup.
The guide says 'current public catalog' and requires workflow-level validation.
The marketing directory and console documentation do not enumerate the exact same set of integrations.
Source register
Open the source before repeating a version-sensitive claim in a customer or design setting.
Canonical cross-check for the current product, MSP, integration, government, and resource taxonomy.
Supports the Manage / Protect / Support platform framing and the current homepage product story.
Supports the lightweight-agent operating model, device coverage, audience, roadmap, and integration basics.
Supports the learning sequence for roles, policies, monitors, RMM, software, patching, remote, backup, ticketing, documentation, and automation.
Product scope for endpoint visibility, policy, monitoring, automation, software deployment, and reporting.
Product scope for remote monitoring and management across IT teams and MSPs.
Distinguishes device-level remote tools from the separate NinjaOne Remote desktop-control product.
Product scope for OS and application patching, policy, automation, compliance, and Patch Intelligence AI.
Supports scan schedules, approvals, deployment, reboot behavior, application selection, and patch-state monitoring.
Supports real-time server-side CVE and KEV correlation, offline exposure awareness, prioritization, and patch mapping.
Product scope for attended and unattended remote support.
Supports native-console positioning, supported desktop and mobile platforms, session controls, and technician workflows.
Supports invitation-based ad-hoc remote access to an unmanaged device without a preinstalled NinjaOne management agent.
Product scope for Apple and Android enrollment, policy, configuration, security, application, and remote actions.
Supports managed, unmanaged, offline, and network-discovered inventory plus lifecycle, license, warranty, and relationship data.
Supports license allocation, consumption, renewal, expiration, assignment, and billing integration details.
Used as a product-adjacent ITAM capability rather than counted as a separate core platform pillar.
Umbrella source for device, server, and SaaS data protection in the NinjaOne platform.
Supports endpoint and server backup, policy-based protection, and recovery workflows.
Supports Microsoft 365 and Google Workspace backup, retention, search, and granular restore.
Supports searchable email retention and compliance-oriented archive workflows.
Supports security-policy and third-party endpoint-security integration positioning inside endpoint operations.
Product scope for context-rich service requests, workflow, automation, and technician queues.
Product scope for templates, checklists, knowledge, access control, and documentation linked to operations.
Supports the MSP service-operations bundle across ticketing, documentation, ITAM, time, and business workflow.
Supports MSP billing workflows tied to services, products, time, and managed quantities.
Official current integration catalog. Treat connector availability as time-sensitive and re-check before a live claim.
Supports agentless discovery and monitoring of network devices using SNMP/ICMP plus flow and device telemetry where configured.
Supports summary, data-table, runbook, scheduled, and export/reporting workflows subject to permissions and product data.
Windows-focused image capture and deployment capability within Endpoint Management, not presented here as an independent top-level SKU.
Supports custom operational data used by forms, groups, conditions, reports, scripts, and API workflows.
Supports OAuth-based API access and the need to validate grant support for the specific API area.
A cross-product solution story spanning proactive monitoring, automation, self-service, user-centric insight, and remote support; not counted here as an independent SKU.
A cross-product capability for permitted end-user actions, not represented as a standalone commercial product.
Confirms Patch Intelligence AI is a Windows OS patch decision-support capability and not a separate NinjaOne AI product.
Distinguishes vendor-delivered scoped professional services from the MSP PSA product.
Cross-check for current demo tracks including endpoint management, patching, MDM, remote, SaaS backup, ITAM, billing, ticketing, documentation, warranty, and custom fields.
Supports native ITAM and the PSA bundle relationship without relying on third-party summaries.
Authoritative for ninjarmm-cli binary paths per OS, command grammar, the full custom-field type table with exact value ranges and character caps, exit codes, and the PowerShell 1/2 and empty-template constraints.
Authoritative for the three OAuth scopes (Monitoring, Management, Control), supported grant types, and the system-administrator-only configuration constraint. Does not publish rate limits or regional base URLs.
Confirms Auto/Manual/Reject approval states and the >=1 hour scan-to-install interval. Deliberately does NOT prescribe ring sizes, soak durations, or escalation criteria - which is why this site labels its ring model as field interpretation.
Used for the US-West hostname estate, the 72 connect shards, the eight NinjaOne Remote endpoints, and the four regional backup buckets.
Authoritative catalogue of every condition type: 28 agent conditions (including Patch CVSS Score, Script Result, BitLocker Status, FileVault Status, Custom Fields, RAID Health, Windows Event), 7 VM host, 6 VM guest, and 14 NMS conditions. Confirms threshold-plus-duration semantics and reset behavior.
Authoritative for the four policy types (Agent, NMS, VM, MDM), Parent Policy inheritance, the Organization -> Location -> Device assignment precedence, and the hard constraint that a device cannot be assigned to multiple policies at the same time.
Authoritative for MDM minimum OS versions (iOS 10.0+, iPadOS all versions, Android 8.0 Oreo+), the NinjaOne Remote and Quick Connect mobile floors (iOS 16.0+, Android 8.0+), and the Declarative Device Management floors (iOS/iPadOS 17.0, macOS 14.0) with documented fallback to standard MDM behavior below them.
Supports the enrollment model claims: automated enrollment via Apple Business Manager, Apple School Manager, and Android Enterprise, plus QR code enrollment across Android and Apple iOS/iPadOS.
Hub page. Points to per-platform agent prerequisites and the global allowlist article rather than carrying specifications inline.