Portability (Pillar 04)
Can you leave? — The fourth of the five pillars. Asks whether exit is genuinely available. Lock-in is treated as a sovereignty failure rather than a commercial inconvenience: a vendor you cannot leave sets your terms on cost, renewal and everything else.
The question
If you cannot walk away, you were never in control. Egress economics, proprietary formats and operational entanglement are all mechanisms for removing a choice you believed you had.
The architectural answer
SkyeConnex orchestrates rather than replaces: you keep your hyperscalers, and shards sit in storage accounts you own. If a provider fails, is acquired or squeezes you, data reconstitutes elsewhere and recovery runs without SkyeConnex in the path. Recoverability is architectural, not contractual.
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 Portability (Pillar 04)
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 →