Question 1

Why did iTmethods rebrand?

Accepted Answer

Reign is the platform name for what iTmethods previously shipped as Forge. The rename reflects a change in scope, not a change in supplier. The platform now spans four motions rather than one. Operate is Reign Ops, available today. Build is Reign Factory, in beta and being productized. Govern is Reign Gateway, available today. Assure is Reign Assurance, in co-design development. One name across the four makes it clear which motion a customer is buying and which is not yet available. The category we build for is Continuous Agentic Assurance. iTmethods Inc. remains the contracting entity throughout.

Question 2

What is the iTmethods platform?

Accepted Answer

Reign is the iTmethods platform for Continuous Agentic Assurance in regulated industries. It has four motions. Operate is Reign Ops, available today. Build is Reign Factory, in beta and being productized. Govern is Reign Gateway, available today. Assure is Reign Assurance, in co-design development. Reign Ops and Reign Gateway can be bought today. Reign Factory and Reign Assurance cannot. iTmethods Inc. is the company that builds and operates the platform.

Question 3

When did the rebrand happen?

Accepted Answer

Reign is the current platform name for what iTmethods previously shipped as Forge. The name is in use now, across the product, the documentation and the contracts written from here. We do not publish a rebrand date on this page, because the date that matters to a customer is the date their own records change, and that is theirs to set. Nothing about your service, your contract or your counterparty turned on a particular day. iTmethods Inc. has been the contracting entity throughout.

Question 4

Is iTmethods being acquired or changing ownership?

Accepted Answer

No. iTmethods Inc. remains an independent, founder-led company. Paul Goldman remains Founder and Chief Executive Officer. There is no change of ownership, control, or contracting entity. The rebrand changes the name of the platform and nothing about who you are contracted with.

Question 5

What is iTmethods Inc.?

Accepted Answer

iTmethods Inc. is the legal entity, and the rebrand does not change it. Reign is the platform brand that iTmethods Inc. builds and operates. Contracts, invoices, attestations and legal relationships continue to sit with iTmethods Inc. No novation, no assignment and no new counterparty is involved in a change of product name.

Question 6

How should I refer to your company?

Accepted Answer

Call the company iTmethods, cased exactly so. Call the platform Reign. Name the motion when it matters: Reign Ops for Operate and Reign Gateway for Govern, both available today, Reign Factory for Build, which is in beta and being productized, and Reign Assurance for Assure, which is in co-design development. The category we work in is Continuous Agentic Assurance. Forge is the retired name for Reign Ops and should not be used as a current product name.

Question 7

Does anything change with my service?

Accepted Answer

No. A rename does not change what you have contracted for. Your contract remains in force on its existing terms with iTmethods Inc., and the service you are running is the same service under a new name. Anything that would change scope, commercial terms or service levels happens through the contract and is agreed in writing. It does not happen through a rebrand. Production SLAs are documented per engagement and reviewed quarterly. SLA targets, incident history, and remediation procedures are available under NDA.

Question 8

Do I need to sign a new contract?

Accepted Answer

No. Your existing contract remains valid, because the counterparty has not changed. iTmethods Inc. is still the contracting entity. If a naming reference needs to be updated for your own records, that is handled as a written amendment at renewal. Nothing about the rename requires you to reopen commercial terms.

Question 9

Will my costs change due to the rebrand?

Accepted Answer

No. The rebrand does not change any commercial term. Your pricing is set by your contract and can only change in the way your contract says it changes. We do not publish pricing on this page, and a change of name is not a change of price.

Question 10

Do I need to update anything on my end?

Accepted Answer

No action is required. The rename does not invalidate a purchase order, a vendor record or a signed agreement, because the contracting entity, iTmethods Inc., has not changed. When you next update vendor records in the ordinary course, the company is iTmethods, the platform is Reign, and the product you operate is Reign Ops.

Question 11

What if my team still uses the old product name?

