Release notes

These release notes identify the new features included in 8.8, including alpha feature releases.

8.8 minor

Scheduled release date	Scheduled end of maintenance	Changelog(s)	Release blog	Update guide
14 October 2025	13 April 2027	-	-	-

8.8.0-alpha2

Release date	Changelog(s)	Blog
11 March 2025	Camunda 8 core Connectors	Release blog

Camunda Spring Boot SDK for the C8 REST API

A Spring Boot SDK is provided for the Camunda 8 REST API to unify process management, user tasks, and identity features under a single dedicated starter. This simplifies the interaction between a Spring Boot application and Camunda 8, allowing you to:

• Easily integrate process entity management and queries within your workflows.
• Seamlessly configure endpoints and authentication via Spring Boot auto-configuration, minimizing boilerplate code.
• Rely on an official, standardized approach to guarantee consistency and reduce maintenance costs when upgrading.

To learn more about this feature, see the Camunda Spring Boot SDK.

Camunda 8 Run authentication updates

Camunda 8 Run no longer requires authentication when working with APIs. Authentication and authorizations can be optionally enabled to allow requests using basic authentication, and to test authorizations and permissions.

To learn more about this feature, see the API documentation for Camunda 8 Run.

Identity management updates SaaSSelf-Managed

The Identity service is enhanced to deliver greater flexibility, control, and security for both Self-Managed and SaaS users. These updates are part of our broader effort to streamline the platform’s architecture.

Cluster-level identity management

Identity settings will be configured at the orchestration cluster level, allowing each cluster to have unique OIDC configurations. This cluster-specific setup empowers organizations to assign different identity providers (IdPs) across clusters, offering improved control over permissions and user group mappings, resulting in a more streamlined and efficient configuration experience.

For SaaS customers, identity management in Camunda 8.8 remains consistent with Camunda 8.7, allowing the attachment of a single IdP per organization. However, cluster-level identity capabilities are provided for SaaS as well as Self-Managed. This means that user groups, roles, and access permissions can now be managed at the cluster level, giving SaaS customers the same granular access control as in Self-Managed environments.

Decoupling from Keycloak Self-Managed

Built-in Keycloak integration in Self-Managed is removed, allowing customers to use any compatible IdP.

• Keycloak remains fully supported as an external option. For cluster-level identity management it must be connected as an external OIDC provider moving forward.
• OpenID Connect (OIDC) remains the standard for seamless integration with chosen IdPs.

Resource-based permissions

Resource-level permissions are introduced to control read and write permissions per specific resource.

• Admin users retain full access, but regular users must be granted specific permissions to perform operations or view resources.
• For organizations that build custom front-ends and access Camunda via API, users or Clients with API permissions can still access data through the V2 API, respecting their resource permissions.

8.8.0-alpha1

Release date	Changelog(s)	Blog
11 February 2025	Camunda 8 core Connectors	Release blog

note

Some features available in 8.8.0-alpha1 were originally released in 8.7.0 alphas. These features are longer planned for release in 8.7.0. For more information, see the Camunda 8.7 and 8.8 release update blog.

User task listeners SaaSSelf-ManagedModelerOperate

Task lifecycle management is enhanced with user task listeners, allowing users to react to specific user task lifecycle events.

• Process designers can now model task listeners for different events, such as assigning and completing.
• Developers can use the same job infrastructure to activate and complete task listener jobs.
• Operations engineers can easily check details of active and completed task listeners within instances, and efficiently resolve task listener incidents.

This enhancement streamlines operations and ensures smoother incident handling, improving time to unblock process execution.

To learn more about this feature, see user task listeners.

Camunda 8 REST API Query API API

You can now use a single Query API in the Camunda 8 REST API to find process and decision data instead of using multiple component APIs.

For example, send a request to the Query decision definitions endpoint to search for decision definitions.

New Query API endpoints are added as follows:

• Decision definitions
• Decision instances
• Decision requirements
• Flownode instances
• Incidents
• Process definitions
• Process instances
• User tasks
• Variables

To learn more about these endpoints, see the Camunda 8 REST API documentation.

Amazon OpenSearch Optimize support Self-ManagedOptimize

Camunda 8 Self-Managed now fully supports the use of Amazon OpenSearch with Optimize.

Process instance migration SaaSSelf-ManagedZeebe

Enhanced process instance migration allows you to solve problems with process definitions and use the latest process improvements.

You can now migrate the following:

• Compensation boundary event subscriptions
• Escalation boundary events
• Escalation event subprocesses

To learn more about migration, see process instance migration.

Camunda Exporter Self-Managed

A new Camunda Exporter brings the importer and archiving logic of web components (Tasklist and Operate) closer to the distributed platform (Zeebe). The index schema is also being harmonized.

To learn more about this feature, see the Camunda Exporter documentation.

Backup and restore improvements Self-Managed

Camunda backups have been improved and made easier to use. The web application backups are now merged together under one endpoint.

Connector Runtime SaaSSelf-ManagedConnectors

Spring SDK and Camunda REST API Migration

The Connectors experience is enhanced with the migration from the Spring Zeebe to the Camunda REST API, and the removal of dependency on the Operate client.