Skip to main content
    Reign for enterprise engineering and AI

    Accelerate software delivery.
    Govern AI-enabled work.
    See whether it worked.

    Reign operates the engineering platforms your teams rely on, adds capacity to build and test defined software work, and applies agreed controls to AI traffic sent through Gateway. Reign Assurance is being designed to help business and risk leaders assess whether defined AI-enabled work met its intended outcome and the risk and regulatory requirements set for it.

    Memberships
    Linux Foundation · FINOS · Agentic AI Foundation
    AWS designations
    Advanced Tier Services Partner · Validated Managed Service Provider
    Attestation
    iTmethods holds a SOC 2 Type II attestation for Reign Ops; the report, scope and period are available under non-disclosure
    Tenure
    21 years operating critical infrastructure
    What Reign covers

    Four capabilities, focused business outcomes

    Reign offerings: Ops to operate engineering platforms, Factory to implement and test defined software changes, or Gateway to govern model and tool calls. Reign Assurance is being designed to assess the work and its business outcome using evidence from the systems in scope.

    Operate

    Reign Ops — Operate engineering platforms

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

    What you get. Your engineers have more capacity for software delivery, while incidents and upgrades move through the operating process you agreed.
    Build

    Reign Factory — Increase software-delivery capacity

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

    What you get. Your team gains capacity to move eligible software work toward review, with checks, findings and open issues visible before anyone decides what ships.
    Available · Beta Release See the delivery path →
    Govern

    Reign Gateway — Govern AI traffic

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

    What you get. For calls sent through Gateway, you can review what was requested, the policy decision and the recorded outcome.
    Available today How the boundary works →
    Assure

    Reign Assurance — Assess AI-enabled work against agreed outcomes and requirements

    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.

    Co-design target. Business and risk leaders can assess whether defined AI-enabled work met its intended outcomes and stayed within agreed risk and regulatory requirements, and see where further review is needed.
    Co-design development Co-design it with us →

    Planned capability: Reign Gateway will support policy-controlled failover across customer-approved models.

    What operates today is dated in the product status register, and what each published figure was measured on is at what we measured.

    Reign Factory · Available · Beta Release

    Accelerate software delivery, in control.

    Reign Factory adds implementation and test capacity and opens merge requests in your repository. Your source control, checks, approvals and release process determine what ships.

    Increase capacity for software delivery

    Factory takes on eligible remediation, upgrade and roadmap work through a defined implementation and test path.

    Focus engineers on work that needs their judgment

    Factory performs the implementation and test work while software engineers focus on product direction, architecture and complex delivery decisions.

    Keep software delivery controlled and consistent

    Each change arrives as a merge request with its checks, results, findings and open issues attached. The customer’s repository, pipeline, reviewers, approval policy, merge decision and release process determine what ships.

    A small software team produced an initial working version of Reign Gateway in about three months. iTmethods used Reign Factory in its own production engineering, then continued building and hardening the product through the same source-control, test, review and approval path its software engineers use today.

    This is one internal product-development example, not an expected customer timeline or a comparison with traditional development.

    From a ticket to a merge request

    Increase software-delivery capacity — your controls still decide what ships.

    You assign eligible work to Reign Factory. It performs implementation and test work under an agreed method, then opens a merge request in your repository with its checks and findings attached. Your source control, reviewers, approvals, pipelines, merge and release process determine what ships. When an item needs a product, architecture or priority decision, Factory involves the person responsible.

    Reign Factory · operated for you
    Your software project · your controls remain decisive
    Eligibility
    The rules you set for what it may touch. Tested, and visible to you.
    Implementation
    Factory works on the eligible item under the agreed method.
    Gateway and checks
    Policy at the boundary. Build and test first.
    Merge request
    Opened in your repository, carrying its findings.
    Your checks
    Your pipeline runs the required checks.
    Review and approval
    The stages you run. Your policy decides.
    Merge and release
    Your rules, your process.
    Involves a person where judgment is needed Out of scope · check unmet · needs judgment
    A named person receives the item’s current state and reason, reviews it and approves any next step.
    It works only on eligible work you assign. Eligibility rules decide what it may touch, and the rule that refused an item is visible to you.
    Your policy decides. Review, approval, merge and release stay yours.
    Standards and frameworks

    The frameworks we map to.

    For an engagement that needs it, we work with the customer’s compliance function and counsel to map relevant Reign controls to the applicable requirements in one or more of the frameworks below.

    NIST SSDF · SP 800-218 with SP 800-218A

    Secure development practice, including for generative AI.

    NIST AI RMF 1.0, with the Generative AI Profile

    Structures the AI governance and risk questions an engagement answers.

    SOC 2 TSC and ISO/IEC 27001:2022 Annex A

    Control objectives are mapped, and we walk your control function through the register row by row.

    ISO/IEC 42001, EU AI Act, OSFI Guideline E-23

    Built to support your obligations under each, applied as an engagement overlay where your jurisdiction makes it relevant.

    How we work with you

    Start with one priority.

    Bring us a delivery priority, an operational challenge or an AI use case. We work with your engineering, operations, risk and compliance teams to define the work, agree who does what and move it forward.

    1

    Name the work

    Choose the outcome you want to advance and the first piece of work that will show progress.

    2

    Agree how we work

    Set responsibilities, access, controls and the measures that matter for that work.

    3

    Deliver together

    Our engineers work with the people who own the systems and decisions.

    4

    Review the result

    Review the work and its evidence, then agree what to advance next.

    The way we engage follows the work: we can operate services for you, deliver alongside your engineers, or design assurance with your risk and compliance teams.

    See deployment options →
    The ask

    Let’s discuss your priorities.

    Tell us what you want to move forward.