Accepted Answer

That is not a problem. Forge and Reign Ops name the same platform, and older internal identifiers such as iTmethodsONE refer to the same service under the same contract. Nothing in your environment depends on which name your team uses. We use Reign Ops in current documentation so that there is one current name.

Question 12

Will my invoices change?

Accepted Answer

Invoices continue to come from iTmethods Inc., and payment terms are set by your contract rather than by the product name printed on the invoice. If the descriptor on an invoice changes to match the current product name, the amount, the terms and the counterparty do not change with it.

Question 13

Will my account manager change?

Accepted Answer

The rebrand does not reassign accounts. Named contacts and support arrangements are set by your contract and are not altered by a change of product name. If your account contacts change for an ordinary business reason, we tell you directly rather than through a rebrand.

Question 14

How do I explain this rebrand to my internal stakeholders?

Accepted Answer

Use this. iTmethods has renamed its platform to Reign. The product we operate is Reign Ops. The contracting entity, iTmethods Inc., is unchanged, so our agreement, our purchase order and our vendor record stand as signed. Any change to scope or commercial terms would reach us in writing through the contract, not through a change of name.

Question 15

Are there any new certifications or compliance changes?

Accepted Answer

No. The rebrand does not change the entity that holds attestations or the programs behind them. iTmethods Inc. holds a SOC 2 Type II attestation, and its scope covers Reign Ops. Reign Gateway, Reign Factory and Reign Assurance are not in scope of it. Current attestation and certification status is provided on request under non-disclosure. We hold no FedRAMP authorization and make no FedRAMP claim of any kind, including alignment claims. Reign does not make a customer compliant, certified, validated or qualified. It produces the evidence that a customer's own compliance function uses.

Question 16

Will the portal URL change?

Accepted Answer

The portal remains at portal.itmethods.com. If we introduce an additional hostname under the Reign name, existing bookmarks and integrations get notice and a migration window before anything changes. We do not promise a URL forever on this page, and we do not change one without telling you first.

Question 17

How long has iTmethods been in business?

Accepted Answer

iTmethods Inc. has run enterprise DevOps and platform infrastructure for regulated organizations since well before the Reign name existed, under the same founder and the same legal entity. We do not publish a tenure figure on this page rather than round one into a marketing number. Corporate registration details and customer references are provided on request under non-disclosure.

Question 18

Who leads iTmethods?

Accepted Answer

Paul Goldman is the Founder & CEO of iTmethods. The company remains founder-led with a focus on sustainable growth and customer-first values.

Question 19

What industries does iTmethods serve?

Accepted Answer

iTmethods serves regulated industries, principally healthcare, financial services, government, life sciences and enterprise technology. Our products are built for organizations where security, compliance and data sovereignty are not negotiable.

Question 20

Where can I learn more about the rebrand?

Accepted Answer

Visit itmethods.com. For anything specific to your account, contact your account team or write to contact@itmethods.com. Questions about attestations, service levels or commercial terms are answered under non-disclosure rather than on this page.

Question 21

What is Reign Ops?

Accepted Answer

Reign Ops is the Operate motion of Reign. Available today. iTmethods runs the delivery toolchain for regulated enterprises, including source control, build, artifact management and code quality, as one managed environment with change control, access control and a recorded history of who did what and when. Deployment is a single-tenant dedicated instance. Governance of model access sits in a separate motion, Reign Gateway, which is also available today. Reign Ops is an operating service, not a compliance outcome. Whether your obligations are met is a determination for your own risk and quality functions.

Question 22

How does Reign Ops differ from iTmethodsONE?

Accepted Answer

Reign Ops is iTmethodsONE under a new name. Same platform, same team, same agreements. It was also called Forge for a period. Forge and iTmethodsONE both mean Reign Ops, and Reign Ops is the only current name. Your existing tools, configurations, workflows, service levels, support routes and invoices are unchanged, and nothing is being added to your service because a name changed. Governance of model access is a separate motion, Reign Gateway. If you changed nothing at all after reading this, you would be doing the right thing.

