Reign · Deployment

Where Reign runs.

Choose the supported deployment model that fits your infrastructure.

Book a briefing Product status → How Reign keeps it yours →

Deployment model	Availability	What it is
Reign Dedicated	Available today	A dedicated instance hosted and 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 and sovereign deployment are supported. Google Cloud is planned for 2027.

Single tenancy

What single-tenant means in practice.

Every Reign deployment uses the same operating model: a dedicated single-tenant instance for one customer. Each instance’s application tier, database and workload plane are dedicated to that customer. The application, data stores and pipeline tooling belong to the instance.

01Identity and access

Credentials, identity configuration and access rules are specific to and held inside the instance.

02Configuration and policy

Each instance has its own configuration and policy.

03Upgrades

Upgrades are applied to the instance on an agreed schedule.

04Administrative access

Named iTmethods operations staff hold administrative access to run the platform. Their names are recorded, and access is reviewed.

Limits

What is not on offer.

01No multi-tenant, no shared SaaS

There is no multi-tenant option and no shared SaaS edition. Those models are not on a roadmap. Single-tenant is the model, wherever the instance runs.

02The tooling we name

iTmethods operates the source control and delivery tooling in scope inside the instance, including GitLab, GitHub Enterprise Server and Bitbucket Data Center. That is the tooling we run, and it is named here because we run it, not as an endorsement of anything else.

03On security language

A dedicated instance is a boundary we operate and record. It is not a guarantee about risk, and we will not describe it as one.

Deployment boundary

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.

Reign DedicatedHosted and operated by iTmethods

Dedicated single-tenant instance

Application tier
Database
Workload plane

Customer AWS or Azure accountThe same instance, operated under the documented responsibility model

Dedicated single-tenant instance

Application tier
Database
Workload plane

The deployment recordNames the selected infrastructure model, application and data boundary, access, telemetry and administrative responsibilities.

One customer, one instance, in either placement. The customer’s risk function assesses what that instance boundary means in its environment.

The infrastructure, data location and boundary

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.

Security and trust →Reign Factory →Reign Gateway →Reign Ops →

Next step

Let’s discuss your deployment requirements.

iTmethods was founded in 2005 and has two decades of experience operating enterprise infrastructure for regulated industries. 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.

Book a briefing