Camunda Alpha Release for July 2025

We're excited to announce the July 2025 alpha release of Camunda. Check out what's new.
  • Blog
  • >
  • Camunda Alpha Release for July 2025

We’re excited to share that the latest alpha release of Camunda is now live and available for download. For our SaaS customers who are up to date, you may have already noticed some of these features as we make them available for you automatically.

Below is a summary of everything new in Camunda for July 2025 with the 8.8-alpha6 release.

This blog is organized using the following product house, with E2E Process Orchestration at the foundation and our product components represented by the building bricks. This organization allows us to organize the components to highlight how we believe Camunda builds the best infrastructure for your processes, with a strong foundation of orchestration and AI thoughtfully infused throughout.

Product-house

E2E Process Orchestration

This section will update you on the components that make up Camunda’s foundation, including the underlying engine, platform operations, security, and API.

Orchestration Cluster

User task listeners

With user listeners, you can respond to user task lifecycle events. In this alpha, we now support all user task listeners’ event types. This version adds support for listening to the creating and canceling events. Previous versions already added the assigning, updating, and completing events.

These changes allow users to react to specific user task lifecycle events.

  • Process designers can now model task listeners for different events.
  • 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.

Check out the documentation to learn more.

Identity

With Camunda 8.8, we have fundamentally improved how authentication and authorizations work across Self-Managed and SaaS environments.

In versions to version 8.7, all Self-Managed components were required to rely on an Identity system based on Keycloak and Postgres, resulting in installation complexity, duplicated configuration, and operational friction.

With the 8.8 release, Identity is split into two distinct scopes, each optimized for its purpose:

  • Orchestration Cluster Identity
  • Management Identity

Orchestration Cluster Identity

The new Orchestration Cluster Identity comes with built-in user and group management by default and does not require Keycloak or an external database. It is specifically designed for runtime components, including Zeebe, Operate, Tasklist, and the Orchestration Cluster API.

Key capabilities:

  • Simplified User, Group, and Role Management: Create and manage users, groups, and roles directly in a cluster.
  • OIDC Integration: Connect to external identity providers such as Microsoft EntraID or OIDC-compliant identity provider for Single Sign-On.
  • Resource-Based Authorizations: Define fine-grained access control at the resource level. Examples of the supported resources:
    • Authorizations
    • Process and decision definitions
    • Users and groups
    • Deployments
    • Claim mapping rules
    • Tenants
    • Clients
    • Resources
    • Etc.
  • Flexible Mapping for OIDC: Map OIDC token claims to roles, groups, and tenants to streamline user provisioning and permissions assignment.
  • Cluster-Specific Roles and Groups (SaaS): In SaaS, you can manage permissions for each cluster independently, enabling secure multi-cluster deployments.
  • Secure Storage: All entities are stored within the cluster’s primary and secondary storage, reducing external dependencies and improving resilience.
Orchestration-cluster-identity-authorizations
Authorizations in the Orchestration Cluster Identity

Management Identity

Management platform components, like Console, Web Modeler and Optimize, continue to use Keycloak by default and support external identity providers via OIDC, with role-based access across components.

Why this matters

The new architecture reduces operational overhead and installation friction by eliminating the need to rely on Keycloak and Postgres for Orchestration cluster components. It also introduces a clear separation between execution and platform access, allowing you to:

  • Scale and secure clusters independently.
  • Centrally or locally manage identity based on governance needs.
  • Simplify setup for both simple and enterprise deployments.

Try the new Identity on SaaS and Self-Managed

To try the new Identity on SaaS, create an alpha cluster on version 8.8.0-alpha6.

On Self-Managed, the new Identity is available for Camunda 8 Run, Docker Compose, and Helm chart installation. Check out this guide to get started.

With this alpha release, we’re moving toward a simpler, more unified, secure, and scalable identity experience in Camunda 8.

Known limitations in this alpha release

While the release introduces significant updates, there are some current limitations to be aware of that we plan to resolve until the minor 8.8.0 release:

Authentication & authorizations
  • Changes to application authorizations (if a user is allowed to access Identity, Operate, Tasklist), roles, or groups only take effect after the user logs out and logs back in. Changes in access level won’t apply until a new session is created.
  • Before enabling authorization checks in clusters, users must manually assign themselves to the admin role to not lose access.
Navigation, notifications, and logout
  • Navigation in the UI between components within an Orchestration cluster (Operate, Tasklist, and Identity) is not fully functional.
  • Logout functionality is not fully supported across Orchestration cluster components.
  • User profile information is not displayed in applications of an Orchestration cluster Identity.
  • SaaS notifications are not displayed in Orchestration cluster components.
