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
    Governed AI software delivery

    Ship the backlog.
    Keep control of what ships.

    Reign Factory turns your tickets into tested pull requests. Reign Gateway records every model call it makes. Your reviewers approve every merge.

    Book a briefing See how a change ships
    Sample screen. Fictional names and numbers.
    • SOC 2 Type IIAttestation on Reign Ops.
    • Single-tenantIn your AWS or Azure account, or on Reign Dedicated.
    • 2 decadesOperating the platforms regulated enterprises deliver on.
    • Open by designA member of the Linux Foundation, FINOS and the Agentic AI Foundation.
    Three products

    One governed path from ticket to release.
    Use one, or all three together.

    Build
    Reign Factory

    Tickets in.
    Pull requests out.

    Tested pull requests through the delivery process you already have. Your reviewers approve every merge.

    • Roadmap backlog: defined work waiting for engineering time.
    • Security remediation: findings turned into fixes, one pull request each.
    • Upgrades: dependency, framework and platform upgrades.
    • Migrations: repeatable change across a codebase.
    Book a briefingSee Reign Factory

    Sample screen. Fictional names and numbers.

    reign.internal/factory/backlog
    Backlog4 tickets
    LEDGER-412
    Add idempotency keysFeature
    Open
    SEC-88
    Fix SQL injection in /searchSecurity
    Open
    PLAT-231
    Upgrade Spring Boot 3.3Upgrade
    Open
    LEDGER-415
    Move logging to OpenTelemetryMigration
    Open
    Govern
    Reign Gateway
    Allowed, blocked or masked.

    One governed path to the models your teams use. Your policy decides.

    See Reign Gateway

    Sample screen. Fictional names and numbers.

    Calls through Reign GatewayLive
    payments-apiClaude Sonnet
    Checking
    data-scienceMasked by a guardrail
    Checking
    coding agentBlocked: spend limit
    Checking
    Record written, your storage
    Operate
    Reign Ops
    24×7

    The SDLC platforms you deliver on, operated for you.

    See Reign Ops

    Sample screen. Fictional names and numbers.

    PlatformsOperated 24×7
    Source controlnorthwind-git
    Checking
    Scanningpayments-scan
    Checking
    CI gatepayments-ci
    Checking
    Artifact storenorthwind-artifacts
    Checking
    How the work flows

    Your tools and rules on either side.
    Reign in the middle.

    Your team and tools
    Reign Factory
    Your review and release
    LEDGER-412Ready
    Add idempotency keys
    Defined work waiting for engineering time.
    In your tools
    GitHubGitLabJiraLinear
    Rules you set
    Which work qualifies
    Who approvesD
    SupervisorQueuedRunningDone
    AI workerWaitingBuild and testFix and re-checkPassed
    AI workerWaitingBuild and testFix and re-checkPassed
    AI workerWaitingBuild and testFix and re-checkPassed
    Reign Gateway on model calls
    IdentityPolicySpend limitsRecord
    Record written
    payments-api · pull request 1187
    Add idempotency keysOpenMerged
    Checks attached
    Unit tests
    SAST
    Your pipeline
    DDana OrtizYour approvalReviewingApproved
    Your releaseYour pipeline ships it
    Sample screen. Fictional names and numbers.
    1. Ticket: In GitHub, GitLab, Jira or Linear
    2. Rules you set: Which work qualifies, and who approves
    3. Supervisor: Queues your tickets and runs the workers
    4. Build and test, then fix and re-check: AI workers, scaled to demand
    5. Reign Gateway on model calls: Identity, policy, spend limits and a record of each call
    6. Pull request: In your repository, checks attached
    7. Your approval: Your reviewers decide what merges
    8. Your release: Your pipeline ships it

    Every step is governed and recorded, aligned to the FINOS SDLC Common Controls Catalog.

    • GitHub
    • GitLab
    • Jira
    • Linear
    • Slack
    • OpenAI-compatible endpoints
    • Anthropic-compatible endpoints
    Why it matters

    Sovereign

    Reign lives inside sovereign.

    Sovereignty is a deployment property, not a separate product. Where it runs changes; how the work is governed does not.

    How Reign keeps it yours →

    1. 01Where it runsYour AWS or Azure account, or Reign Dedicated. Single-tenant, always.
    2. 02Accounts and keysYour models, on your own accounts and keys.
    3. 03The recordChanges in your repository. Every governed call in storage you own.

    The brackets in the Reign mark stand for your boundary.

    Governance, built in

    Every agent change leaves a record your auditors can read.

    Mapped to FINOS SDLC³, the open catalog of SDLC controls for financial services. Reign supports the evidence for its agentic control, SDLC-SEC-013.

    Get the SDLC³ control mapVisit Governance
    Provenance record · SEC-482Stored
    Agent
    Reign Factory worker
    Model
    Your provider, your keys
    Change
    payments-api · pull request 1187
    Checks
    unit tests and SAST passed
    Approver
    Named reviewer, 15:12 UTC
    Stored
    Write-once, in your storage
    Sample screen. Fictional names and numbers.
    Delivery

    Run for you, or with you.
    Either way, we own the outcome.

    Your policies and checks, set up and kept current by our engineers.

    • Reign engineers
    • Your team
    • Together
    Run for you

    Our engineers run it.

    Reign engineers run, monitor and upgrade the service, and set up your agents, models, checks and stop rules.

    • Policies and checks kept current by our engineers
    • Your named reviewer approves every merge
    Run with you

    Your team runs it, we work beside it.

    Your engineers run it. Ours work alongside your team and coach it.

    • You author the catalog of what is sanctioned; the boundary enforces it
    • Your named reviewer approves every merge
    Either way: a named Reign engineer owns the work from ticket to production, and the record stays in storage you own.How we are accountable
    FAQ

    Questions buyers ask.

    What is Reign?

    Reign is the iTmethods product line for building and operating AI work inside regulated environments. It is three products available today. Reign Factory: tickets in, pull requests out. Reign Gateway: one governed path to the models your teams use. Reign Ops: the platforms you deliver on, operated for you.

    Which agents and models does it work with?

    Your choice, on your own accounts and keys: OpenAI, Anthropic, Gemini, Bedrock, Azure OpenAI, or bring your own models, including open-weights models on your own endpoint. Claude Code, GitHub Copilot and Cursor, and apps built on the OpenAI or Anthropic SDKs. Each one points at the same endpoint, so the same policy and record apply.

    Do I change my CI?

    Reign Factory works through the delivery process you already have. Your CI/CD runs on every change. Agents run your checks and fix failures before a pull request opens.

    Where does it run?

    It stays in a dedicated, single-tenant instance in your AWS or Azure account, or on Reign Dedicated. Air-gapped and sovereign deployment are supported. Google Cloud is planned for 2027.

    Who approves merges?

    Your reviewers approve every merge. Nothing merges without your approval.

    What is available today?

    Reign Factory, Reign Gateway and Reign Ops are available today.

    Do the three Reign products work together?

    Yes, and each one stands on its own. Reign Factory builds, Reign Gateway governs what crosses to a model, and Reign Ops operates the delivery platform. Adopting one product does not commit you to another, and no product is available because another one is.

    Existing iTmethods customer?

    Your service continues, unchanged. The platforms already run for you are now Reign Ops.

    What is changing

    Bring one piece of work
    you want to advance.

    Book a briefing