Feature Maturity Levels

We use standardized maturity levels to help you understand the stability and availability of features as we develop them

Feature lifecycle

Experimental

Experimental features are where we explore new ideas and test out proof of concepts.

• We’re still building out core functionality, so things may be incomplete or unstable
• We might make breaking changes without much notice as we iterate
• We limit access to our internal team and design partners
• Our design partners help us figure out what the feature should do and how it should work
• We’re in full feedback-driven development mode

Beta

Beta features are usable, but they might change. We may redesign or rethink them based on what we learn.

• You can use these features, but don’t build workflows around them that you can’t undo
• Expect breaking changes — the API, behavior, or UX may change as we iterate
• We’re actively gathering feedback to shape the final design
• Documentation is available, but may evolve alongside the feature
• Our support team can help, though some rough edges are expected

Generally Available (GA)

GA features are stable. GA is a promise about stability — you can depend on these features in production.

• The API won’t break and the UX won’t fundamentally change
• We’re committed to backward compatibility
• Complete documentation and training materials are available
• Fully supported by our team

Using Feature Maturity Levels

These levels help you understand what to expect from each feature’s stability, so you can decide what works best for your production environment and risk tolerance.

When you’re evaluating features for your use case, we recommend considering the maturity level alongside your requirements for stability, support, and backward compatibility.