BDS as Framework: Divesting From Your Extractive SaaS Stack

In this article:

• How Does the BDS Framework Apply to Extractive SaaS Platforms
• Boycott: Which Tools to Stop Using
• Divestment: Removing the Financial Relationship
• Sanctions: The Collective Pressure Layer
• Frequently Asked Questions
• How do you apply the BDS boycott principle to a SaaS stack?
• What is the difference between canceling a SaaS subscription and divesting from it?
• What is the sanctions layer in the SaaS context?
• References

BDS as a framework for SaaS divestment is not an analogy. It is an application of an organizational logic that has been tested at scale, refined over two decades of campaign work, and proven capable of producing material economic consequences for targeted entities. The logic applies to platform dependency because the structural situation is similar: concentrated power, captured infrastructure, and the need for collective organized response.

Boycott in the SaaS context means identifying the platforms whose practices meet the criteria for withdrawal and ceasing to pay for them. The criteria should be principled rather than reactive: platforms that store data in non-portable formats, that use aggregated user data for purposes beyond the stated product function, that are owned by private equity firms with documented histories of extraction following acquisition, or that have demonstrated willingness to suppress political speech are candidates for boycott.

Boycott is most effective when it is targeted and principled rather than total and reactive. Identifying which subscriptions represent the greatest lock-in risk and the deepest alignment with extractive practices, and exiting those first, is a strategy.

Divestment in the SaaS context means removing not just the subscription but the dependency. A business that cancels a SaaS subscription but continues to run workflows that require that platform's data has not divested. It has disrupted its operations while maintaining the dependency. Divestment requires replacing the capability before canceling the subscription, migrating the data before the access ends, and rebuilding the workflow on alternative infrastructure before declaring the exit complete.

Sanctions in the BDS framework means institutional and governmental pressure on the targets of the campaign. In the SaaS context, the equivalent is regulatory advocacy: supporting interoperability mandates, data portability requirements, and competition enforcement actions against platforms that use lock-in to suppress market competition. EFF and FSFE are doing this work. Supporting their advocacy is the sanctions layer of the framework.

The three-part framework makes the response to extractive SaaS more coherent than individual exit decisions made without shared logic. Boycott withdraws participation. Divestment removes dependency. Sanctions creates the systemic pressure that changes the conditions under which the next generation of platforms operates.

Identify platforms whose practices meet principled criteria for withdrawal. Candidates include platforms that:

• Store your data in non-portable formats that cannot be meaningfully exported to a competing service
• Use aggregated user data for purposes beyond the stated product function, including competitive intelligence and AI training
• Are owned by private equity firms with documented histories of enshittification following acquisition
• Have demonstrated willingness to suppress political speech or apply terms of service selectively based on content that threatens their commercial interests

Exit those first, starting with the ones where lock-in is deepest and the extractive practices are most documented.

Canceling a subscription stops the payment. Divesting removes the dependency. An agency that cancels a subscription but continues running workflows that require that platform's data has canceled without divesting. True divestment requires replacing the capability, migrating the data, and rebuilding the workflow on alternative infrastructure before the subscription lapses. the step-by-step migration guide that makes divestment operationally viable.

Sanctions in BDS means governmental and institutional pressure. In the SaaS context, the equivalent is regulatory advocacy: supporting interoperability mandates, data portability requirements, and competition enforcement against platforms that use lock-in to suppress market competition. The EFF and FSFE are doing this work.

BDS Movement. bdsmovement.net.

Electronic Frontier Foundation. eff.org.

Free Software Foundation Europe. fsfe.org.

PACBI. pacbi.org.