Control how your applications and agents use AI.
Reign Gateway applies identity, access, policy and spend controls to calls that applications and agents send through it. It creates an evidence record showing the caller, policy decision and outcome, subject to approved capture settings.
Available today
Apply identity, access and policy to every governed call.
For traffic in scope, applications and agents send calls through Gateway to approved models and tools. Gateway checks the caller’s identity and access, applies the policy and spend limit for the request, routes it to an approved destination and records the outcome.
01 · Know who or what is calling
Connect each governed call to the application, agent or user identity making it. Security teams can review access through the agreed identity and authorization model.
02 · Apply policy and spend limits
Check the rules and budgets assigned to that identity and workload while the call is being handled.
03 · Use approved models and tools
Route each governed call to the models and tools approved for that use. Gateway does not fail over between models automatically. When a model does not answer, the call is recorded as failed; it does not fall back to a model your policy has not permitted.
See how each governed call was handled.
Each call routed through Gateway creates an evidence record showing the caller, route, policy decision, destination, outcome, time and cost, subject to approved capture settings. Security teams can use these records alongside their monitoring and response processes to review access, investigate activity and explain how a call was handled.
Coverage follows the path. Gateway creates records for calls routed through it. Your wider security program covers AI traffic that uses other routes.
Bring governed AI traffic into the reviews you already run.
Security, risk, compliance and audit teams can use Gateway’s controls and evidence in their existing reviews. Those experts determine how the controls support the organization’s obligations and what conclusions the evidence supports.
The Deployment page sets out where Reign can run and how the application, data, access and operating boundaries are recorded.
iTmethods holds a SOC 2 Type II attestation for Reign Ops. The report, scope and period are available under non-disclosure. Reign Gateway runs on the same infrastructure as Reign Ops, and is operated by the same operations team under the same processes. The SOC 2 Type II scope is being updated to include it.
Architecture, data flow, subprocessors, access control, change control, logging and incidents, the model boundary and the attestation report, released under non-disclosure. Write to security@itmethods.com or raise it in a briefing.
Report a suspected vulnerability through security@itmethods.com or the published security.txt.
Bring one AI traffic path.
Let’s discuss one AI traffic path you want to govern, the policy you want to apply and the evidence your security team needs.