Topic
This article explains each product stage, what type of access you have at each stage, and what you can expect from us at each point in the product lifecycle.
Environment
- NinjaOne Billing
- NinjaOne Backup
- NinjaOne Documentation
- NinjaOne Dojo
- NinjaOne Endpoint Management
- NinjaOne Integrations
- NinjaOne IT Asset Management (ITAM)
- NinjaOne Mobile Device Management (MDM)
- NinjaOne Network Management System (NMS)
- NinjaOne Patching
- NinjaOne Platform
- NinjaOne Remote
- NinjaOne Reporting
- NinjaOne Ticketing
Description
Every NinjaOne feature moves through a defined lifecycle — from early experimentation to general availability, and eventually to retirement. Understanding where a feature sits in that lifecycle helps you set the right expectations around stability, support, and access.
Feature lifecycle stages and access criteria are subject to change. For the most current information on a specific feature, refer to its dedicated Dojo article or contact your NinjaOne representative.
Index
Select a topic to learn more:
Product Lifecycle Overview
The typical lifecycle of a product goes through the following stages:
Alpha → Beta → Early Access (EA) → General Availability (GA) → End of Sale → Deprecation → End of Life (EOL)
Stage Definitions
Alpha
Products or features in the alpha stage are proof of concept or experimental updates that we may choose to share with a highly select group of partners. At this point of development, there is typically no polished user interface because the purpose is to demonstrate a capability and gather directional feedback, rather than to deliver a production-ready feature. Your participation at this stage helps us identify edge cases before the code is published to production, and your input shapes whether and how the feature progresses.
| Product Feature | Details |
|---|---|
| Access | Invitation only; we will reach out directly to you |
| Stability | Limited functionality and low compatibility |
| Readiness | Not recommended for production environments |
| Support | None; you will submit feedback directly through your NinjaOne contact or account manager |
| Expectations | Features will break, and significant changes will occur |
Beta
Products or features in the alpha stage introduce new functionality with unfinished compatibility and capabilities. We provide availability to a limited number of partners who meet specific eligibility criteria, and availability is subject to a partner cap. We actively test beta features against real-world use cases ahead of broader release and request feedback through designated channels. Your input directly influences the product roadmap.
We recommend performing backups and ensuring redundancy at this stage.
| Product Feature | Details |
|---|---|
| Access | Product manager approval required |
| Stability | Core functionality and medium compatibility |
| Readiness | Only deployed to production environments at partner discretion |
| Support | Limited; the Product Team prioritizes issues and determines if documentation is necessary |
| Expectations | Functionality may change between updates and there may be gaps in compatibility |
Early Access
Products or features in the early access stage are approaching completion and are available to a broader audience. Known bugs may still exist, but the experience should be close to what will ship at the general availability (GA) stage.
| Product Feature | Details |
|---|---|
| Access | Wider availability that may still require opt-in through account settings or your NinjaOne representative |
| Stability | Near-complete functionality and high compatibility |
| Readiness | Deployed to all production environments |
| Support | Limited resolution timelines |
| Expectations | Bugs may be present as we evaluate the feature for operational adoption |
General Availability (GA)
Products or features in the GA stage have stabilized functionality and are ready for full release. These features have passed NinjaOne's quality and compatibility standards and are fully covered by NinjaOne support.
| Product Feature | Details |
|---|---|
| Access | Available to all partners meeting standard licensing requirements |
| Stability | Stable; we will follow the standard communication process for breaking changes |
| Readiness | Deployed to all production environments |
| Support | Full NinjaOne support coverage |
| Expectations | This is the version you can rely on for day-to-day operations |
End of Sale
Products or features in the end-of-sale stage are no longer available for purchase for new or renewing partners. Existing customers who already have access may continue to use it.
| Product Feature | Details |
|---|---|
| Access | We maintain existing access, but we do not make this feature available for new or renewing customers |
| Stability | No new capabilities; maintenance updates may continue |
| Support | Full NinjaOne support coverage for partners with existing access |
| Expectations | We will begin evaluating alternative features or migration paths and communicate recommended alternatives where applicable |
Deprecation
A deprecated feature is still accessible but is no longer receiving new capabilities or non-emergency fixes. NinjaOne has signaled that this feature is approaching end of life, and partners should begin transitioning away from it.
Child statuses of deprecation may exist for specific sub-capabilities, such as extended agent support for legacy operating systems.
| Product Feature | Details |
|---|---|
| Access | We maintain existing access, but we do not make this feature available for new or renewing customers |
| Stability | No new capabilities; we may provide limited maintenance or fix only critical bugs |
| Support | Reduced; we may be unable to resolve complex issues |
| Readiness | We will plan migration paths and communicate recommendations |
| Expectations | Audit your environment for use of this feature and begin migration to the recommended alternative before the published end-of-life date |
End of Life
End of life (EOL) means the feature has been fully retired. It is no longer accessible, supported, or maintained.
If you have not yet migrated, contact your NinjaOne representative immediately for guidance.
| Product Feature | Details |
|---|---|
| Access | None |
| Stability | Not applicable |
| Support | None |
| Expectations | NinjaOne will provide advance notice and migration guidance ahead of any EOL date. If you are still relying on a feature approaching EOL, contact your NinjaOne representative as early as possible |
Frequently Asked Questions
How do I find out the current stage of a feature?
We will provide the feature lifecycle status in the relevant Dojo articles and in-product where applicable. If you're unsure, contact your NinjaOne representative.
How do I request access to a feature in the alpha or beta stage?
Alpha access is by invitation only; NinjaOne will contact you directly. For beta access, speak with your NinjaOne representative, who will assess your eligibility and submit a request for product manager approval.
Will I be notified before a feature reaches the end of life stage?
Yes. NinjaOne commits to providing advance notice ahead of any EOL date, along with guidance on recommended alternatives or migration paths. Note that lifecycle communications are sent through standard account and licensing channels.
If you are using a feature that is not reflected in your current licensing, you may not receive these notifications. To ensure you're included, confirm with your NinjaOne representative that your active features are accurately reflected in your account.
Can I give feedback on a feature in its early access or beta stage?
Absolutely, and we encourage it. Feedback during these stages has the most impact on the final product. Use the designated feedback channels provided when you're granted access, or reach out directly to your NinjaOne contact.
Additional Resources
Refer to Integration & Feature Availability by Instance for related documentation.