Documentation
  • Documentation for the new Identity, its configuration, and features is being updated and we’re publishing it progressively.

Operate

This release includes the following bug fixes. The top three (3) are:

  • The v1 API now returns the proper response in the result field.
  • Process cancel operations in Operate are correctly transitioned to COMPLETED after the instance is fully cancelled (terminated) and the PI.ELEMENT_TERMNATED record is exported.
  • The ADD_VARIABLE / UPDATE_VARIABLE operation transitions to COMPLETED state once the variable is successfully added/updated.

We hope you enjoy everything in the latest Operate 8.8.0-alpha6 release.

Tasklist

For this release, our Tasklist engineering team worked on bug fixes.

We hope you enjoy everything in the latest Tasklist 8.8.0-alpha6 release.

Web Modeler

In this release, the following feature has been added for Web Modeler:

  • Bitbucket Git Sync
    Camunda now supports integration with Atlassian’s Bitbucket Cloud. his helps customers who heavily use it for their development processes.

We hope you enjoy everything in the latest Web Modeler 8.8-alpha6 release!

Desktop Modeler

For this release, our Desktop Modeler engineering team worked on bug fixes.

Optimize

Our Optimize engineering team worked on bug fixes for this release.

Installation Options

This section gives updates on our installation options and various supported software components.

Self-Managed

Backup and restore improvements

The Camunda backup guides for version 8.5 through 8.7 have been improved and are easier to use.

Helm Charts

There have been some changes made to Helm charts in this release:

  • Alternative container images, Camunda now provides alternative container images via registry.camunda.cloud. These images offer faster Common Vulnerabilities and Exposures (CVE) patching and better support compared to the previously used Bitnami open source images.
  • Configurable Volumes. You can now define PersistentVolumeClaims via values.yaml for improved flexibility. extraVolumeClaimTemplates allow attaching additional volumes to Zeebe/Core pods.
  • Unified Resource Labels. You can now use commonLabels to consistently label all Camunda resources, simplifying management and organization.
  • Web Modeler Scaling: You can set replicas for Web Modeler’s REST API and frontend independently via new config values.
  • External DB for Web Modeler: External Database configuration now mirrors Identity’s structure via webModeler.restapi.externalDatabase, with the legacy URL field still supported.

Task Automation Components

In this section, you can find information related to the components that allow you to build and automate your processes including our modelers and Connectors.

Connectors

This release the following have been updated:

  • A new intrinsic function for retrieving JSON data is available.
  • We have enabled deduplication for webhooks.

We hope you enjoy everything in the latest Connectors 8.8.0-alpha6 release right here.

Agentic Orchestration

In this section, you can find information related to the components that related to Camunda’s support for agentic orchestration.

AI Agent connector

The following features have been updated for our AI Agent Connector.

  • Structured outputs/JSON mode.  Our configurable response formats allow you to specify if the connector should return text or JSON responses for downstream processing of the agent output. Depending on the model used, this also allows you to define the JSON schema of the data returned by the agent.
  • Conversation history storage: The conversation history can now be stored in Camunda’s document storage instead of process variables. This allows a larger conversation history to be stored without being limited by process variable size limits.

To learn more about this connector, see AI Agent connector.

C7 Data Migrator

With our C7 Data Migrator 0.1.0-alpha3 release, the C7 to C8 Data Migrator brings a few quality of life improvements for our customers that are moving from Camunda 7 to Camunda 8:

  • Support for Oracle 19/23 and Postgres 17.
  • All BPMN flow nodes are covered by tests, and limitations are documented.
  • Improved error handling and migration resume capabilities.
  • Configuration is more streamlined and self-explanatory.
  • Variable migration
    • Register variable interceptors to change variable formats yourself.
    • Date variables are converted into a format that can be consumed by C8.

While the C7 Data Migrator is still in alpha, you can already check out the project and try it!

Visit https://github.com/camunda/c7-data-migrator.

Thank you

We hope you enjoy our latest minor release updates! For more details, be sure to review the latest release notes as well. If you have any feedback or thoughts, please feel free to contact us or let us know on our forum.

If you don’t have an account, you can try out the latest version today with a free trial.

Start the discussion at forum.camunda.io

Try All Features of Camunda

Related Content

Camunda 8.8 provides notable enhancements to our orchestration cluster and how it is deployed and operated. Read on to learn more.
Bitnami's shift in container image distribution leads Camunda to disable infrastructure sub-charts by default.
Build and deploy AI agents where they matter most and transform aspiration into an operational advantage.