Question 23

What tools are included in Reign Ops?

Accepted Answer

Reign Ops operates the delivery toolchain as one managed environment. Typical estates include GitLab, GitHub Enterprise, Bitbucket, the Atlassian suite (Jira Software, Jira Service Management, Confluence), Jenkins, JFrog Artifactory, Nexus, SonarQube, Terraform and Plane. We do not publish a tool count, because the count is not the thing you are buying. The exact set is scoped per engagement and written into the agreement rather than assumed. These tools are named because we operate them, not as an endorsement and not as a claim of any partnership tier.

Question 24

What is the Reign AI Gateway?

Accepted Answer

Reign Gateway is the Govern motion of Reign. Available today. Model calls run through it rather than around it, so access is set by policy before the call and recorded after it. The record covers the request, the policy decision applied, the model and version invoked, the destination, the response and the identity that initiated it. Calls that fall outside policy are refused at the boundary, and the refusal is recorded with the same detail as an allowed call. This is enforcement with evidence. It is not a claim that every route in an enterprise passes through it on day one.

Question 25

What is MCP and why does it matter?

Accepted Answer

MCP, the Model Context Protocol, is an open standard for connecting AI systems to enterprise data and tools. It matters for one reason. Every MCP server an agent can reach is a route into an enterprise system, and a route with no policy in front of it and no record behind it is an ungoverned one. Reign Gateway treats MCP traffic the way it treats any model call. Policy is applied before the call, a record is written after it, and refusals are recorded. That holds whether the MCP server is operated by you, by us or by a third party.

Question 26

What deployment options does Reign Ops offer?

Accepted Answer

Two models are available today. A single-tenant dedicated instance, provisioned for one customer and serving that customer only, with no pooled application tier, no pooled database and no shared workload plane between customers, run either in infrastructure iTmethods operates or in your own cloud account on AWS or Azure. Google Cloud is planned for 2027. There is no multi-tenant option and no shared SaaS edition, and neither is on a roadmap. Air-gapped operation and sovereign deployment are in development. Neither is available today, neither is being sold, and we are not offering a date, because we do not have one worth publishing. If your requirement is one of those two, say so early and we will tell you plainly where the work stands.

Question 27

Does iTmethods hold SOC 2 Type II?

Accepted Answer

iTmethods Inc. holds a SOC 2 Type II attestation, and its scope covers Reign Ops. Reign Gateway, Reign Factory and Reign Assurance are not in scope of it. We do not state its scope on a public page, because scope is the part a reviewer has to read for themselves rather than take from a marketing sentence. Current attestation and certification status is provided on request under non-disclosure. Write to security@itmethods.com, saying which entity is asking and which regulator or internal standard is driving the question. Holding an attestation is a statement about iTmethods. It is not a statement that your use of the platform meets your obligations.

Question 28

How does Reign Ops relate to HIPAA?

Accepted Answer

HIPAA compliance is not something a platform holds on your behalf. It is a determination about your organization and your use of a system, made by your own privacy and compliance functions. What we do is design controls against the published expectations and record what actually happened, so that determination rests on evidence rather than on assertion. The categories of data in scope for an engagement, including any protected health information, are agreed and written into the agreement before work begins, together with what contractual instruments that requires. Current attestation and certification status is provided on request under non-disclosure. Alignment is not compliance, and we will not describe it as compliance.

Question 29

Does iTmethods hold any FedRAMP status?

Accepted Answer

No. iTmethods holds no FedRAMP status of any kind, in any tense. There is no authorization, no listing and no readiness designation, and we will not describe ourselves as having one. We design our controls against published expectations, which is a statement about design rather than a status granted by anybody. If your workload requires a service carrying a federal authorization, Reign is not that service today. Current attestation and certification status is provided on request under non-disclosure.

