Skip to content
Solidarity Commons Protocol

Platform Cooperatives and Digital Sovereignty

Platform cooperatives matter because digital platforms can capture the value created by users, workers, creators, moderators, and communities. Digital sovereignty asks a related question: can a community use shared digital infrastructure without becoming a tenant of one company, one database, or one exit path?

Concrete examples sit on a spectrum. A creator platform can improve direct payments while still leaving the platform sellable to outside owners. A cooperative platform such as Subvert or Stocksy asks who owns the platform, who elects board seats, and who receives surplus. A member-governed federated space such as Social.coop separates instance governance from the broader social protocol. Portability projects such as Data Transfer Initiative and Solid reduce lock-in, but they do not answer governance by themselves.

Basic Pattern

Section titled “Basic Pattern”

Platform Cooperativism Consortium describes platform cooperatives as businesses that sell goods or services primarily through a website, mobile app, or protocol, relying on democratic decision-making and shared platform ownership by workers and users. It also emphasizes broad-based ownership, democratic governance, co-design, and open source or open data aspirations.

Some projects begin as conventional startups and later try to change who owns them. The Platform Cooperativism Consortium resource on Exit to Community describes a transition from investor ownership toward ownership by the people who rely on a company most, such as users, workers, customers, participant organizations, or combinations of stakeholders.

Digital sovereignty also depends on portability and protocol boundaries. Data Transfer Initiative focuses on making it easier for technology users to transfer data from one service to another. ActivityPub is a W3C Recommendation for decentralized social networking based on ActivityStreams 2.0. Social Web Foundation frames the social web as open and decentralized spaces that no one organization controls.

What Examples Clarify

Section titled “What Examples Clarify”

Creator-owned marketplaces need records for owner classes, contributions, payment rules, dividend or surplus logic, and board representation. The platform still needs competent operations; shared ownership does not mean every product decision goes to a mass vote.

Exit to Community needs transition records: which users, workers, customers, creators, or organizations become owners; which investor rights remain; which assets transfer; and which obligations bind the new steward.

Federated social spaces need a split between protocol records and instance records. A protocol can move posts or follows across services, while a community still needs its own membership, moderation, treasury, and governance history.

Data-portability projects need consent, export, deletion, delegation, and interoperability evidence. Portability lowers exit costs, but it does not decide who should benefit from the platform’s value.

Why It Matters Here

Section titled “Why It Matters Here”

Platform co-ops and digital-sovereignty projects create records that cross governance, data, economics, and federation:

  • Which stakeholder classes can join, vote, govern, moderate, receive benefit, or exit.
  • Which terms, bylaws, trust documents, community agreements, or protocol rules constrain platform operators.
  • Which creator, worker, user, moderator, or organizational-member records support participation or benefit.
  • Which data can be exported, ported, deleted, delegated, or shared across services.
  • Which moderation, ranking, algorithm, federation, or interoperability decisions were authorized.
  • Which securities, consumer-protection, privacy, labor, intellectual-property, or data-protection systems remain external.

This page sits near Cooperative Governance, Federation and Shared Services, Data Trusts and Cooperatives, and Community Investment.

What Software Should Not Flatten

Section titled “What Software Should Not Flatten”

A platform cooperative is not just a social app with voting. It may involve worker ownership, user membership, creator payments, data rights, moderation duties, open protocol commitments, investment terms, and public-facing service obligations.

Digital sovereignty is also not solved by export buttons alone. Portability, federation, privacy, consent, moderation, identity, reputation, and community governance can conflict. A protocol can make movement possible, but it does not decide who should govern a community, who receives benefit, or which records are safe to expose.

Solidarity Commons Protocol can preserve membership, authority, agreements, provenance, portability decisions, federation records, and benefit references. It should not replace platform compliance, data-protection review, securities advice, payment rails, content moderation operations, or the protocols that already govern external networks.

Section titled “Read Next”