Alpha features

You can use alpha features to learn about upcoming changes, try them out, and share feedback.

info

To understand the difference between an alpha feature and an alpha release, see alpha features and releases.

Alpha

Selected Camunda features and components are released as alpha versions. We release these in an early state for you to test and participate in development by sharing your feedback before they reach general availability (GA).

Limitations of alpha features and components include:

• Not for production use.
• APIs, dependencies, and configuration are likely to change.
• Not necessarily feature-complete.
• Might lack full documentation.
• No guaranteed updates to newer releases.
• Support based on SLAs agreed with you, but bugs are treated with the same priority as feature or help requests. See Camunda Enterprise Support Guide.
• No maintenance service.
• (SaaS) No availability targets.
• Released outside the standard release policy.

To learn more about using alpha features, see enabling alpha features.

note

• Alpha features can also be included in a minor version (stable) release.
• Although there is no maintenance service, customers can still provide feedback through designated support channels, depending on their SLAs. These channels include filing issues in the respective GitHub repositories and submitting questions and suggestions by contacting us.

General availability (GA)

Once features and components are released and considered stable, they become generally available.

Stable features and components are:

• Ready for production use for most users with minimal risk.
• Supported by L1 Priority-level support for production use.
• Fully documented.

A release or component is considered stable if it has passed all verification and test stages and can be released to production.

note

Alpha releases can also have limited availability, such as features that are only available to enterprise customers.