Question 30

How fast can I get started with Reign Ops?

Accepted Answer

We do not publish implementation durations. How long it takes to stand up a single-tenant dedicated instance depends on your identity provider, your network approvals and the scope of the estate coming across, and a number quoted before those are known would be invented rather than estimated. The timeline is scoped and agreed in writing at the start of the engagement, with named owners on both sides. Air-gapped and sovereign deployments are in development, are not available and carry no date.

Question 31

Does Reign Ops support SSO?

Accepted Answer

Yes. Reign Ops supports enterprise single sign-on through SAML 2.0 and OIDC, and integrates with identity providers that implement those standards, including Okta, Microsoft Entra ID, Ping Identity and OneLogin. Identity configuration, credentials and access rules are specific to your instance and are not inherited from a shared default that other customers also carry. Your provider and the exact configuration are confirmed during scoping and recorded in the deployment record for your instance.

Question 32

What SLA does Reign Ops provide?

Accepted Answer

We do not publish service level numbers on this page. A target quoted without knowing the scope it covers is marketing rather than a commitment. Service levels are agreed per engagement and written into the agreement. Targets, incident handling and remediation are provided on request under non-disclosure. Existing customers keep the levels they have already agreed. Those stand exactly as written and are not restated, reinterpreted or replaced by a change of name.

Question 33

Can I migrate from my current DevOps tools to Reign Ops?

Accepted Answer

Yes. Migration is a normal part of an engagement, and iTmethods has moved enterprises off self-managed Jira, Jenkins, GitHub Enterprise and comparable estates onto tooling we operate. We do not promise zero downtime. What we do is agree the cutover window, the rollback path and the acceptance criteria in writing before anything moves, and record what happened at each step so it can be read back later. Migration is scoped as professional services alongside the operating service, and that scope is written into the agreement.

Question 34

Does Reign Ops include Atlassian tools?

Accepted Answer

Yes. Reign Ops operates the Atlassian suite, including Jira Software, Jira Service Management, Confluence and Bitbucket, inside a single-tenant dedicated instance. Upgrades, patching and configuration are applied to that instance on an agreed schedule under the change process, rather than to everyone at once. Licensing arrangements are settled in the agreement rather than assumed here. Atlassian is named because we operate it, not as a claim of any partnership tier.

Question 35

Can I use Reign Ops with GitHub?

Accepted Answer

Yes. Reign Ops operates GitHub Enterprise Server inside the single-tenant dedicated instance we run for you, or integrates with a GitHub Enterprise Server deployment you already run. Be precise about where that instance sits. It runs in infrastructure iTmethods operates, or in your own cloud account on AWS or Azure. Both are available today, and Google Cloud is planned for 2027. Which components sit inside which boundary is written into the deployment record for your instance rather than left to a general statement on a website.

Question 36

What AI models does Reign support?

Accepted Answer

Model access runs through Reign Gateway. It supports the major commercial providers, including OpenAI, Anthropic, Google, Amazon Bedrock and Azure OpenAI, and it supports models you host yourself. The list is not the point. The point is that whichever model is called, the call is subject to policy before it is made and leaves a record afterwards covering the model and version invoked, the destination, the response and the identity that initiated it. Which models are enabled for your instance is set by your policy, not by us.

Question 37

How does Reign Ops handle security?

Accepted Answer

Data is encrypted at rest and in transit. The instance is single-tenant and network isolated, with no pooled application tier, no pooled database and no shared workload plane between customers. Access is role-based, privileged access is named and reviewed, and joiner and leaver handling is documented. Change reaches an instance as a merge request with named approvers on both sides, and the merge request is the record. Vulnerability scanning, monitoring and incident handling are described in the standard pack, including how and by whom you are notified. Platform hardening is designed against published benchmarks, which is a statement about design and not a certification. 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. Write to security@itmethods.com for the pack.

Question 38

Can I get dedicated support?

