Skip to main content
    Meet us at the ISF World Congress in Milan, November 14 to 17. Ontario Pavilion, Stand 7.Book a meeting
    Book a demo
    The New Stack · Article 6 of 6

    The Camunda 7 Fork That Financial Services Built. And Why It Changes Everything for AI Governance

    A FINOS community fork of Camunda 7 is now hosted under the Linux Foundation, announced in October 2025 with four financial institutions named as partners. Here is why this changes the AI governance conversation entirely.

    Editor’s note, October 2026. Written on April 6, 2026, before Fluxnova 3.0. Since then the project’s release notes on GitHub (opens in a new tab) show Fluxnova 3.0 (July 20, 2026) and 3.1.1 (October 23, 2026), which removes WildFly and JBoss support. Before you plan a move, read Fluxnova 3.0: What Shipped, What Breaks, What To Do.

    Camunda 7 Community Edition is dead.

    The repository is archived. No security patches. No PRs accepted. If you are running Camunda 7 CE in production at a regulated institution, you are running unsupported software. Today.

    Camunda 7 Enterprise Edition gets a reprieve, extended through April 2030, but the final feature release (7.24) shipped in October 2025. The clock is ticking.

    And the migration path that Camunda is offering? Camunda 8 is not an upgrade. It is a reimplementation. Different engine (Zeebe), different API, different data model, different licensing. Third-party analysts are blunt: “Trying to do a technical migration is a recipe for disaster.” Small projects take 2 to 3 months. Large ones take 6 to 12 months or more. And Camunda 8 has no open-source variant.

    So what happens when 2,600+ companies (many of them in financial services, where BPM engines underpin loan origination, KYC/AML, trade processing, and regulatory reporting) face a forced migration to a proprietary platform?

    The same thing that happened with Terraform, Redis, and Elasticsearch.

    The industry forks.

    2,600+
    CAMUNDA USERS
    GLOBALLY
    $0
    LICENSE COST
    APACHE 2.0
    v2.0
    AIGF RISKS
    GOVERNED

    The Fork Financial Services Built

    In October 2025, at the Open Source in Finance Forum in New York, FINOS announced Fluxnova: a fork of the last Apache 2.0-licensed version of Camunda 7, hosted by FINOS.

    The institutions behind it tell the story: four financial institutions named as partners in FINOS’s launch announcement of October 21, 2025 (opens in a new tab).

    These are not hobbyists. They are financial institutions whose people and resources are showing up, under the Linux Foundation CLA, to collaboratively chart the future of an orchestration engine they will not outsource to a single vendor. FINOS Executive Director Gabriele Columbro called it “the first time financial institutions exercise their right to fork to collaboratively chart their future under open governance.”

    Existing BPMN and DMN models created for Camunda 7 work with Fluxnova with minimal modification. A migration utility automates much of the transition. No reimplementation. No new licensing cost.

    The pattern is now unmistakable:

    Terraform→OpenTofu
    Redis→Valkey
    Elasticsearch→OpenSearch
    Camunda 7→Fluxnova

    Every time a critical open-source tool moves to a proprietary model, the ecosystem responds.


    Why This Is Existential for Regulated Industries

    Here is the part most people miss: in regulated industries, process orchestration engines are not just tooling. They are the compliance substrate.

    A BPM engine like Camunda 7 touches the audit trail. Regulators (OSFI, OCC, FCA, ECB) do not just want to know what happened. They want to know how the process was defined, who approved the workflow, when it executed, and why it made the decisions it did. The orchestration engine is the system of record for all of that.

    It is embedded in change management. Every modification to a production workflow goes through change advisory boards, model risk review, and often regulator notification. A forced migration is not a software upgrade. It is hundreds of individual change tickets, each requiring re-testing, re-validation, and re-approval.

    And as agentic AI enters production, the orchestration engine is becoming the governance boundary: the system that decides whether an AI agent can execute a trade, approve a loan, or release a drug batch. If that layer is controlled by a single vendor who can change terms unilaterally, the institution has outsourced its regulatory posture to a third party.

    That is precisely what OSFI’s B-10 guidance on third-party risk, the EU’s DORA regulation, and the OCC’s critical service provider framework are designed to prevent.

    The vendor lock-in question is not theoretical. It is existential.


    The Missing Piece: Who Governs the Agents?

    Fluxnova solves the orchestration independence problem. But it opens a new question that nobody has answered yet.

    FINOS’s launch announcement of October 2025 (opens in a new tab) tied Fluxnova to agentic AI: with agents on the rise, it said, orchestrating models, agents and external systems matters more than ever.

    But a control plane without governance is a liability. If an AI agent operates within a Fluxnova workflow (approving a transaction, classifying a regulatory filing, routing a customer complaint), who governs that agent? Who enforces the policy boundaries? Who captures the evidence trail that satisfies the examiner?

    The FINOS AI Governance Framework (AIGF v2.0), released in late 2025 and developed collaboratively by FINOS member institutions with Tetrate leading the v2.0 agentic extension, defines a catalogue of risks and corresponding mitigations across operational, security, and regulatory dimensions, with explicit alignment to ISO 42001, OWASP, and MITRE ATLAS. New risks in v2.0 target agentic architectures specifically: multi-agent trust boundary violations, agent action authorization bypass, tool chain manipulation, MCP server supply chain compromise, agent state persistence poisoning, and agent-mediated credential harvesting.

    This is where orchestration and governance converge. The institutions forking Camunda 7 into Fluxnova are the same institutions co-authoring the AI governance framework. They need both halves of the equation: an open-source orchestration engine they control, and a governance layer that enforces controls at runtime, not just in policy documents.


    The Question for Every Camunda 7 Shop

    If you are running Camunda 7 in production at a regulated institution, you have three options:

    1

    Migrate to Camunda 8

    Proprietary, 6 to 12 month reimplementation, new licensing model

    2

    Stay on unsupported CE

    Increasing compliance risk with every passing month

    3

    Move to Fluxnova

    A FINOS-hosted open source project, with sponsors among the largest financial institutions on the planet. See Fluxnova 3.0: what shipped, what breaks, the Fluxnova overview and Managed Fluxnova.

    The question is not whether to adopt the fork. The question is whether you want to run it yourself or have it operated for you.

    At iTmethods, we have been building at this intersection. Reign Ops runs Managed Fluxnova today, as a single-tenant dedicated instance. If you are running Camunda 7 and evaluating your options, I would welcome the conversation.

    Managed Fluxnova on Reign Ops

    Open-source BPM. Operated for you, single-tenant.

    PG

    Paul Goldman

    Founder and CEO, iTmethods

    Founder and CEO of iTmethods. Writes Governed Delivery, essays on building and delivering software with AI agents, keeping the business safe, and owning the outcomes. His team runs the platform, does the work, and proves it.

    Continue reading The New Stack

    Governed Delivery.

    Build faster. Keep the business safe. Own the outcomes. Practical lessons on delivering software with AI agents. One email per essay.

    Talk to the team that runs the work.

    Reign Ops operates the platforms you deliver on, 24x7. Reign Factory and Reign Gateway are available today; Gateway is available on its own or included with Factory. Tell us what you are solving for and we will route it to the people who own that work.

    Book a briefing