- Boundaries
- Customer-defined Permitted ingress and egress paths defined by the customer, enforced at the network and routing layer.
- Jurisdiction
- In-region scope Cluster, control plane and operations placed inside the customer's jurisdiction from initial deployment.
- Keys
- Customer-held Customer holds encryption key ownership throughout the deployment lifecycle.
- Audit
- Evidence on demand Access trails, change records and review logs surfaced on demand, not on a quarterly reporting cycle.
- Posture
- Public · Private · Air-gapped Three postures, deployable alone or combined inside a single sovereign programme.
- Operations
- In-region, vetted Smart-hands and NOC staff based in-jurisdiction, vetted to customer-defined clearance requirements.