Accepted Answer

Support is provided by named people under the terms of your agreement, and escalation runs to the engineers who operate your instance rather than into a queue. We do not publish support tiers or response time guarantees on this page. What is committed is what is written into your agreement, and that is where to look. Existing customers keep the support address, ticket path, escalation ladder and people they use today. None of it changed with the name.

Question 39

How does Reign Ops integrate with CI/CD pipelines?

Accepted Answer

Reign Ops operates the pipeline tooling as part of the instance, typically Jenkins, GitLab CI or GitHub Actions runners, with artifact management in JFrog Artifactory or Nexus and code quality scanning in SonarQube. Pipelines run inside the single-tenant instance rather than on shared infrastructure. Pipeline, build and deployment telemetry, including job records, timings and outcomes, is retained so a reviewer can follow what ran, when, and on whose approval. Which of these you run, and how they are wired together, is scoped per engagement.

Question 40

What is Reign?

Accepted Answer

Reign is the iTmethods product line for building and operating AI work inside regulated environments. It is four motions at four different stages, not one product. Reign Ops operates the delivery platform and is Available today. Reign Factory builds, and is Available · Beta Release: it is not generally available, and beta access is agreed with us and scoped in writing. Reign Gateway governs what crosses to a model, and is Available today. Reign Assurance prepares evidence for the people who decide, and is Co-design development, which means it is not available, not sold and not shipping. The category we are establishing is Continuous Agentic Assurance.

Question 41

What problem does Reign solve?

Accepted Answer

Agents now act inside enterprises faster than anyone can reconstruct afterwards what was asked for, what a model was given, and who approved the result. Reign closes that gap in the operational path rather than after the fact. Reign Gateway applies policy where a request crosses to a model and records the crossing, including the refusals. Reign Ops operates the environment the work runs in. Reign Assurance is being designed to assemble that record for your own reviewers, and it is Co-design development, which means it is not available, not sold and not shipping. We do not publish a timeframe on this page, because a timeframe set before your scope is known would be invented.

Question 42

How quickly can Reign be deployed?

Accepted Answer

That depends on your environment, and we do not publish a number on this page rather than invent one. Reign runs as a single-tenant dedicated instance provisioned for one customer. What sets the timeline is your identity configuration, your network boundary, the repositories and systems in scope, and the reviewers who own them. We scope it with you under non-disclosure and tell you what it will take once we have seen the environment. If the honest answer at that point is longer than you wanted, that is the answer you will get.

Question 43

What AI platforms does Reign govern?

Accepted Answer

Reign Gateway is model-neutral. It sits where a request crosses to a model and applies the policy you set, so which providers and which model versions are permitted is configuration for your instance rather than a fixed list we publish. Commercial APIs, cloud-hosted models and models you host yourself are treated the same way: the crossing is decided against policy, and the request, the decision, the model and version, the destination, the response and the identity behind it are recorded. We do not claim to govern every route in an enterprise on day one. A route that does not pass through the Gateway is not governed by it, and finding those routes is part of the scoping work. Reign Gateway is Available today.

Question 44

How does Reign help prevent shadow AI?

Accepted Answer

Reign Gateway governs the routes that pass through it. It does not block the ones that do not, and we will not say otherwise. Authorised traffic is routed through the Gateway, where policy is applied at the model boundary and every crossing is recorded, including the refusals. Stopping traffic leaving by another path is work your existing controls do, usually network policy at the egress point or endpoint configuration, and it belongs to your security team rather than to us. What the Gateway gives that team is a tested record of what was requested and returned on the governed routes, which is the material you need in order to argue about the ungoverned ones. Reign Gateway is Available today.

Question 45

What policies can Reign enforce?

Accepted Answer

