In a dedicated, single-tenant instance, on Reign Dedicated or in your own AWS or Azure account. Air-gapped and sovereign deployment are supported.

Is anything shared with other customers?

No. There is no multi-tenant option and no shared SaaS edition. Single-tenant is the model, wherever the instance runs.

Whose models, accounts and keys?

Yours. Frontier, your own or open-weight models, on your own accounts and keys. You can swap models without changing how the work is governed.

Who at the vendor can get in?

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

What is written down before we start?

The deployment record. Where it will run, where your data and records will be held, and who is responsible for operating each part, agreed and documented before Reign is deployed.

Where is the record kept?

With you. Every change lands in your repository for your team to approve. Every governed call is recorded in storage you own.

Across the stack

Holding the asset is one job. Checking the work is another.

The questions now asked of every AI vendor are about control: where it runs, whose models and keys, who can get in. Here is how Reign answers each one, and where we publish it. Then the question most stop before: who holds the record.

Book a briefing See deployment options

Ask us

The questions, and the page that answers each one.

Q01
Where will it run?
In a dedicated, single-tenant instance, on Reign Dedicated or in your own AWS or Azure account. Air-gapped and sovereign deployment are supported.
Published on Deployment →
Q02
Is anything shared with other customers?
No. There is no multi-tenant option and no shared SaaS edition. Single-tenant is the model, wherever the instance runs.
Published on Deployment: what is not on offer →
Q03
Whose models, accounts and keys?
Yours. Frontier, your own or open-weight models, on your own accounts and keys. You can swap models without changing how the work is governed.
Published on Reign Gateway →
Q04
Who at the vendor can get in?
Named people. Named iTmethods operations staff hold administrative access to run the platform. Their names are recorded, and access is reviewed.
Published on Deployment: administrative access →
Q05
What is written down before we start?
The deployment record. Where it will run, where your data and records will be held, and who is responsible for operating each part, agreed and documented before Reign is deployed.
Published on Deployment: the deployment record →
Q06
Checking the work
Where is the record kept?
With you. Every change lands in your repository for your team to approve. Every governed call is recorded in storage you own.
Published on Reign Factory → and Reign Gateway →

On 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.

Across the stack

Runs on the stack you already have.

Sovereignty is a deployment property, not a separate product. Where it runs changes; how the work is governed does not. The same answers hold for Reign Factory, Reign Gateway and Reign Ops.

The argument, at length.

Next step

Bring the infrastructure and jurisdiction you need to preserve.

We will walk through the supported deployment model and the parts that sit inside and outside your boundary.