Govern AI use with evidence.
Reign Gateway applies approved identity, access, policy and spend controls to AI calls sent through it and creates an evidence record for each governed call. Reign Factory opens each change as a pull request with check results, and your reviewers approve every merge.
Available today
Make the operating decisions explicit.
Your teams decide which AI uses, models, tools and identities are approved. Reign Gateway applies those decisions to traffic sent through it and records the result.
Name the application or agent, its owner and purpose, the models and tools it may reach, and the access and spend limits that apply.
Gateway checks identity and access, applies policy and spend limits, and sends permitted requests to an approved model or tool.
Each governed call creates an evidence record showing the caller, policy decision, destination, outcome, time and cost, subject to approved capture settings.
Your decisions remain visible in the operating record.
| Who | What they decide or do |
|---|---|
| Business and risk owners | Define the approved purpose, risk appetite, accountable owner and response to exceptions. |
| Security and engineering teams | Define identities, access, approved models and tools, technical policy, spend limits, capture and retention settings. |
| Your engineering reviewers | Approve or decline each Reign Factory pull request; nothing merges without them. |
| iTmethods | Operates Reign Gateway and applies the approved configuration to traffic sent through it. |
| Risk, compliance and audit experts | Assess the evidence against the organization’s objectives and obligations. Auditors are responsible for any audit opinion or certification. |
Review AI-enabled work with evidence you can trace.
Internal audit sets the review objective, evaluates the evidence and reaches its conclusions. Business, risk and compliance teams make the operating and reliance decisions within their roles. Any audit opinion, certification or independent assurance is issued by an appropriately independent reviewer.
See the identities, routes, policies and activity recorded for the systems being reviewed.
Trace a request from the caller and policy decision to its destination and outcome.
Gateway writes evidence records to configured customer-controlled S3-compatible storage under the customer’s access and retention settings.
Changes made by agents. Each Reign Factory change arrives in your repository as a pull request with its check results, and a named reviewer from your team approves the merge. Internal audit can sample those pull requests the way it samples any other change.
Coverage follows the path. Gateway records the calls sent through it, and the deployment record states the selected environment and its access, capture and retention settings. Review deployment options →
Use the evidence in the framework your organization operates.
AI and model-risk expectations differ across Canada, the United States and the European Union. Our regulatory pages explain the scope, dates and practical implications of the instruments they cover. Specific mappings are established with your compliance function and counsel.
Discuss one AI traffic path or workflow.
We can discuss who owns it, which policies apply and what evidence your risk and audit teams can use today.