Reign Gateway decides, at the model boundary, whether a request may cross. Policy covers which models and versions may be reached, for which classes of work, carrying which categories of context, under which identity. Policy is configuration set for your instance by your people, not a default inherited from a shared template. A request that falls outside policy is refused at the boundary, and the refusal is recorded with the same detail as an allowed call, because a refusal that leaves no trace is not a control. We describe this as enforcement with evidence. We do not describe it as a guarantee that no mistake is possible.

Question 46

Does Reign support compliance reporting?

Accepted Answer

Reign produces evidence. It does not produce a compliance determination, and no supplier can. Reign Gateway records each crossing to a model: the request, the policy decision applied, the model and version invoked, the destination, the response and the identity that initiated it. Reign Ops records how the environment changed, by whom, and with whose approval. Reign Assurance is being designed to assemble that material into a form your own reviewers can interrogate, and it is Co-design development, which means it is not available, not sold and not shipping. Whether the result satisfies a given framework is a determination for your risk function and for accredited third parties. iTmethods makes no compliance, certification or accreditation claim under any framework. Current attestation and certification status is provided on request under non-disclosure.

Question 47

Can Reign control AI costs?

Accepted Answer

Reign Gateway records every crossing it handles, including the model and version invoked and the identity behind it, so spend on the governed routes can be attributed to a team, a system or a person rather than arriving as a single line on a provider invoice. Attribution is the part we do. Deciding what to do about it is yours. We do not publish figures for what a customer will find or save, because the only honest number is the one your own traffic produces, and you will have it once the Gateway is running.

Question 48

Can Reign Gateway be used without Reign Ops?

Accepted Answer

Yes. The motions stand up separately and Reign Gateway does not require Reign Ops. Gateway governs what crosses to a model. Ops operates the delivery platform the work runs on. A customer who wants only the model boundary governed takes Gateway. A customer who wants their delivery tooling operated takes Ops. Both are Available today. Where a customer runs both, the Gateway record and the change record from Ops describe the same work from two directions, which is more useful to a reviewer than either alone. Reign Factory is Available · Beta Release: it is not generally available, beta access is agreed with us, and it is not part of either.

Question 49

How does Reign protect sensitive data?

Accepted Answer

Reign Gateway decides what may be assembled into a request before that request crosses to a model. Which context is eligible is set by policy for your instance ahead of the call rather than negotiated during it, and a request that falls outside policy is refused at the boundary with the refusal recorded. Be clear about where the boundary is today. Reign runs as a single-tenant dedicated instance provisioned for one customer, in infrastructure iTmethods operates or in your own cloud account on AWS or Azure. Air-gapped deployment and sovereign deployment are in development. Neither is available, neither is being sold, and we do not offer a date. What sits inside and outside the boundary is written into the deployment record for your instance rather than left to a sentence on a website.

Question 50

What industries benefit most from Reign?

Accepted Answer

Reign is built for organizations where somebody has to answer for an action after it has been taken: financial services, life sciences, the public sector and defense, and technology companies operating under customer or regulatory obligation. The common feature is not the sector. It is that AI work touches something a reviewer will later ask about, and that a summary written afterwards by the people who did the work is not sufficient. Reign is designed against published regulatory expectations and maps its controls to them. That is alignment, not compliance. iTmethods makes no compliance, certification or accreditation claim under any framework, and the determination stays with your risk function.

Question 51

Do the four Reign motions work together?

Accepted Answer

Yes, and each one stands on its own. Reign Ops operates the delivery platform and is Available today. Reign Gateway governs what crosses to a model and is Available today. Reign Factory builds, is Available · Beta Release, and is not generally available; beta access is agreed with us. Reign Assurance is Co-design development, which means it is not available, not sold and not shipping. Where more than one motion is in place the records line up: the Gateway records the model boundary crossing, Ops records the change and the approval, and one population of work can be followed from request to merge. Adopting one motion does not commit you to another, and no motion is available because another one is.

Question 52

How is Reign different from enterprise DLP?

Accepted Answer

