Residency (Pillar 03)
Where does it really live? — The third of the five pillars, and the only one most vendors answer. Asks where data physically sits — and, more usefully, whether you can prove it. SkyeConnex treats residency as one input to placement policy, enforced per file and evidenced in the custody record.
The question
This is where sovereignty theatre lives: a flag on the marketing page while the keys, the custody and the control sit elsewhere. Residency answers one question out of five.
The architectural answer
Placement policy is set per jurisdiction and enforced at upload. SkyeMap shows the resulting geography per file, folder and account, graded by confidence — verified by traceroute, declared by the provider, or inferred. The policy also shapes the durability maths, because the erasure coding is resolved against the pool your rules actually leave.
Related
- SkyeConnex Architecture — the technical deep-dive that situates this term in the full platform.
- How SkyeConnex Works — the step-by-step pipeline.
- Cryptographic Posture — every primitive in active use with its NIST/FIPS reference.
- Whitepaper v1.2 — the consolidated reference document.
Posts that mention Residency (Pillar 03)
Reed-Solomon erasure coding for storage: a practical primer
Reed-Solomon codes are decades old. They're suddenly central to sovereign cloud architecture. Here's what they do, the math you need, and th…
Read → Architecture · 7 min readWhy multi-cloud RAID beats multi-cloud sync
Most multi-cloud storage products replicate your file inside each provider. SkyeConnex erasure-codes it across them. That distinction is the…
Read →