Four motions. Four different stages.
Reign is not one product at one level of maturity. One motion is operating today. One is being productized while it runs. One is in production as a governed path. One is in co-design and is not available. This page exists so that nobody has to guess which is which.
The four motionsWhat we holdHow a chip moves
If a page elsewhere on this site reads as more confident than this one, this one is correct.
Where each one actually stands.
Status chip, what the status means in practice, and what it does not mean.
| Motion | Status | What this means in practice | What it does not mean |
|---|---|---|---|
| Reign Ops · Operate | Available today | This is the work iTmethods has been doing for twenty-one years. We operate delivery tooling, including GitLab, for regulated enterprises. There are named people, an agreed change process, and a service that runs whether or not anything else on this page ever ships. | It does not mean the other three motions are available because this one is. |
| Reign Factory · Build | Available · Beta Release | It is running, on real work, in beta. We are turning what works into a product while it runs, which is slower than announcing it and more honest than pretending the packaging is finished. | It is not generally available. Beta access is agreed with us and scoped in writing before anything runs. |
| Reign Gateway · Govern | Available today | The governed path is in production. Model access, policy and the record of what was requested and returned run through it rather than around it. | Being in production is a statement about the component running, not a claim that governance is solved or that every route in an enterprise passes through it on day one. |
| Reign Assurance · Assure | Co-design development | It is being designed with a small number of customers, on scope agreed per engagement and written down before anything starts, including how long it runs. The effort follows from the scope, and the commercial relationship follows from the effort. The concept is Continuous Agentic Assurance. The model, a demonstration on synthetic data, and a verifiable evidence package exist. None of it has run against a customer’s work. | It is not available, not sold, and not shipping. iTmethods does not issue an audit opinion or certification. Reign prepares; people decide. |
One attestation, named, and nothing else claimed.
The register covers claims as well as stages. This is the only assurance artifact iTmethods asserts anywhere on this site.
Reign Ops holds a SOC 2 Type II attestation. The report — its scope, its period and the firm that issued it — is released on request under non-disclosure, because the scope is the part that decides whether it answers your question and a badge does not carry scope.
It does not extend to Reign Gateway, Reign Factory or Reign Assurance. A SOC 2 Type II is an attestation report issued by a CPA firm, not a certification, and whether it satisfies a given buyer is their determination rather than a claim we make for them.
No ISO/IEC 27001, no ISO/IEC 42001, no FedRAMP authorization, no HIPAA attestation, and no standing under any framework named elsewhere on this site. Naming a framework is not a claim of standing under it.
The process, the standard pack and the route to ask are on security and trust. The report itself is released under non-disclosure, with its scope and its period.
How a motion moves to the next stage.
Status here is a description of the current state, not a forecast. These are the conditions that have to be true before we change a chip.
No dates. We do not publish target dates for movement between stages. A date we cannot stand behind is worse than no date at all.
Ask about the stage, not the story.
Tell us which motion matters to you and we will tell you exactly what stands behind it today. If the answer is that it is not ready, that is the answer you will get.