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
    SectorsBanking and capital markets

    Put ownership and evidence behind technology change.

    Reign helps banks operate engineering platforms, move defined software changes through review and govern AI traffic. Its operating and evidence records give engineering, risk, compliance and audit teams material they can review.

    Technology change

    Connect the work to the record.

    Software changes

    Reign Factory is available today for eligible, well-specified work. It implements and tests the change, then opens a pull request in the bank’s existing review process.

    Reign Factory →

    AI traffic

    Reign Gateway is available today. It applies identity, access, policy and spend controls to AI calls sent through it and creates an evidence record showing the caller, policy decision and outcome.

    Reign Gateway →

    Operated engineering platforms

    Reign Ops is available today. iTmethods assumes the agreed operating responsibilities for the engineering tools and open source services in scope, subject to agreed service measures.

    Reign Ops →
    Canada, the United States and the European Union

    Model-risk and resilience expectations differ by jurisdiction.

    Canada

    OSFI Guideline E-23

    Published on 11 September 2025 and taking effect on 1 May 2027, E-23 applies enterprise-wide model-risk principles to federally regulated financial institutions and addresses AI and machine learning methods in its model-risk context.

    OSFI Guideline E-23 at osfi-bsif.gc.ca ↗

    Our E-23 page →

    United States

    SR 26-2

    Issued on 17 April 2026, the revised US guidance excludes generative and agentic AI from its scope. It directs banking organizations to use their own risk-management and governance practices for tools, processes and systems outside the guidance.

    SR 26-2 at federalreserve.gov ↗

    Our model risk and validation page →

    European Union

    DORA

    DORA has applied since 17 January 2025. It addresses ICT risk, resilience and third-party oversight for financial entities, including an EU oversight framework for providers designated as critical.

    Read the European Commission’s DORA overview →

    Read the EBA’s oversight framework →

    The EU AI Act page, where credit scoring is an Annex III high-risk use →

    These instruments provide context for the operating and evidence needs described on this page. The bank’s risk and compliance functions and counsel determine applicability, required controls and how the evidence is used. Beyond SOC 2 Type II for Reign Ops, no other certification or accreditation is claimed.

    Where the work runs

    Choose the deployment model that fits the system and data scope.

    A bank’s risk, compliance and audit teams review where applications, data and records sit and who holds administrative access. The Deployment page explains how each is recorded.

    01Single-tenant
    A dedicated single-tenant deployment for each customer. There is no multi-tenant or shared option.
    02Where it runs
    In infrastructure iTmethods operates, or in the customer’s AWS or Azure account.
    03Air-gapped and sovereign
    Air-gapped and sovereign deployment are supported.

    Review deployment options →

    Next step

    Discuss one banking technology priority.

    Let’s start with one engineering platform, software change or AI traffic path and the teams that need to review it.