Where Reign runs.
Choose the supported deployment model that fits your infrastructure.
| Deployment model | Availability | What it is |
|---|---|---|
| iTmethods-operated infrastructure | Available today | A dedicated instance operated by iTmethods. |
| Customer AWS or Azure account | Available today | The same dedicated instance in the customer’s cloud account, operated under the documented responsibility model. |
Air-gapped deployment is supported for isolated or offline operation. Sovereign deployment is supported for the agreed jurisdictional, data-location and operating requirements. Google Cloud is planned for 2027.
Operator experience behind each deployment.
Founded in 2005, iTmethods has twenty-one years of experience operating enterprise infrastructure for regulated industries.
That experience informs how the deployment boundary and operating responsibilities are defined and recorded. The sections below set out what that means in practice.
What single-tenant means in practice.
Every Reign deployment uses the same operating model: a dedicated single-tenant instance for one customer.
Its application tier, database and workload plane are dedicated to that customer. The application, data stores and pipeline tooling belong to the instance, and iTmethods operates GitLab and the surrounding delivery tooling inside it.
Single tenancy is the only operating model, wherever the instance runs.
What is not on offer.
What the deployment record sets out.
Before Reign is deployed, we agree and document where it will run, where your data and records will be held, and who is responsible for operating each part.
Where Reign runs
The deployment record identifies the selected infrastructure, data location, and the application and data boundary for your instance.
Who operates what
It sets out the responsibilities of iTmethods and your teams, including identity and administrative access, the operational information needed to support the service, and the decisions that remain with you.
Named iTmethods operations staff hold administrative access to run the platform. Their names are recorded, and access is reviewed.
Let’s discuss your deployment requirements.
Bring the infrastructure, jurisdictional constraints and operating responsibilities you need to preserve. We will walk through the supported deployment model and the parts that sit inside and outside your boundary.