/ platform · deploy
Two decisions, not one.
Where the infrastructure runs and how far along it is are separate questions. Conflating them is how deployment conversations stall.
/ where it runs
Four topologies.
Cloud
Inferrex-operated, multi-tenant, with regional data residency.
Enterprise
Deployed into your own cloud tenancy, under your controls.
Sovereign
Deployed inside your jurisdictional boundary, with inference local to it.
Air-gapped
No egress. Comprehension and inference run entirely within the boundary.
/ environment maturity
Seven environments.
Development
Building against the platform.
QA / SIT
Interface and integration testing.
UAT
Acceptance against defined criteria.
Staging
Production-equivalent rehearsal.
Production
Live operation.
Enterprise
Production under enterprise operational commitments.
Sovereign
Production under sovereign and regulatory constraints.
/ the point
The two are chosen independently.
Environment maturity determines operational commitment. Deployment topology determines where the infrastructure runs.
A sovereign topology can run a development environment. A cloud topology can run production. The commitments attached to each are set separately, which is why the two questions are asked separately. Environments covers the progression in full.
Tell us where and how it has to run.
The deployment model should not change what Inferrex is.