Skip to main content
    Meet us at Open Source in Finance Forum (OSFF) New York, Convene Brookfield Place, November 4 to 5.Book a meeting
    Book a briefing
    Reign OpsManaged Fluxnova

    Managed Fluxnova, operated by Reign Ops.

    Fluxnova is an open-source fork of Camunda 7, hosted by FINOS under Apache 2.0. iTmethods packages, deploys and operates the platform as a dedicated service, and can plan and carry out a move from Camunda 7 or an earlier Fluxnova release.

    Available today Discuss your Camunda or Fluxnova estate See the benchmark →
    The process stays yours; Reign Ops operates the platform The process Your BPMN and DMN models, decision tables and integrations Summit58 leads the process, application and engine work You and Summit58 The platform Deployment, availability, backup and recovery, patching, monitoring Reign Ops The engine is Apache 2.0 and hosted by FINOS.
    The process stays yours; Reign Ops operates the platform
    The processYou and Summit58Your BPMN and DMN models, decision tables and integrations. Summit58 leads the process, application and engine work
    The platformReign OpsDeployment, availability, backup and recovery, patching, monitoring

    The engine is Apache 2.0 and hosted by FINOS.

    Reign Ops operates the platform; Summit58 covers the process, application and engine work.
    SOC 2 Type II on Reign Ops Apache 2.0 FINOS open source project

    Delivered as a single-tenant dedicated instance, in infrastructure iTmethods operates or in your own cloud account on AWS or Azure. Both are available today; Google Cloud is planned for 2027. Air-gapped and sovereign deployment are supported.

    Your options for Camunda 7 and Fluxnova

    Start from what you run today.

    01If you run Camunda 7
    Assess the current engine, applications, process definitions, dependencies and operating requirements; then plan the compatible path to Fluxnova and the environment that will run it.

    The benchmark results →

    02If you already run Fluxnova
    Plan the required upgrade, including framework and library changes, application-server changes, testing, rollback and operational handoff.

    Version 3.0 (July 2026) upgraded Spring Boot to 4 and fourteen other libraries, and Control Center replaced Cockpit. Version 3.1.1, released on 23 October 2026, removed JBoss and WildFly support (release notes). If you run either app server, this is a forced move rather than a planned one.

    03If you run Camunda 8, or are staying on Camunda
    Reign Ops operates Camunda 8 as a single-tenant dedicated instance under your Camunda license, and keeps Camunda 7 supported while you plan.

    Compare the paths on process compatibility, migration effort, data, integrations and operating model. Your requirements decide the recommendation, including a recommendation to stay where you are.

    04What iTmethods adds to the open project
    The community maintains the project.

    iTmethods provides the operating service around it: release engineering, deployment, patching, upgrades, monitoring, incident response and a named escalation path for the agreed scope.

    Migration

    Move the engine. Keep the processes.

    Camunda 7 to Fluxnova, or Fluxnova 2.x to the current 3.x release. iTmethods takes the platform and infrastructure work, Summit58 takes the process, application and engine work, and the boundary is named before work starts. Fluxnova is built to run Camunda 7 BPMN and DMN models; the assessment confirms yours.

    WhoWhat they own
    iTmethods · infrastructureEngine deployment and topology. Database migration and schema. Environment build across dev, test, production and DR. Identity, secrets and CI/CD integration. Cutover planning and rollback.
    Summit58 · process, application and engineBPMN and DMN process definitions. Business logic and rules. Forms and task interfaces. Process semantics and behavior. Engine fixes and performance work. Business validation and UAT. Training your process modelers.
    BothMigrating running process instances sits across both halves. Its owner is named before work starts rather than left to a general rule.

    Rollback is planned before cutover, not after. Camunda 7 to Fluxnova runs on a timeline you set. Summit58 and Reign Ops together →

    Benchmarks

    An invoice process, run on three engines in one Amazon EKS environment.

    One invoice process at 300 and 1,000 workflows on Camunda 7, Fluxnova and Camunda 8, with zero failures on every engine. At 1,000 workflows Camunda 7 finished in 16.7 seconds and Fluxnova in 21.3; at 300, Fluxnova was ahead, 6.0 seconds against 6.7. On this process we read that as the same performance class.

    <25sFluxnova and Camunda 7, 1,000 workflows, zero failures
    15×Longer for Camunda 8 than Fluxnova at 1,000 workflows
    0Changes to the invoice model between Camunda 7 and Fluxnova

    Fluxnova 2.0.x, Camunda 7.24.0 and Camunda 8.8.0 on Amazon EKS, June 2026, before Fluxnova 3.0 and not re-run on 3.x. One invoice process, on our infrastructure. The published method and results → · Run it on your own volumes →

    Agents and the engine

    Fluxnova 3.0 lets an agent choose its own steps at runtime.

    Version 3.0 added MCP integration and agentic adhoc subprocesses as plugins. Each subprocess starts from a prompt and the business context, builds its task sequence during execution, and leaves the steps it ran in the engine record.

    Policy and records for each model call
    With Reign Gateway in the deployment, model calls pass through it and the customer’s policy is applied to each call. Calls outside that policy are refused, with the reason recorded. Each record connects the call to the Fluxnova process instance and carries the identity, policy, decision, model and time. The quality of the agent’s judgment depends on its design, testing and review. Reign Gateway is available today.How the boundary works → · What shipped in 3.0 →
    “Fluxnova provides a strong, proven foundation for orchestrating agentic processes and defining the guardrails that keep each agent within its intended boundaries.”
    Ryan Johnston, Founder and Managing Principal, Summit58

    Fluxnova Con, Wednesday 4 November. It runs inside Open Source in Finance Forum New York, day 1, at Convene Brookfield Place. Ryan Johnston of Summit58 and Rob Stevens of iTmethods present “Fluxnova: Enterprise Performance & Camunda 7 Compatibility” on the event schedule. See the week →

    Deployment

    Two shapes are available, and both are single-tenant.

    Runs on the stack you already have. The instance is provisioned for one customer and serves that customer only, wherever it runs.

    Deployment modelAvailabilityWhat it is
    Dedicated instance Available today A single-tenant instance in infrastructure iTmethods operates, connected securely to your estate. The faster start and the lower entry point.
    Customer cloud Available today The same single-tenant instance deployed and operated inside your own cloud account on AWS or Azure. The account is yours and the billing relationship with the provider is yours. Google Cloud is planned for 2027.

    Air-gapped and sovereign deployment are supported. There is no multi-tenant or shared option. Deployment models in full →

    FAQ

    What is Fluxnova?
    An open-source fork of Camunda 7, hosted by FINOS under Apache 2.0. It was launched in October 2025 by a group of global banks and asset managers, runs BPMN and DMN, and FINOS is part of the Linux Foundation.
    Is it actually maintained?
    Yes, actively. Version 3.0 shipped in July 2026 with a Spring Boot 4 upgrade, fourteen other library upgrades, a new Control Center UI and a plugin ecosystem. Version 3.1.1 followed on 23 October 2026. The gap for a regulated institution is not maintenance. It is operation.
    Are my Camunda 7 processes compatible?
    Fluxnova maintains backward compatibility with Camunda 7 BPMN 2.0 and DMN models. Our benchmark’s invoice process moved with zero changes, and the assessment checks yours before anything moves.
    What changed in 3.0?
    Spring Boot 4 and fourteen other library upgrades, a Control Center UI covering process definitions, heat maps, instance migration and incident retry, adhoc subprocesses, restricted variables for personal data, and a plugin ecosystem, through which MCP integration and agentic adhoc subprocesses are added. The full breakdown →
    We are staying on Camunda for now. Is that a conversation?
    Yes, and it is a common one. Reign Ops operates and supports Camunda 7 and Camunda 8 as well, and will move you to Fluxnova whenever you decide rather than on a vendor’s deadline. Compare the options →
    What is the support model?
    Support scope and service levels are agreed in the scoping conversation and shared under non-disclosure. The SOC 2 Type II report for Reign Ops and the standard pack for procurement are released the same way, under non-disclosure. Security and trust →
    FINOS member Linux Foundation, Silver member
    Fluxnova itself is maintained by the FINOS community under Apache 2.0. We operate a distribution of it; we do not own it, and nothing here makes the engine ours.

    Camunda is a registered trademark of Camunda Services GmbH. iTmethods is not affiliated with or endorsed by Camunda, and provides independent managed services and migration support for Camunda software.

    Next step

    Tell us where Camunda and Fluxnova run today.

    Which edition or version you are on, roughly how many process definitions are in production, and what is forcing the question. We will come back with what the work actually involves, what we would take on first, and which part of the estate we would leave where it is.

    Discuss your Camunda or Fluxnova estate The benchmark results →