Data loss prevention asks what left the building. Reign Gateway asks a different question at a different point: may this request cross to this model, under this identity, carrying this context, and what is the record if it does. The decision is taken in the operational path before the call is made, and the refusal is recorded with the same detail as the permission. Data loss prevention is a control on data movement. The Gateway is a control on agent action. Most organizations that need one need the other as well, and we do not position the Gateway as a replacement for controls your security team already operates.

Question 53

Where can I learn more about Reign?

Accepted Answer

Product status is on /status, which states where each of the four motions actually stands and is the page that wins if any other page reads as more confident. Deployment models are on /deployment. Security, subprocessors and the standard procurement pack are on /security. We do not publish pricing, and there is no trial and no self-service signup, because every engagement is scoped under non-disclosure rather than sold from a page. To talk to the engineers who own the control rather than to a demonstration script, book a briefing or write to reign@itmethods.com.

Question 54

What is Reign for Life Sciences?

Accepted Answer

Reign for Life Sciences is Reign applied in a regulated life-sciences estate. It is not a separate product and it is not a scientific application. The motions are the same ones: Reign Ops operates the delivery toolchain and is Available today, Reign Gateway governs what crosses to a model and is Available today, Reign Factory is Available · Beta Release, and Reign Assurance is Co-design development and is neither available nor sold. What is specific to life sciences is what the record has to survive. Change to a system in scope for GxP is captured as it happens, with named reviewers and named approvers, in a form a validation process can read afterwards. iTmethods holds no life-sciences certification or accreditation and claims none.

Question 55

What does data sovereignty mean for AI in life sciences?

Accepted Answer

Sovereignty is a question about where data sits, who can reach it, and what is recorded when it moves. In life sciences it bites hardest on trial and patient data, on proprietary research, and on the record a validation process reads later. State it precisely rather than absolutely. Reign runs as a single-tenant dedicated instance, provisioned for one customer and serving that customer only, with no pooled application tier, no pooled database and no shared workload plane between customers. That instance runs in infrastructure iTmethods operates, or in your own cloud account on AWS or Azure. Air-gapped and sovereign deployments are in development, are not available and carry no date. Where a model is called, Reign Gateway records what was sent, which policy applied, and what came back. The categories of data in scope for an engagement are written into the agreement rather than assumed.

Question 56

How does Reign relate to FDA 21 CFR Part 11?

Accepted Answer

There is no such thing as an FDA-compliant platform. 21 CFR Part 11 sets expectations for electronic records and electronic signatures, and whether a computerised system in your estate meets them is decided by your quality function, not by a supplier. What Reign does is capture the record those expectations rest on. Who made a change, who reviewed it, who approved it and when, recorded as the work happens rather than reconstructed afterwards. Where a model took part in a change, the record says so. Reign Assurance arranges that record for a validation process and stops there. It does not perform validation and does not decide whether a system is validated. Reign prepares; people decide. iTmethods holds no certification, accreditation or approval under 21 CFR Part 11 and claims none. Alignment is not compliance.

Question 57

What does Reign do in a life sciences organization?

Accepted Answer

Reign operates the delivery estate and governs model access. It is not a scientific application. It does not discover drugs, analyze genomes or run trials. It sits underneath that work: the systems your teams build and change, and the AI those teams use to build and change them. Reign Ops operates the toolchain with change control, access control and a recorded history, and is available today. Reign Gateway governs which models may be called, by whom and with what context, records each call, and is available today. Reign Assurance arranges the resulting evidence for a validation process; it is in co-design development, is not available and is not sold. Where a system in your estate is in scope for GxP, the value is that its change history was captured as the work happened rather than assembled afterwards.

Question 58

How is Reign for Life Sciences deployed?

Accepted Answer

