Where Reign runs. Always inside your trust boundary.
Open, sovereign, bespoke. Reign meets you where your data residency, regulatory, and sovereignty obligations live. Same governance layer across every topology.
Topologies
Four topologies. One governance layer.
Pick the topology your obligations require. The Audit Ledger, AI Gateway, Model Risk Validation, and Assurance Packs behave identically across all four.
Multi-tenant cloud
Reign operated by iTmethods in a logically isolated multi-tenant environment on AWS, Azure, or GCP.
Enterprises beginning to operationalize AI governance who want a fast path to a working trust layer without standing up dedicated infrastructure.
Supports SOC 2 Type II, ISO 27001, NIST AI RMF, GDPR, EU AI Act on shared infrastructure with tenant-level data isolation.
Dedicated cloud
Reign operated by iTmethods in a single-tenant environment with dedicated compute, storage, and network on AWS, Azure, GCP, or NVIDIA DGX Cloud.
Established AI programs in regulated industries that need bring-your-own-keys, private networking, and custom audit retention without operating the platform themselves.
Adds customer-managed encryption keys, region-locked data residency, and engagement-scoped SLAs on top of the multi-tenant compliance baseline.
Customer cloud
Reign deployed into your own cloud account, inside your VPC, behind your firewall rules, governed by your IAM. Data never crosses your network boundary.
Large enterprises and government-adjacent organizations with strict data residency requirements, internal cloud landing zones, and existing security baselines they will not exit.
ISO 27001 closed-system classification, EU and regional data residency guarantees, and full audit trail written to customer-owned storage.
Air-gapped
Reign installed on disconnected on-premise hardware. Zero egress. Offline model updates via secure transfer. Audit Ledger generated air-gapped.
Defense enterprises, classified AI programs, and sovereign national initiatives that cannot accept any external network dependency.
FIPS 140-2 Level 3 encryption, STIG-aligned audit logging, FedRAMP-aligned controls, and full sovereign operation of the trust layer.
Sovereignty principles
Four things the customer always owns.
Sovereignty is not a deployment option. It is the default. These four properties hold across every topology above.
Customer-owned keys
Encryption keys are generated, held, and rotated by the customer. iTmethods operates the platform without holding the keys to your data.
Customer-owned data
Prompts, completions, embeddings, and operational data live in storage you control, in the region you specify. Reign is the governance layer over your data, not a destination for it.
Customer-owned models
Bring your own foundation models, fine-tunes, and validated artifacts. Reign governs how they are invoked. Model weights remain yours.
Customer-owned audit trail
The Audit Ledger writes tamper-evident records to customer-owned storage. Submission-ready packages are generated on demand, owned by the customer, portable by design.
Reign governs what runs. Forge runs what Reign governs.
The same trust boundary that contains Reign also contains the AI substrate that executes inside it. One sovereign deployment posture. Two coordinated platforms.