Digital Enclosure Is Designed to Make Exit Expensive

In this article:

• Why Is Lock-In a Design Objective Not a Side Effect
• What Is the Real Cost of Exiting a SaaS Platform After Three Years
• Why Is Interoperability a Political Demand and Not a Feature Request
• Frequently Asked Questions
• What makes SaaS platform lock-in so difficult to escape?
• What is interoperability and why do EFF and FSFE fight for it?
• How can you evaluate a SaaS tool's lock-in architecture before you adopt it?
• References

Digital enclosure works because exit is expensive. The platform does not need to keep the product good. It needs to keep the cost of leaving higher than the cost of staying. That calculation is not an accident of technical architecture. It is the design objective.

Every platform decision that makes data harder to export, every format that is proprietary rather than open, every workflow that is built inside the platform rather than on standard protocols is a lock-in decision. These decisions accumulate into an architecture whose primary function is not to serve users but to retain them.

Individual engineers working on data export features are not thinking about enclosure. But the incentive structure that underfunds data export, that deprioritizes migration tooling, that lets proprietary formats persist without investment in open alternatives is making enclosure decisions whether or not anyone names them as such.

For a business leaving a SaaS platform after three years, the exit cost is not just the hassle of learning a new tool. It is the loss of operational history that cannot be meaningfully exported. It is the rebuilding of workflows and reporting. It is the gap in baseline data that makes the first six months on a new platform operationally weaker than the last six months on the old one.

That cost is real and it was deliberately engineered. The platform that does not invest in data portability is not making a neutral technical decision. It is raising the exit cost for every user, every month, compounding the enclosure with each additional piece of data generated inside its system.

Interoperability is the right to take your data and use it with a competing service. It is not a technical nicety. It is the structural condition that makes genuine market competition possible. Without interoperability, switching costs accumulate until the platform can raise prices without competitive consequence.

The EFF and the FSFE have fought for interoperability mandates at the regulatory level precisely because the market does not produce interoperability voluntarily. Enclosure is more profitable than openness. The demand for interoperability is the demand that enclosure have a limit.

Lock-in is difficult to escape because the switching cost is not the price of learning a new tool. It is the loss of accumulated operational data that cannot be meaningfully exported, the rebuilding of workflows and baselines, and the gap in analytical continuity. Platforms deliberately engineer this accumulation.

Interoperability is the right to take data generated on one platform and use it on a competing service without loss of functionality. Without it, switching costs accumulate until platforms can raise prices without competitive consequence. how interoperability mandates work and what the policy fight looks like.

Ask these three questions before signing up:

1. What format does this tool export data in, and can that format be imported into a competing tool without data loss?
2. Can I access my data directly through a database or API, or only through the platform's own export function?
3. What happens to my data if I cancel: is there a grace period, can I retrieve everything, and in what format?

Tools that cannot answer these questions cleanly have lock-in architectures by design.

Electronic Frontier Foundation. eff.org.

Free Software Foundation Europe. fsfe.org.

Doctorow, Cory. The Internet Con: How to Seize the Means of Computation. Verso, 2023.