# Feature Maturity (/docs/console/more/feature-maturity)

Location: Console > More > Feature Maturity

Prisma releases updates to Console multiple times per week, as opposed to the Prisma ORM that we release on a set schedule every few weeks. This is why we consider the lifecycle and process for maturing features in Console differently.

You can [check out the releases and maturity process for the Prisma ORM](/orm/more/releases) for further details.

You can find information about releases across *all* Prisma tools and products in the [changelog](https://www.prisma.io/changelog).

Early Access [#early-access]

If a feature on the Console is labeled as **Early Access**:

* We have validated a problem and are considering a solution to it but are not certain whether that solution is complete or a perfect fit.
* We want to gather more feedback and adjust the solution as necessary, knowing that users are prepared for significant breaking changes.
* We reserve ourselves the right to throttle or remove access to a feature in Early Access to preserve the stability of the platform, or enforce its use to stay within the scope defined in our [Terms of Service](https://pris.ly/terms).

As always, your feedback in our [Discord](https://pris.ly/discord?utm_source=docs\&utm_medium=inline_text) is invaluable to shape the design of the features. This will help us ensure that they can solve your problems in the best way possible.

Preview [#preview]

If a feature on the Console is labeled as **Preview**:

* We have refined the software based on the valuable feedback we obtained during the Early Access phase.
* We developed the feature further, bringing it closer to the final version, though it's not completely ready for production usage.
* We have lifted the invite gate, so users no longer need an invitation to access the feature. Users just need to sign up to gain access.
* We have increased the stability of the software compared to the Early Access phase. While there might still be some issues, they should be less frequent and less critical.
* We use the Preview phase as a final stress test to ensure the product is ready for heavy production workloads.

We recommend testing the product in a staging environment and welcome any feedback in our [Discord](https://pris.ly/discord?utm_source=docs\&utm_medium=inline_text). This will assist us in improving the product for its final release.

Public Beta [#public-beta]

If a product or feature is labeled as **Public Beta**:

* It is open for anyone to try. No invite or waitlist is required.
* The core model is stable, and the documented happy paths work end to end. It is a good fit for evaluation, dogfooding, staging environments, internal tools, and low-risk apps.
* Behavior should stay stable unless the documentation or release notes call out an exception.
* Details can still change before general availability: exact limits, pricing, retention policies, runtime guardrails, supported frameworks and build behavior, some CLI and API details, Console UX, naming, and advanced workflows.
* We don't recommend it yet for mission-critical or heavy production workloads.

Public Beta is the final stress-test phase before general availability. Expect some rough edges, and tell us about them in [Discord](https://pris.ly/discord?utm_source=docs\&utm_medium=inline_text); your feedback directly shapes the release.

## Related pages

- [`Support`](https://www.prisma.io/docs/console/more/support): Find the right support for any Console question