Fluxnova runs the process. Summit58 makes it something a person still designed.
The FINOS-backed engine underneath it is Fluxnova, for new BPM workflows and for existing ones moving off Camunda 7. Summit58 designs and engineers the process, including where an agent step belongs and where it does not. Reign Ops operates Fluxnova underneath it, inside your own trust boundary. Reign Assurance is being designed to evidence what actually happened.
A consulting firm that designs the process itself.
Summit58 is a technology consulting firm specializing in strategic business process automation, workflow orchestration, AI-enabled solutions and custom software development. Its work includes process and decision analysis and modeling and agentic process design.
Summit58 advises across several workflow platforms, preserving customer choice as an organization’s needs evolve. Where an organization chooses Fluxnova, this partnership is how it gets designed, operated and evidenced. For Fluxnova, Summit58 supports evaluation, adoption, migration and day-to-day operation, including support, backed by nearly two decades of direct experience with the Fluxnova codebase and open-source workflow technologies.
Summit58 is based in Scottsdale, Arizona.
3.0 expanded the possibilities, and the governance challenge.
Fluxnova 3.0 shipped MCP Start Event integration and agentic subprocesses as optional plugins. Agents can invoke processes and determine their own steps at runtime from prompts and business context. These capabilities are generally available today, not roadmap.
The engine’s governance is part of the product.
Fluxnova is an open source project backed by FINOS and the Linux Foundation. Its roadmap and its license sit outside the control of any single vendor, including iTmethods. For a regulated organization deciding where to put a decade of process logic, that governance is part of the product. The engine runs on the infrastructure the organization already has, inside its own trust boundary, rather than requiring the work to move to somebody else’s estate.
Three layers. Clear ownership. No overlap.
Process design, engineering and what the agents do inside it
Process analysis and BPMN modeling, decision logic and DMN, agentic process and subprocess design, systems and data integration, custom software development, legacy modernization, Camunda 7 and Fluxnova migration, engine engineering and bug fixes, performance work, process and KPI monitoring, training and operational handoff.
The platform
Environment build and deployment, hosting inside the customer’s trust boundary, security and identity, availability, backup and recovery, upgrade and patch execution, platform monitoring and service management.
The evidence
Checks that run against work as it moves rather than being assembled afterwards, with three outcomes: passed, did not pass, and needs a person.
Customers raise issues through a single route. The two firms have agreed that principle and are documenting the triage, handoffs and service commitments behind it.
Fluxnova is the target. Camunda 7 is one way in.
Fluxnova is where new BPM workflows get built and where existing ones are headed. Organizations with no Camunda estate start there directly. Organizations with a decade of process logic on Camunda 7 get there by migration, and that path is well defined because Fluxnova maintains backward compatibility with Camunda 7 BPMN 2.0 and DMN models and ships migration tooling for code, dependencies and configuration.
Camunda 7.24 LTS, released in October 2025, is the final public release, and Camunda states that there will be no further public releases. Enterprise Edition continues to receive maintenance releases: Camunda’s published schedule gives end of maintenance as 13 April 2030, followed by extended support to April 2032.
Fluxnova maintains backward compatibility with Camunda 7 BPMN 2.0 and DMN models, and provides migration tooling for code, dependencies and configuration. Summit58 scopes the application, data and integration work each implementation requires, then supports the move and the processes that continue to evolve afterwards.
Where each Reign motion actually stands.
Four motions at four different stages. This page describes each one no more confidently than the register does.
| Motion | Status | What this means in practice | What it does not mean |
|---|---|---|---|
| Reign Ops · Operate | Available today | Twenty-one years operating delivery tooling for regulated enterprises, with named people and an agreed change process. Managed Fluxnova runs here. | It does not mean the other three motions are available because this one is. |
| Reign Gateway · Govern | Available today | The governed path is in production. Model access, policy and the record of what was requested and returned run through it rather than around it. | Being in production is a statement about the component running, not a claim that governance is solved or that every route in an enterprise passes through it on day one. |
| Reign Factory · Build | Available · Beta Release | It is running, on real work, in beta, and is being turned into a product while it runs. | It is not generally available. Beta access is agreed with us and scoped in writing before anything runs. |
| Reign Assurance · Assure | Co-design development | It is being designed with a small number of organizations, on scope agreed per engagement and written down before anything starts, with the effort and the commercial relationship following from it. | It is not available, not sold, and not shipping. iTmethods does not issue an audit opinion or certification. Reign prepares; people decide. |
No target dates are published for movement between these stages.
Agent-enabled processes.
The processes that matter to a regulated organization are the ones where an agent now decides part of the path. A process that can determine its own steps at runtime is more useful than one that cannot, and harder to answer for afterwards. Both of those are true at once, and the second is the reason the three layers are separated the way they are.
Summit58 designs where an agent step belongs and where it does not. Reign Ops runs the platform the process executes on, inside the customer’s trust boundary. Reign Assurance is being designed so that what the agent did can be shown to somebody who was not in the room, without asking them to take the engine’s word for it.
— Ryan Johnston, Founder and Managing Principal, Summit58
Bring one process. New, or running on Camunda 7 today.
In a working session we will discuss the process, what it has to hold, and a practical Fluxnova operating path. If it runs on Camunda 7 today we will cover the migration; if it does not yet exist, we will cover how it gets built.
Scope, description and every factual statement about Summit58 on this page are approved by Summit58. Sources for lifecycle and project statements: Camunda support announcements, FINOS Fluxnova FAQs and the FINOS Fluxnova launch announcement.