Jurisdiction
Country, legal entity, operator, customer eligibility, and workload restrictions.
Regions
A region is an evidence record, not a dot on a map
Every Talvium region will publish its operator, legal entity, lifecycle, eligible customers, service inventory, residency and access model, key options, connectivity, assurance scope, and infrastructure evidence.
No production region represented as live
Site 01candidate diligence
Node AU.S. pilot design
Node Bselection pending
Evidence matrix
Current planning record
| Record | Purpose | Lifecycle | What is verified now |
|---|---|---|---|
| Africa Site 01 | Candidate physical anchor for a future secure compute node | Diligence | Management-reported access to approximately 4,000 acres in Africa; documentary and technical validation pending |
| Pilot Node A | Controlled U.S. endpoint for an unclassified federation demonstration | Design | Architecture intent only; site and capacity not published |
| Pilot Node B | Second eligible endpoint for denial and recovery testing | Selection pending | No geography committed |
Capability set
Required region record
Data & keys
Storage, processing, backup, support, operator access, HSM, and customer key options.
Capacity
Compute class, accelerator, storage, quantity, delivery window, and service lifecycle.
Connectivity
Carriers, private links, latency bands, edge relationships, and dependencies.
Assurance
Exact claims, issuer, boundary, dates, documents, and shared responsibility.
Infrastructure
Power, battery, water, cooling, materials, measurement, and exceptions.
Next decision
Availability must be generated from one record
Product pages, region pages, environment comparisons, pricing, and sales routing should never disagree.