In this article:

• Why Is Individual Platform Exit Structurally Insufficient
• What Does the BDS Organizational Model Contribute to Platform Resistance
• What Alternative Infrastructure Is Already Being Built
• What Does a Collective Platform Exit Strategy Actually Require
• What Frame Connects These Fronts Into a Coherent Resistance
• Frequently Asked Questions
• Why is individual platform exit not enough to resist platform capture?
• What can the BDS Movement's organizational model teach tech resistance movements?
• What is the collective platform exit strategy and does it exist yet?
• References

Resistance to platform capture is not primarily an individual decision, and treating it as one is one of the main reasons it fails. An individual business migrating off a SaaS platform to a self-hosted alternative has solved its own problem. It has not changed the platform's pricing structure, its data portability decisions, or its lock-in architecture. The businesses that remain on the platform are no less captured after the migration than they were before it. The individual exit is real and meaningful for the business that completes it. As a strategy for changing the conditions that produced the problem, it is insufficient. The strategy that works at scale is collective, organized, and backed by alternatives that make participation viable for more than the technically sophisticated early adopter.

This is not an argument against individual exit. It is an argument for understanding individual exit as a tactic within a larger strategy rather than as the strategy itself. The BDS Movement, the Boycott, Divestment, and Sanctions campaign founded by Palestinian civil society in 2005, is the most sophisticated example of organized collective economic pressure operating at scale in the contemporary world. Its organizational logic has been tested across two decades of campaign work against targets with significant economic and political resources. The structure it developed for making collective withdrawal viable, coordinated, and sustained over time is directly applicable to the problem of platform dependency, even though the targets, stakes, and political context are entirely different.

Individual platform exit carries risks that collective exit distributes. The business that moves to self-hosted infrastructure before that infrastructure is mature, well-documented, and community-supported bears the full operational burden of the transition alone. It encounters bugs that have not been reported by a large enough user base to prioritize fixes. It writes documentation that does not yet exist. It solves configuration problems that later adopters will find already solved. The individual exit is harder, more expensive, and more fragile than the collective exit that follows once the community has built the supporting infrastructure around the alternative.

This is not a reason to wait for others to go first. Early adoption of alternatives is how the alternatives become viable for later adopters. But it is a reason to understand individual exit in its correct strategic context: as a contribution to a collective process rather than as a self-contained solution. The business that exits a SaaS platform and documents the migration process publicly is doing more for the collective strategy than the business that exits and keeps the process proprietary. The value of the individual exit is multiplied by the degree to which it builds the commons of knowledge and tooling that makes the next exit easier.

Individual exit is also fragile in a second sense: it does not change the incentive structure that produced the problem. A platform losing two percent of its users to self-hosted alternatives annually adjusts its pricing model accordingly and continues extracting rent from the ninety-eight percent that remain. Individual exit at small scale does not create competitive pressure. It creates the appearance of a niche market for self-hosted alternatives without changing the dominant platform's behavior.

BDS did not emerge as a spontaneous consumer boycott. It was structured by over one hundred and seventy Palestinian civil society organizations as a principled, targeted campaign with defined objectives, clear criteria for participation, and a coalition structure that allowed coordination across organizations with different political contexts and different levels of exposure to risk. The framework distinguishes among boycott, the individual and collective withdrawal from participation with targeted entities; divestment, the removal of institutional financial relationships from complicit entities; and sanctions, the demand for governmental and institutional pressure on those entities. The three-part structure is designed to allow participation at multiple levels of commitment and risk, making the campaign viable for actors with very different capacities.

The infrastructure that makes BDS work includes a research layer that documents corporate complicity with enough specificity to make targeted campaigns credible and defensible: WhoProfits maps corporate activities in the occupation with documented evidence. It includes a coordination layer that connects national and international organizations without requiring organizational merger. It includes a support layer that provides resources and mutual aid to participants facing retaliation. And it includes a communications layer that makes the framework legible to new participants and maintains the shared understanding of what the campaign is doing and why.

None of this infrastructure exists for platform exit from extractive SaaS. The community of practitioners moving toward self-hosted and decentralized alternatives is making individual decisions that are structurally similar to each other but organizationally disconnected. There is no research layer documenting platform practices with the specificity needed to make targeted exit campaigns credible. There is no coordination layer connecting practitioners making the same decisions. There is no support layer providing resources to businesses during the transition. The individual exits are happening. The collective strategy does not yet exist.

