Camunda orchestrates AI agents, people, and systems across end-to-end business processes. To make that work for everyone who touches those processes, we continue to invest in making our platform easier to learn, navigate, and use.
With Camunda 8.10, we're introducing a new design system that gives our products a shared foundation.
The result is a platform that's easier to navigate, without giving up room for the work itself. This helps people get started and makes it easier to onboard new users as Camunda adoption grows across your organization.
Available in both SaaS and Self-Managed.

Navigation that keeps your work in context
Business teams and developers work in the same interface. Modeling, operating, and monitoring share one navigation model, so the people who design a process can also see how it runs.
The sidebar changes with where you are, so it always shows what's relevant to your current work:
- Across your organization. Get to your workspaces, environments, and shared resources.
- Inside a workspace. See that workspace's projects, settings, and environments.
- Environments and their apps. Each environment lists its apps, like Operate and Tasklist, so you can open the one you need from there.
- Room to work. Collapse the sidebar when you need more space, like when you're modeling a process.
The breadcrumbs in the header show where you are:
- Your path at a glance. See your workspace, project, and file at the top of the page.
- Move up a level. Select any part of the path to go back to it, for example from a file to its project.
- Switch quickly. Change to another workspace or project right from the breadcrumb.

Accessibility from the start
Camunda is used by many people across your organization: developers modeling processes, operations teams keeping them running, and business users working through tasks every day. Some of them navigate with a keyboard, rely on a screen reader, or need strong contrast to read the screen. All of them should be able to do their work in Camunda without workarounds.
That's why accessibility is part of the design system and applied across Camunda:
- Keyboard access. Users can reach and use very interactive elements with the keyboard alone, with no keyboard traps.
- Visible focus. Every focusable element shows a clear focus indicator, so keyboard users always know where they are.
- Contrast. Text, controls, and focus indicators stand out clearly from their background, so they stay easy to see and read.
- Screen reader support. Buttons and controls have clear labels, so screen reader users know what each one does.
Accessibility is part of how we design and build new features, and we test it in the workflows people use every day.
Use the design system in your applications
Building on top of Camunda APIs? The design system is public — @camunda/design-system on npm, Apache 2.0, documented in Storybook. Tailor the experience to your users while keeping familiar Camunda styles and patterns.
It's under active development, so the public API can shift between minor releases. Check the docs before you lock in a version.
What comes next
Camunda 8.10 establishes this shared foundation. From here, we'll keep expanding the component library, refining interaction patterns, and strengthening accessibility across Camunda.
Explore the @camunda/design-system package, browse the Storybook, or visit the GitHub repository to follow the work and contribute.



