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 for further details.

You can find information about releases across all Prisma tools and products in the changelog.

Early Access

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

• It is ready to try out and represents the cutting edge of what we are building.
• It can still evolve based on feedback from our users, and its API surface won't change drastically as it matures.
• 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.

As always, your feedback in our Discord 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

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, and it is close to being 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. This will assist us in improving the product for its final release.

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; your feedback directly shapes the release.