A company decides to leave its US cloud provider. On paper, backup has always been in place: data has been copied elsewhere every night for years. But when the time comes to actually leave, almost nothing goes as planned.
Backup is not a one-way ticket
A backup answers one specific question: what to do if a file disappears or a server goes down. It does not answer a different, rarer but real question: how to leave the provider itself. The data is there, copied, encrypted, available. What is missing is the history of how the data got there: who created a given record, under what authorization, on what date, and under which version of the policy then in force.
Three functions that had blended into one
Over time, three different things had ended up merged into a single system: where the data is stored, how it is backed up and restored, and the memory of its history — who wrote what, when, and why. As long as everything stays with the same provider, this blending costs nothing. It becomes a problem the day you want to change just one of these three pieces without touching the other two.
What changes once they are separated
By separating these three functions, a move becomes an ordinary project again rather than a full rebuild. Storage can change provider. The backup tool can stay the same or evolve on its own. And the history of the data — who changed what, under which rule, at what time — keeps existing independently of both, ready to be verified wherever the data ends up next.
This is exactly the role KARL Core plays in StratoFoundry's architecture: keeping the memory and provenance of data as a separate layer, neither a storage provider nor a backup tool, so that changing either one remains an ordinary technical decision rather than a gamble.
The opposite of being locked into a provider is not using several of them. It is being able to actually leave, the day you decide to, with everything you need to keep of your history.
It's not a question of how many providers you use. It's a question of architecture: when the history and provenance of data live separately from storage and backup, reversibility stops being a sales promise and becomes something you can actually test.