Tech for Palestine is one of the clearest examples of the collective alternative-building strategy operating in the digital context. The coalition has incubated more than twenty projects since its founding, building tools, platforms, and infrastructure that Palestinian communities and solidarity organizations can use without depending on platforms that have demonstrated willingness to suppress Palestinian voices. UpScrolled is a decentralized social platform built as an explicit alternative to Meta and TikTok. The Boycat app makes corporate complicity in the occupation legible and actionable at the individual consumer level. These are not individual exits. They are coordinated constructions of alternative infrastructure backed by a community that understands what it is building and why.

The Electronic Frontier Foundation and the Free Software Foundation Europe are building the policy layer of the alternative: fighting for interoperability mandates, data portability requirements, and competition enforcement actions that would structurally reduce the switching costs that make platform lock-in viable. The Mastodon network, Signal, Proton, Codeberg, and Cloudron are building the technical layer: operational alternatives to surveillance capitalist infrastructure that are governed by nonprofits and cooperatives rather than by platforms optimizing for extraction. These are the components of a collective alternative. They are not yet coordinated into a strategy.

The gap between the components and the strategy is the organizational gap that BDS's framework addresses. BDS is effective not because any individual boycott action is devastating to its target but because the framework connects individual actions to a shared analysis, coordinates those actions toward shared objectives, and sustains participation over the long timeline that economic pressure campaigns require to produce results. The components of a platform exit strategy exist. The framework that connects them and the coordination infrastructure that sustains collective action over time do not yet exist at scale.

A collective platform exit strategy requires three things that individual exit does not:

1. A shared analysis of targets, based on documented practices rather than general dissatisfaction. Documentation needs to be specific enough to be defensible and actionable. Which platforms engage in data extraction beyond their stated function? Which are owned by entities whose incentive structures guarantee enshittification? Which have demonstrated willingness to use their infrastructure for political censorship?
2. Credible alternatives that make exit viable for practitioners who are not technically sophisticated early adopters. The self-hosted alternatives exist. The documentation and support infrastructure that makes them accessible to a practitioner who has never managed a server does not yet exist at the scale needed. Building that infrastructure is a contribution to the collective strategy.
3. A shared frame that connects individual decisions to a larger understanding of what is being resisted and why. The business that exits a platform because the pricing got too high made an individual economic decision. The business that exits because it understands the enshittification sequence, the technofeudal dependency model, and the role of collective withdrawal in changing the conditions that produced those dynamics made a political decision. The political decision is more durable because it does not depend on the pricing remaining intolerable.

The practitioners building self-hosted tools, the engineers contributing to Mastodon and Signal, the organizers building Tech for Palestine's infrastructure, the policy advocates at EFF and FSFE fighting for interoperability mandates, the artisan sellers moving their stores off Etsy and onto self-hosted WooCommerce: these are all making versions of the same decision from different positions in the same system. The system is the one Varoufakis calls technofeudalism, the one Doctorow describes through the enshittification sequence, the one Ostrom's commons governance research identified the alternative to, the one BDS's framework shows how to resist collectively.

The frame that connects these fronts does not yet have an institution behind it. It has a set of practices, a set of analytical frameworks developed by thinkers working in different domains, and a growing number of practitioners making decisions that express the frame without always having named it. Naming it is part of the work. The connection between the BDS framework and the platform exit strategy, between the enclosure of the digital commons and the enclosure of the English commons, between the surveillance capitalism that extracts value from business workflows and the surveillance capitalism that suppresses Palestinian voices, is not an analogy. It is a description of how the same system operates on different targets simultaneously.

Resistance that understands this is more durable than resistance that does not. Individual exit from a platform you find frustrating is reversible when the frustration subsides. Collective withdrawal from a system you understand is structural is sustained by the understanding rather than by the emotional temperature of the moment.

Individual exit solves the individual problem without changing the structural conditions that produced it. A platform losing two percent of users to self-hosted alternatives adjusts its pricing and continues extracting from the ninety-eight percent who remain. Individual exit at small scale creates a niche market for alternatives without creating competitive pressure.

BDS demonstrates that collective economic pressure requires a research layer that documents complicity specifically, a coordination infrastructure that connects participants without requiring organizational merger, a multi-level framework that enables participation at different levels of commitment, and a long-term orientation sustained by structural analysis. the BDS organizational model explained in detail.

The components exist: self-hosted tooling, decentralized communication infrastructure, EFF and FSFE policy advocacy, open source alternatives, and communities like Tech for Palestine building the framework. The coordination infrastructure that connects these components into a coherent strategy does not yet exist at scale.

BDS Movement. bdsmovement.net.

Tech for Palestine. techforpalestine.org.

Electronic Frontier Foundation. eff.org.

Electronic Frontier Foundation. Interoperability. eff.org.

Free Software Foundation Europe. fsfe.org.

WhoProfits. whoprofits.org.

US Campaign for Palestinian Rights. uscpr.org.