Environments
Select the control boundary before the service catalog
Talvium uses five deployment environments to make the tradeoffs among service breadth, jurisdiction, isolation, operator control, connectivity, cost, and time to provision visible.
Selection framework
5deployment environments
Differentcatalog by boundary
Expliciteligibility
Evidence matrix
Environment comparison
| Environment | Control pattern | Best fit | Status |
|---|---|---|---|
| Global Compute | Regional selection; Logical isolation; Customer-managed key options | Enterprise development, public data, and portable applications. | Planned |
| Sovereign Region | Defined processing geography; Operator-access policy; Jurisdiction control map | Public-sector and regulated workloads with residency obligations. | Planned |
| Secure Enclave | Private network boundary; Attested compute; Enhanced decision logging | Sensitive collaboration, protected analytics, and confidential inference. | Reference design |
| Private / National | Dedicated infrastructure; Local operating authority; Independent governance | National platforms, critical programs, and tightly governed private estates. | Partner model |
| Disconnected Edge | Local identity cache; Signed updates; Controlled synchronization | Field operations, remote infrastructure, and offline mission workflows. | Reference design |
Next decision
No service parity is implied
Each product page and region record must publish current environment eligibility. A roadmap label is not availability.