Camunda
Closed beta

Re-engineer processes for an AI-native world

ProcessOS is the intelligence layer of the Camunda platform, using specialized AI agents to discover how work really runs, redesign processes around the outcomes you want, build and deploy them, and continuously improve what goes live.

ProcessOS is currently in closed beta. Request early access to share your use case and help Camunda determine fit and prioritize access.

All business processes are legacy

Most business processes were designed around human work, existing systems, and constraints that predate AI. Adding AI can accelerate individual steps, but the structure of the process stays the same.

ProcessOS starts somewhere different: with the outcome you want. It uses AI to understand the process you have today, re-engineer what it should become, and turn that design into something you can run and improve.

“
ProcessOS tackles the real reason AI adoption stalls: we can't build tomorrow's processes using only what we know today. Transformation starts with a bold vision of the future.

Lily Wang

Managing Director, Barclays

CamundaCon 2026 opening keynote — Jakob Freund and Daniel Meyer

CamundaCon · May 2026

Watch the keynote

See the first public introduction of ProcessOS and why becoming AI-native requires more than automating the processes you already have.

Turn process transformation into a continuous system

ProcessOS is the agentic operating system for your business processes and the intelligence layer of the Camunda platform. Four specialized AI agents work across the process lifecycle: discovering how work actually runs, re-engineering it around the outcomes you want, building and deploying the new process, and continuously improving it in production.

Start with the outcomes

Describe the process in natural language, then define the outcome and KPIs that matter. ProcessOS uses that brief as ground truth to reconstruct the as-is process, design the to-be process, and generate what is needed to run it.

Cycle time | Manual effort | Quality | Cost | Throughput | Compliance

ProcessOS working on a delivery-exception process: the as-is map and the to-be BPMN review

From kickoff to production in weeks, not quarters

Traditional process transformation can spend months on discovery, workshops, documentation, redesign, and build. ProcessOS applies AI across the lifecycle to compress that work while retaining what it learns for the next process.

  • Discovery: 1–2 weeks, not months
  • Re-engineering: 1 week
  • Build and deploy: 2–4 weeks, not quarters
  • Organizational memory captures decisions, systems, integration patterns, and edge cases.
  • The Catalog makes proven connectors and building blocks reusable across processes.
  • Each new process can move faster than the last because ProcessOS retains organizational context and reusable Catalog assets.
Timeline: discovery in 1–2 weeks, re-engineering in 1 week, build and deploy in 2–4 weeks, then production

Structural redesign changes the process itself, not just the speed of individual tasks.

  • Finnova

    70–80%

    faster customer onboarding

    Finnova redesigned an onboarding experience that took 15–30 minutes and depended on manual steps and scattered systems. The redesigned process reduced the same task to minutes.

    Read the case study

  • R-KOM

    Near-instant

    ticket response time

    R-KOM replaced a fully manual ticket-to-technician workflow with AI-agentic orchestration. Response time moved from an average of eight hours to near real-time.

    Read the case study

An intelligence layer across the Camunda platform

ProcessOS works across the process lifecycle while Camunda provides the orchestration foundation for running the resulting processes. Teams can direct ProcessOS agents, work through their own coding agents, or work manually in the Camunda Workspace, with each mode writing to the same Project Repository.

  • Platform architecture
    ProcessOS sits as the intelligence layer of the Camunda platform, connecting discovery, re-engineering, build and deploy, and continuous improvement to the processes running in Camunda.
  • Working with ProcessOS
    Architects and developers can work in three modes: direct the ProcessOS agents through the UI, reviewing outputs, approving designs, and redirecting agents as they work; use ProcessOS Agent Skills from a coding agent such as Claude Code; or work manually in Workspace with Web Modeler and the Catalog. All three write to the same Project Repository.
  • Plugin model
    ProcessOS can extend into the tools and process intelligence investments you already use. For example, process mining tools such as Celonis or MPMX can plug into discovery to enrich the operational picture rather than forcing teams to start over.
ProcessOS architecture: the intelligence layer on the Camunda Hub, orchestrating the engine, Operate, Tasklist, core systems and AI agents

FAQ

  • What is ProcessOS?
    ProcessOS is the intelligence layer of the Camunda platform. Four specialized agents help discover how processes run, redesign them around desired outcomes, build and deploy the new process, and continuously improve it in production. It is not a modeling tool or a monitoring dashboard; it is designed to make process transformation faster, repeatable, and continuously improvable.
  • What is the difference between adding AI to a process and re-engineering it?
    Adding AI can speed up individual steps in an existing process. Re-engineering starts from the outcome and redesigns the process around what AI, people, and systems should each do. The goal is structural change, not simply faster execution of the old workflow.
  • How is this different from process mining?
    Process mining shows how work is happening across operational systems. ProcessOS can use that intelligence, then go further by redesigning the process, building and deploying it, and continuously improving it. Existing process mining tools such as Celonis or MPMX can be used as plugins during discovery.
  • How do architects and developers work with ProcessOS?
    Teams can direct ProcessOS agents in the UI, use ProcessOS Agent Skills through a coding agent such as Claude Code, or work manually in Workspace with Web Modeler and the Catalog. Each mode writes to the same Project Repository.
  • What is a fitness function?
    A fitness function is a weighted scoring model built from the KPIs that matter to the process, such as cycle time, resolution rate, cost per case, and compliance rate. You set the weights based on what matters most in your domain. ProcessOS uses the function to evaluate process variants and proposed improvements against the outcome you defined.
  • How does continuous improvement work?
    ProcessOS monitors live performance against the fitness function. When it finds a potential improvement, it can backtest the change against historical process data—real cases, real edge cases, and real outcomes—and model the projected impact on the score before surfacing a proposal. A person reviews the evidence and approves the change. Proposed changes require human review and approval before they reach production.
  • What is organizational memory, and how does it compound?
    Organizational memory captures what ProcessOS learns about your environment, including systems, integration patterns, edge cases, and process decisions. It is stored in a private git repository and is not used to train shared models. Combined with reusable Catalog assets, every process makes the next one faster. Each new process can become faster to transform—not because the tool itself changed, but because ProcessOS retains more context about your business.
  • When is ProcessOS generally available?
    ProcessOS is currently in closed beta with limited capacity. Request early access to share your use case and help Camunda determine fit and prioritize access.

Ready to re-engineer your first process?

Closed-beta engagements are limited. Tell us about the process you want to transform. Your answers help the team understand whether ProcessOS is the right starting point for your organization.