The agent does the legwork.Your team makes the call.
Miragon AI gives your AI agents tools for four of the five phases of your BPM lifecycle, on Camunda 7, CIB seven and Operaton. You sign off by review or pull request, and the knowledge stays in your team.
The lifecycle
Analyse once, then one loop
Analyse maps what you have. Design, Implement, Execute and Optimize form the loop, and what you learn in Optimize goes back into Design. Every phase and tool below is a link.
Who it is for
New tools for the Camunda 7 world
For teams with their own developers whose processes run on Camunda 7, CIB seven or Operaton. Miragon AI brings AI agents to exactly that stack: they map your process landscape, edit your models, make them deployable and tell you what is stuck. No new engine, no migration. Find your role and the tool to start with.
- ArchitectBefore a bigger change or an AI decision, you cannot say which processes you have and how they connectanalyzr brings your process models into one landscape and links them for your review.Start with analyzr
- Product ownerSign-off happens outside Git, and you review DMN changes as an XML diffIn designIQ every release is a pull request, and a DMN review shows a table of changed answers.Start with designIQ
- Automation leadThe backlog of processes to automate grows, and every project wires up the engine againThe Skills make your models deployable, and the Solution templates connect your own systems.Start with Skills
- Lead developerYour coding agent writes BPMN XML by handWith bpmn-cli your agent edits BPMN by command and keeps the layout, and the Skills add the engine details.Start with bpmn-cli
- Platform leadEvery engine has its own Cockpit, and runtime questions need PromQLPulse answers in the chat across your engines, and operate hands the engine state to your shell, agent and CI.Start with Pulse
- Head of ITYou have a mandate to bring in AI, but no agent may reach production uncheckedWithout OAuth, Pulse starts read-only. Whether an agent gets write access is your team's decision.Start with Pulse in read-only mode
What Miragon AI does
A tool for four of the five phases
Analyse runs once, at the start. Design, Implement, Execute and Optimize form the loop, and what you learn in Optimize goes back into Design.
- Phase 1 · onceAnalyseWhich processes do you have, and how do they connect? analyzr brings your models from engines, BPM suites and modelling tools into one landscape. A rule links unambiguous call activities, and agents propose further links and the place of each process in your value chain.Learn more
- Phase 2 · loopDesignAn AI agent that edits a model tends to rewrite the whole XML, coordinates included, and moves your hand-drawn layout. In designIQ your team edits models live in the browser while AI assistants work on the same models over MCP, and every release is a pull request. bpmn-cli changes BPMN by command and keeps the layout.Learn more
- Phase 3 · loopImplementA missing historyTimeToLive shows up only when the engine rejects the deployment. With the Skills for bpmn-cli and operate, your agent in Claude Code sets the engine details and tests on a dev engine. The Solution templates miragon-ai-starter and mcp-toolkit-starter start your own MCP server.Learn more
- Phase 4 · loopExecuteYour team pieces the state together from Cockpit tabs and stack traces, one engine at a time. Pulse shows the incidents across your engines in chat, grouped by failing activity and incident type, and drafts the ticket. operate runs the triage in one command, in your shell and in CI.Learn more
- Phase 5 · loopOptimizeWhen someone in operations notices that a model no longer fits, there is no set way back to the model. We have no tool for this phase yet, so your team carries the finding back itself.Learn more
- The way backBack into DesignYour team pins the finding as a todo on the BPMN element in designIQ, a GitHub issue in your repo. From there the loop starts again.Todos in designIQ
Human and AI
Who does what, phase by phase
The business flow of a process stays with people. In every phase the agent prepares the work and someone on your team decides.
- AnalyseThe agent proposes links with confidence and a rationaleYour team decides on each proposal, in review or by an auto-accept rule it sets.
- DesignThe agent turns described changes into valid BPMNYour team models the business flow and signs off by merge.
- ImplementThe agent sets engine attributes and tests on the dev engineYour team writes the worker code and reviews.
- ExecuteThe agent reads the state and drafts ticketsYour team decides whether the agent gets write access, and files the ticket.
- OptimizeThe agent has no tool here yetYour team decides what goes back into Design.
- Every phaseYour own permissions applydesignIQ follows the write permissions on your GitHub repo, where CODEOWNERS and branch protection decide who may merge. Without OAuth, Pulse stays read-only.
Why Miragon
Built by a process automation consultancy
Process automation since 2019
Miragon has been a consultancy for process automation since 2019 and is a Camunda partner. We introduce the tools together with your team until you run them on your own.
On your own infrastructure
You run Pulse yourself. Without OAuth it starts read-only, and it needs neither a migration nor access to the engine database.
Public under the MIT licence
designIQ, bpmn-cli, operate, Pulse and the miragon-ai-starter template are public on GitHub. For now we show analyzr as a read-only demo.
Tested against three engines
On every change, operate's CI runs its integration tests against Operaton 2.1.5, CIB seven 2.2.0 and Camunda 7.24.0.
Proof you can open
Open it before you talk to us
Versions as of 14 October 2026. Every link is public and needs no login.
- Version 5.3.0designIQThe repo Miragon/design-iq, with the self-hosted image.Open
- Version 0.7.0bpmn-cliThe repo Miragon/bpmn-cli, with the Skills plugin for it.Open
- Version 0.7.0operateThe repo Miragon/operate, with its plugin marketplace.Open
- Version 0.20.0PulsePulse is the MCP server from the repo Miragon/miragon-ai.Open
- Templatemiragon-ai-starterA GitHub template that starts your own MCP server.Open
- Read-only demoanalyzrThe early alpha on a synthetic process landscape. Its repo stays private.Open
- Every changeoperate's CIIntegration tests against Operaton 2.1.5, CIB seven 2.2.0 and Camunda 7.24.0.Open
- No loginPulse playgroundAdd it as an MCP server. Read-only, on a CIB seven engine with live demo traffic.Open
What we don't promise
Where the tools stop today
No process mining
analyzr reads the process models you already have and does not evaluate event logs.
No autonomous remediation
Agents carry out what your team approves.
No tool for Optimize
The analytics module of Pulse belongs to Execute, looks back 30 days at most and knows neither waiting times nor variants.
No generated worker code
The Skills make a model deployable, but no tool writes the worker or delegate code behind it. Your team does.
analyzr is early alpha
Version 0.1.0-alpha.0, in a private repository, with an interface in German only.
Pre-1.0 interfaces
bpmn-cli, operate and Pulse are pre-1.0 and still change their interfaces. The mcp-toolkit-starter template has no licence yet.
Hosted designIQ is pre-GA
The public launch of the hosted service is planned around mid-November 2026. The self-hosted image is released.
No savings numbers
No numbers on time or cost savings until we have published them.
Let's find your
biggest lever.
Pick a slot for a 30-minute first call. Tell us where your processes run and what slows your team down. You get an honest assessment of which tool helps first, or whether none does yet.
Loading calendar…