Skip to main content
    Reign OpsManaged Fluxnova

    Managed Fluxnova, operated by Reign Ops.

    Fluxnova is the FINOS distribution based on the Camunda 7 engine. 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 →
    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.

    The process stays yours; Reign Ops operates the platform The process Your BPMN and DMN models, your decision tables, your integrations Summit58 designs and integrates them with you where you want it Yours The platform The engine, the instance, patching, backup and restore, the pager Reign Ops The engine is Apache 2.0 under FINOS, and it stays that way.
    Your models, decision tables and integrations run on an Apache 2.0 engine and move with you. Summit58, the process design partner, does BPMN and DMN design and integration work where you want it.
    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 migration path →

    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 moved Spring Boot and fourteen end-of-life libraries. Cockpit is being retired, and JBoss and WildFly support is ending. If you run either app server, this is a forced move rather than a planned one.

    03If a wider re-platform is possible
    Compare the options on process compatibility, migration effort, data, integrations, operating model and cost.

    Let the customer requirements determine the recommendation.

    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.

    Partners

    Process design and platform operations

    Summit58 provides process analysis, BPMN and DMN design, agentic process design and integration work. Reign Ops operates the Fluxnova platform.

    “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

    Summit58 and Reign Ops together →

    Benchmarks

    An identical invoice process, run on three engines on matched infrastructure.

    One thousand workflow instances on Camunda 7, on Fluxnova and on Camunda 8. Fluxnova is Apache 2.0 and open source, and on this workload it ran in the same performance class as Camunda 7 — so moving off Camunda 7 Community Edition costs no throughput, and the process models move across unchanged.

    <25sFluxnova and Camunda 7, one thousand workflows, zero failures
    15×Longer for Camunda 8 on the same workload
    0Model changes needed to move from Camunda 7

    Measured on our own invoice process and our own 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. 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. Reign Assurance is in co-design development. Nothing on this page depends on it. It is being built to turn requirements into checks that run against the work and prepare evidence for review; commercial availability and terms are undecided.How the boundary works → · Where Assurance stands → · What shipped in 3.0 →
    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 deployment is supported for isolated or offline operation. Sovereign deployment is supported for the agreed jurisdictional, data-location and operating requirements. There is no multi-tenant or shared option. Deployment models in full →

    FAQ

    What is Fluxnova?
    A FINOS community fork of Camunda 7 Community Edition, launched in October 2025 by a group of global banks and asset managers. Apache 2.0, BPMN and DMN, hosted under the Linux Foundation.
    Is it actually maintained?
    Yes, actively. Version 3.0 shipped in July 2026 with a Spring Boot 4 upgrade, fourteen further library upgrades, a new Control Center UI and a plugin ecosystem. The gap for a regulated institution is not maintenance. It is operation.
    Are my Camunda 7 processes compatible?
    Yes. Fluxnova maintains backward compatibility with Camunda 7 BPMN 2.0 and DMN models. Existing process definitions, decision tables and REST integrations move directly. The benchmark above measured zero model changes on the move.
    What changed in 3.0?
    Spring Boot 4 and fourteen end-of-life library upgrades, a Control Center UI covering process definitions, heat maps, instance migration and incident replay, adhoc subprocesses, restricted variables for personal data, a plugin ecosystem, MCP integration and agentic adhoc subprocesses. 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. Managed Camunda →
    What is the support model?
    Support scope and service levels are documented per engagement and available under non-disclosure. Attestation status and the standard pack for procurement are released the same way rather than asserted on a web page. Security and trust →
    SOC 2 Type II on Reign Ops 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.
    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 migration path →