/ environments
Start where you are.Move when you are ready.
Seven environments, from a first look on a developer's machine to a controlled deployment inside your own boundary. What changes is commitment, governance and operational responsibility — not what Inferrex is.
/ the progression
Explore → Validate → Prepare → Deploy → Scale → Sovereign.
Each environment answers the same three questions: who it is for, what becomes possible there, and what it asks of you operationally. Nothing here is a gate on capability. You move because the work has moved, not because a feature was withheld.
Development
For developers and teams evaluating Inferrex. Point it at an API or a system, watch it discover structure and meaning, and work against InferrexAPI, InferrexSDK, InferrexMCP and InferrexCLI. Self-directed, no scoping call. **Next step: start in Development.**
QA / SIT
For teams validating integrations and workflows before wider testing. The understanding built in Development becomes something a test suite can rely on, with system integration exercised end to end rather than per pair.
UAT
For organisations preparing understood systems and relationships for business acceptance. The people who will sign it off can see what was inferred, what was reconciled and what it now means.
Staging
For production readiness: deployment preparation, dry runs and final validation against the shape of the real estate rather than a sample of it.
Production
For live operational workloads and production integrations, where a change upstream is something the platform notices and heals rather than something a person discovers from a failed job.
Enterprise
For larger technology estates, multiple teams, advanced deployment requirements and an enterprise operating model. The question stops being "does it work" and becomes "who owns it, and how is it governed".
Sovereign
For organisations that must operate inside their own boundary: controlled, self-managed or fully air-gapped, with the platform components required to run without reaching out.
/ what changes
The capability does not narrow as you move up.
The progression is not a ladder of features. The core of what Inferrex does — comprehend a system, reconcile it against everything else it knows, and make the understanding reusable — is the same in Development as it is inside an air-gapped boundary.
What increases is everything around it.
Environment maturity
From a machine you can break freely to one other people depend on.
Deployment commitment
From hosted and immediate to dedicated, controlled or isolated.
Operational responsibility
Who runs it, who is on call, and who owns the upgrade path.
Scale
One system, then an estate, then several estates and the teams that own them.
Governance
Evidence, approval and audit as requirements rather than as good practice.
Sovereignty
Where the data sits, where inference happens, and whose boundary decides.
Why the strictest environments get the whole platform
/deploy covers the operating models — hosted, private, sovereign and air-gapped — in more detail./ deliberately absent
No numbers, and that is a decision rather than an omission.
Inferrex publishes no rate card. There are no monetary values on this page, no per-system or per-relationship figures, and no commercial model described anywhere on this site. Beta is the only public entry route, and it starts in Development.
That is not evasiveness about cost. It is that the shape of a commercial conversation for an estate nobody has looked at yet would be a guess, and a published guess is worse than no number: it anchors both sides to something neither has evidence for. The environment you need is knowable from your systems and your constraints. What it costs follows from that conversation, not from a table.
Start in Development. Move when the work moves.
Nothing here requires a conversation to begin. When one is useful, it starts from what Inferrex already understands about your systems rather than from a form.