Build
Tickets in.
Pull requests out. Reign Factory
Tickets in, tested pull requests out, through the delivery process you already have. Your reviewers approve every merge.
Governed AI software delivery
Ship the backlog.
Keep control of what ships.
Reign Factory turns your tickets into tested pull requests. Your reviewers approve every merge.
Tickets in.
Govern
Identity, policy and a record of every model and tool call Factory makes. Reign Gateway
Operate
The SDLC platforms Factory delivers on, with scanning, version control and gating, operated 24×7. Reign Ops
Contrast
Without Reign. With Reign.
01Factory
The backlog waiting on engineers.
Without ReignDefined work waiting for engineering time. Tickets sit until someone can pick them up.
With ReignReign Factory turns your tickets into tested pull requests. Your reviewers approve every merge.
02Gateway
Model calls with no policy or spend limits.
Without ReignEvery team calling models on its own, with no shared policy, spend limit or record.
With ReignReign Gateway gives every team one governed path to the models it uses, with spend limits and your policy on each call.
03Ops
SDLC platforms eating your team's time.
Without ReignThe platforms you deliver on stay on your team. Scanning, version control and gating take time from product work.
With ReignReign Ops operates the platforms you deliver on, 24×7. Your engineers spend their time on the product, not on keeping the platform alive.
Use cases
What it works on.
How the work flows
Your tools and rules on either side. Reign in the middle.
Your team and tools
In GitHub, GitLab, Jira or Linear
Which work qualifies, and who approves
Reign Factory
Queues your tickets and runs the workers
3 · Build and test → 4 · Fix and re-check
Scale workers based upon demand
Identity, policy, spend limits and a record of each call
Your review and release
In your repository, checks attached
Your reviewers decide what merges
Your pipeline ships it
Every step is governed and recorded, aligned to the FINOS SDLC Common Controls Catalog.
Integrations
Works with your tools.
Slack, GitHub, GitLab, Jira and Linear, plus OpenAI-compatible and Anthropic-compatible endpoints.
- GitHub
- GitLab
- Jira
- Linear
- Slack
- OpenAI-compatible
- Anthropic-compatible
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, and Reign Assurance in co-design development. 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, and Reign Assurance is in co-design development.
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.
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.
- 01Where it runsYour AWS or Azure account, or Reign Dedicated. Single-tenant, always.
- 02Accounts and keysYour models, on your own accounts and keys.
- 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.
Provenance record · SEC-482
AgentReign Factory worker
ModelYour provider, your keys
Changepayments-api · pull request 1187
Checksunit tests and SAST passed
ApproverNamed reviewer, 15:12 UTC
StoredWrite-once, in your storage
ExampleSample screen. Fictional names and numbers.
2 decades
operating the platforms regulated enterprises deliver software on
Single-tenant
in your own AWS or Azure account, or on Reign Dedicated
SOC 2 Type II
attestation on Reign Ops
Open by design
with your models and keys, built by a member of the Linux Foundation, FINOS and the Agentic AI Foundation
Self-funded and profitable since our founding
Existing iTmethods customer?
Your service continues, unchanged.
The platforms we already run for you are now Reign Ops. Same team, same service levels, same agreements.