Where Reign runs. Always inside your trust boundary.
Where the data sits matters, and Reign meets whatever your residency and regulatory obligations require. What matters next is whether you can prove what the system did. Same governance layer, same evidence, across every topology.
Topologies
Three 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 three. There is no multi-tenant option.
Hosted dedicated
Reign operated by iTmethods in a single-tenant environment with dedicated compute, storage, and network on AWS, Azure, GCP, or NVIDIA DGX Cloud, connected securely to your trust boundary.
Established AI programs in regulated industries that need bring-your-own-keys, private networking, and custom audit retention without operating the platform themselves.
Customer-managed encryption keys, region-locked data residency, and engagement-scoped SLAs. Supports SOC 2 Type II, ISO 27001, NIST AI RMF, GDPR, and EU AI Act obligations.
Customer cloud
Reign deployed and managed inside 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 national initiatives that cannot accept any external network dependency.
FIPS 140-2 Level 3 encryption, STIG-aligned audit logging, and FedRAMP-aligned controls, with the trust layer operated entirely inside the enclave.
Ownership and proof
Four things the customer always owns.
Sovereignty is necessary. It is not sufficient. Ownership of a layer is a commercial arrangement. Proof of an action is an artefact. These four properties hold across every topology above, and the Audit Ledger is what turns them into evidence an examiner will accept.
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.