Skip to main content

ZITADEL Support States and Software Release Cycle

Support states

It's important to note that support may differ depending on the feature, and not all features may be fully supported. We always strive to provide the best support possible for our customers and community, but we may not be able to provide immediate or comprehensive support for all features. Also the support may differ depending on your contracts. Read more about it on our Legal page


Supported features are those that are guaranteed to work as intended and are fully tested by our team. If you encounter any issues with a supported feature, please contact us by creating a bug report. We will review the issues according to our product management process.

In case you are eligible to support services get in touch via one of our support channels and we will provide prompt response to the issues you may experience and make our best effort to assist you to find a resolution.

Security Issues

Please report any security issues immediately to the indicated address in our security.txt

Enterprise supported

Enterprise supported features are those where we provide support only to users eligible for enterprise support services. These features should be functional for eligible users, but may have some limitations for a broader use.

If you encounter issues with an enterprise supported feature and you are eligible for enterprise support services, we will provide a prompt response to the issues you may experience and make our best effort to assist you to find a resolution.

Enterprise supported features

Community supported

Community supported features are those that have been developed by our community and may not have undergone extensive testing or support from our team. If you encounter issues with a community supported feature, we encourage you to seek help from our community or other online resources, where other users can provide assistance:

Software release cycle

It's important to note that both Alpha and Beta software can have breaking changes, meaning they are not backward-compatible with previous versions of the software. Therefore, it's recommended to use caution when using Alpha and Beta software, and to always back up important data before installing or testing new software versions.

Only features in General Availability will be covered by support services.

We encourage our community to check out Preview and test Alpha and Beta software and provide feedback via our Discord Chat.


The Preview state is our initial stage to document planned futures and collect early feedback on the design. Features are not yet implemented at all or availability is limited to designated testers. We recommend that users exercise caution when using Preview software and avoid using it for critical tasks, as support is limited during this phase.


The Alpha state is our initial testing phase. It is available to everyone, but it is not yet complete and may contain bugs and incomplete features. We recommend that users exercise caution when using Alpha software and avoid using it for critical tasks, as support is limited during this phase.


The Beta state comes after the Alpha phase and is a more stable version of the software. It is feature-complete, but may still contain bugs that need to be fixed before general availability. While it is available to everyone, we recommend that users exercise caution when using Beta software and avoid using it for critical tasks. During this phase, support is limited as we focus on testing and bug fixing.

General available

Generally available features are available to everyone and have the appropriate test coverage to be used for critical tasks. The software will be backwards-compatible with previous versions, for exceptions we will publish a technical advisory. Features in General Availability are not marked explicitly.

Release types

All release channels receive regular updates and bug fixes. However, the timing and frequency of updates may differ between the channels. The choice between the "release candidate", "latest" and "stable" release channels depends on the specific requirements, preferences, and risk tolerance of the users.

List of all releases

Release candidate

A release candidate refers to a pre-release version that is distributed to a limited group of users or customers for testing and evaluation purposes before a wider release. It allows a selected group, such as our open source community or early adopters, to provide valuable feedback, identify potential issues, and help refine the software. Please note that since it is not the final version, the release candidate may still contain some bugs or issues that are addressed before the official release.

Release candidates are accessible for our open source community, but will not be deployed to the ZITADEL Cloud Platform.


The "latest" release channel is designed for users who prefer to access the most recent updates, features, and enhancements as soon as they become available. It provides early access to new functionalities and improvements but may involve a higher degree of risk as it is the most actively developed version. Users opting for the latest release channel should be aware that occasional bugs or issues may arise due to the ongoing development process.


The "stable" release channel is intended for users seeking a more reliable and production-ready version of the software. It offers a well-tested and validated release with fewer known issues and a higher level of stability. The stable release channel undergoes rigorous quality assurance and testing processes to ensure that it meets the highest standards of reliability and performance. It is recommended for users who prioritize stability over immediate access to the latest features.

Current Stable Version:



ZITADEL Cloud follows a regular deployment cycle to ensure our product remains up-to-date, secure, and provides new features. Our standard deployment cycle occurs every two weeks, during which we implement updates, bug fixes, and enhancements to improve the functionality and performance of our product. In certain circumstances, we may require additional deployments beyond the regular two-week cycle. This can occur for example when we have substantial updates or feature releases that require additional time for thorough testing and implementation or security fixes. During deployments, we strive to minimize any disruptions and do not expect any downtime.

Release deployment with risk of downtime

In rare situations where deploying releases that may carry a risk of increased latency or short downtime, we have a well-defined procedure in place to ensure transparent communication. Prior to such deployments, we publish information on our status page, which can be accessed by visiting We also recommend that you subscribe to those updates on the status page.

We make it a priority to inform you of any potential impact well in advance. In adherence to our commitment to transparency, we provide a minimum notice period of five working days before deploying a release that poses a risk of downtime. This gives you time to plan accordingly, make any necessary adjustments, or reach out to our support team for assistance.

Our team works diligently to minimize the risk of downtime during these releases. We thoroughly test and verify each update before deployment to ensure the highest level of stability and reliability.