Feature Maturity Lifecycle

Prev Next

Rocket.Chat uses certain stages to describe the maturity of each feature. These stages help you understand:

  • When a feature is ready for production use

  • Whether you should consider early adoption

  • What level of stability and support to expect

Rocket.Chat features move through four maturity stages.

Not every feature moves through Alpha, Beta, and GA in order. Some may skip stages if they already meet the criteria for a later one. For example, a fully validated feature might launch directly as GA.

1. Alpha

The Alpha stage is the earliest externally testable version of a feature. It is intended for early adopters who want to explore new functionality and provide structured feedback.

What to expect:

  • Core functionality is available, but refinement is ongoing

  • Stability and performance can vary

  • Edge cases are still being discovered

  • Not suitable for critical or production workloads

2. Beta

The Beta stage represents a more complete and stable version. It is suitable for broader testing and helps validate usability, performance, and overall readiness for production.

What to expect:

  • Stable enough for general use, though improvements are still in progress

  • Most documentation and onboarding materials are available

  • Not recommended for mission-critical environments

  • Feedback remains an active part of the process

3. General availability (GA)

GA features are mature, fully tested, and supported as part of the standard Rocket.Chat offering.

What to expect:

  • Meets reliability, scalability, and security standards

  • Fully documented with established support processes

  • Available to all customers under standard licensing

  • Actively maintained and monitored

4. Deprecated/Sunset  

Features in this stage are being phased out or replaced. They no longer receive enhancements, and users should plan to transition to supported alternatives. Adequate notice is provided to allow for a smooth migration.

What to expect:

  • The feature remains available for a defined transition period

  • Clear communication about retirement timelines and alternatives

  • Migration guidance shared through release notes and product updates

High-level support expectation

Stage

Support Level

Production Use

Documentation Availability

Tag in UI

Alpha

Best effort

Not recommended

Basic guidance

Beta

Best effort

Not recommended

Mostly available

GA

Standard SLA coverage

Fully supported

Fully documented

None

Deprecated

Supported until EOL

Not recommended

Migration guidance

What Users Can Expect

  • Clear labeling of Alpha, Beta, GA, and Deprecated features

  • Documentation that matches each readiness level

  • Advance notice of major transitions or deprecations

  • Readiness stages reflected in release notes and product announcements

  • Opportunities to provide feedback during Alpha and Beta phases

These stages create a consistent framework for understanding feature maturity across Rocket.Chat. They help you make confident decisions about testing, adopting, and deploying features within your organization.