Start a conversation

Operate. Build. Govern. Assure.

Reign Ops operates engineering platforms, Reign Factory adds software-delivery capacity and Reign Gateway governs AI traffic. Reign Assurance is in co-design development. Start with the capability that addresses your immediate priority.

What is Reign → Explore all four →

Operate

Reign Ops

iTmethods assumes the agreed operating responsibilities for the engineering tools and open source services in scope, including change, incident and lifecycle management.

Modern DevOps Secure source control AI substrate Managed Fluxnova Services Cloud and AI cost

Available today

Build

Reign Factory

Factory adds implementation and test capacity for eligible, well-specified work and opens a merge request in the customer’s existing review process.

The delivery path Approval gate What you gain

Available · Beta Release

Govern

Reign Gateway

Gateway applies identity, access, policy and spend controls and creates an evidence record showing the request, policy decision and outcome.

How a model or tool request is handled Identity and authorization Evidence records Interfaces and trust

Available today

Assure

Reign Assurance

Reign Assurance is being designed to help business and risk leaders see whether defined AI-enabled work met its intended outcomes and stayed within agreed risk and regulatory requirements.

The operating model Requirement to evidence Results and evidence

Co-design development

AWS Advanced Tier & Validated MSP. SOC 2 Type II on Reign Ops. Current details are available under non-disclosure.

Explore the Reign portfolio →

Solutions

Business outcomes for engineering and AI-enabled work.

Remediation, upgrades, delivery, and the regulatory map around them. One repository, one delivery path, and a written recommendation to continue, narrow or stop.

Talk to us about your priorities →

By challenge

Remediation that stays openIdentified, owned, waiting on capacity. Upgrades that keep slippingMoves where the result is already known. Delivery the business is waiting onCommitments slip as engineers are absorbed. AI already in your workflowsAdopted. The governance did not follow. AI you cannot evidenceRunning, but nothing a committee can read. Cloud and AI spend that is structuralWaste built into the architecture, not into habits. Atlassian Data Center is endingThere are self-managed options.

By role

For technology leadersThe estate, the boundary, and the backlog. For Chief Risk OfficersResidual risk, model risk, board pack. For CISOsThe AI surface and the evidence. For Chief Audit ExecutivesAssurance the committee can read.

By sector

Banking and capital marketsOSFI, SR 26-2, and DORA. Health and life sciencesGxP and 21 CFR Part 11. Public sector and defenseDefine where the work runs and who can access it.

Start here

Talk to us about your priorities

Start with one repository or one delivery path.

Talk to us →

Regulatory context

Regulatory contextSR 26-2, OSFI E-23, DORA, ISO 42001. OSFI E-23Model risk for federally regulated institutions. EU AI ActHigh-risk systems and documentation. SR 26-2 · model risk and validationFed, OCC and FDIC. Supersedes SR 11-7.

Trust

Security, deployment and evidence.

Boundary, isolation, deployment and framework mapping.

Security and trust →

Boundary and control

Where Reign Factory sitsThe delivery path, end to end. Who approves whatFour limits, fixed by design. Isolation and tenancyA dedicated instance for each customer. Deployment optionsManaged or your own cloud. Air-gapped and sovereign deployment supported.

Frameworks

All frameworksSix of them, and where Reign sits. SR 26-2 · model risk and validationFed, OCC and FDIC. Supersedes SR 11-7. NIST AI RMF 1.0 · GenAI ProfileAI 100-1 and AI 600-1. Both final. EU AI ActCurrent dates and what they require. OSFI E-23Effective 1 May 2027. AI/ML in scope.

Security and evidence

Security postureHeaders, subprocessors, one attestation. Evidence and coverageWhat a reviewer can follow alone. What we measuredOne month, our own repositories.

Resources

Whitepapers, guides, and webinars.

Analysis on assured AI, and explainers written for the people who have to defend the decision internally.

All resources →

Knowledge

InsightsPerspectives on governance and agents. LearnExplainers, frameworks and references. Whitepapers and guidesLong-form guides, webinars and tools. FAQWhat each motion covers, and its agreed scope.

Proof

The measurement methodOur own figures, and the denominator. Case studiesWhat we can publish, and what changed. The maturity modelFive levels, and where you sit today.

Also

Why nowOne regulatory cycle, one operational. Open sourceLinux Foundation, FINOS, Agentic AI Foundation. EventsWhere to find us this year.

2026

Find us on the road

Big Data and AI Paris, MCP Dev Summit Toronto, Open Source in Finance Forum New York, and ISF World Congress Milan.

See all events →

Company

Critical infrastructure for enterprise AI.

iTmethods has run the systems regulated enterprises deliver software on since 2005. Reign is that estate: the platform, the work, the boundary and the evidence. Operated by the engineers who own the operational response.

About iTmethods → Contact us →

Company

About iTmethodsWho we are and what we run. LeadershipThe people accountable for Reign. CareersJoin the team. Press and announcementsReleases, milestones, media resources. ContactTalk to our team.

Partner with us

Ways to partnerAdvisory, technology or referral. Three categories, one conversation to start. Strategic infrastructureHyperscalers and silicon, not slideware. Open source and standardsLinux Foundation, FINOS and the Agentic AI Foundation. Co-design opportunitiesShape Reign Assurance with the people who will have to rely on it.

Featured partners

Summit58 (Fluxnova)Their process. Our platform underneath. ArcheraThey provide the instrument. We run it.

Become a partner

Tell us how you want to partner

Advisory, technology or referral. We will tell you what the relationship would actually involve, written down before anyone hears about it.

Start the conversation →

REIGN OPS · FLUXNOVA MIGRATION

Move the engine. Keep the processes.

Camunda 7 to Fluxnova, or Fluxnova 2.x to 3.0. We do the infrastructure half: engine, database, environments, identity, CI/CD, cutover, rollback, and performance validation. Your BPMN and DMN models come with you unchanged.

Model changes

None. Backward compatible

Scope

Fixed fee, sized to your estate

Environments

Dev, test, production, DR

Rollback

Planned before cutover, not after

Scope your migration

Delivered as a single-tenant dedicated instance, in our environment or in your own cloud account on AWS or Azure. Air-gapped and sovereign deployment are supported.

WHICH MOVE ARE YOU MAKING

Two paths, different urgency.

Camunda 7 to Fluxnova

Community Edition is past end of life. Fluxnova is the compatible, openly governed path forward. No re-platform, no model rewrite, no per-core license. Timeline is yours to set.

Fluxnova 2.x to 3.0

Spring Boot 4, fourteen library upgrades, Cockpit retirement, and end of support for JBoss and WildFly. If you are on either app server this is not optional and it has a clock on it.

SCOPE

Two jobs, one named owner each.

iTmethods takes the infrastructure half. Summit58 takes the functional half, and the boundary is named before work starts.

iTmethods · infrastructure

Engine deployment and topology
Database migration and schema
Environment build across dev, test, production
Identity, secrets, CI/CD integration
Cutover planning, rollback, performance validation

Summit58 · functional

BPMN and DMN process definitions
Business logic and rules
Forms and task interfaces
Process semantics and behavior
Business validation and UAT
Training your process modellers

Migrating running process instances sits across both. We name an owner for it per engagement rather than leaving it to a general rule.

Migration Readiness Guide

Estate inventory template, compatibility checklist, environment and cutover sequencing, rollback criteria, and the questions to settle before anyone touches a database. Available shortly. Ask for it on your scoping call in the meantime.