Two models are available today. A single-tenant dedicated instance, provisioned for one customer and serving that customer only. It runs in infrastructure iTmethods operates or in your own cloud account on AWS or Azure, with Google Cloud planned for 2027. It does not run on your premises. Air-gapped operation and sovereign deployment are in development. Neither is available, neither is being sold, and neither carries a date. There is no multi-tenant option and no shared SaaS edition, and neither is on a roadmap. We publish no implementation duration. The timeline is scoped and agreed in writing once the estate and the data categories in scope are known.

Question 59

How is a regulated implementation planned?

Accepted Answer

It is scoped and agreed in advance, in writing, before anything is built. The plan names the systems in scope, the categories of data involved, the environments, the reviewers and approvers on both sides, and what has to be true at each stage before the next one starts. We do not publish an implementation duration, because the length is set by the estate and by your own quality and change processes, and a number quoted before those are known would be a commitment nobody could stand behind. Once the scope is agreed the timeline is agreed with it, and it goes in the statement of work rather than on a web page. iTmethods does not perform validation. Your quality function owns that, and what we provide is the record it reads.

Question 60

Can we run our own models?

Accepted Answer

Yes. Reign Gateway governs access to commercial models and to models you host yourself, including models you have trained or fine-tuned. Which models are enabled is set by your policy. Whichever is called, the call is subject to policy before it is made and leaves a record afterwards covering the model and version invoked, the destination, the response and the identity that initiated it. Hosting a model yourself changes where the call goes. It does not remove the need for the record, and it does not by itself answer a sovereignty requirement; deployment of the instance is the part that does, and that is a single-tenant dedicated instance today.

Question 61

How does Reign for Life Sciences handle patient data?

Accepted Answer

Patient data is a category that has to be named before it is handled, not assumed. The categories of patient, trial and personal data in scope for an engagement are agreed and written into the agreement before work begins. Inside the instance, data is encrypted at rest and in transit, access is role-based, privileged access is named and reviewed, and access is recorded. Where a model is called, what may cross the boundary is set by policy before the call and recorded by Reign Gateway afterwards. If your policy enables a commercial model provider, calls to it leave your instance, and the record says so. If that is not acceptable for a given category of data, the policy is where you say so, and it is enforced at the boundary rather than by convention. iTmethods makes no claim to hold HIPAA compliance. Whether an engagement meets your obligations is a determination for your privacy function.

Question 62

Do you work with early stage biotech, or only large pharma?

Accepted Answer

Both. The determining factor is not headcount. It is whether you have systems and data in scope that need a controlled record, and small organizations often carry that obligation earlier than they expect. We do not publish pricing on this site, and commercial terms are scoped per engagement. The useful starting point is a briefing where you tell us which systems are in scope and which categories of data are involved, and we show you what the record looks like at the end of a real population of work.

Question 63

How is this different from using AWS or Azure directly?

Accepted Answer

It is not a competing cloud. Reign runs on cloud infrastructure, and iTmethods is an AWS Partner at Advanced Tier Services. The difference is what sits on top. A cloud provider gives you primitives: identity, keys, logs, a guardrail service. Reign is the layer that applies policy to a model call before it is made, records the call afterwards, and ties both to the change a named person approved in the delivery toolchain. Deployment is a single-tenant dedicated instance rather than a shared service. We make no statement about how any other provider architects its services, and we do not guarantee a regulatory outcome. That determination belongs to your quality and risk functions.

Question 64

Can Reign help with a regulatory submission?

Accepted Answer

Indirectly, and the distinction matters more here than anywhere else. We do not prepare submissions, do not advise on them, and hold no standing with any regulator. Where a computerised system is involved, what a submission rests on is evidence that the system was built, changed and approved in a controlled way. Reign captures that as the work happens: who changed what, who reviewed it, who approved it and when, and where a model took part in a change, that it took part. Reign Assurance arranges that evidence into a form a reviewer can work through. It is in co-design development, is not available and is not sold. Nothing iTmethods provides is a validated system, and we will not describe it as one. Your quality function owns the validation.

Frequently Asked Questions

Popular Questions