People toss around the words platform and protocol like they mean the same thing. They don’t. And the mix-up isn’t just a vocabulary fail. It’s a political blind spot. If you can’t tell a platform from a protocol, you can’t see who’s holding the reins, how they use that grip, or what happens when the rules shift under your feet without so much as a nod in your direction.
I’m Maren Solberg. I write about infrastructure because infrastructure has never been neutral—not once. The shape of a network decides who gets heard, who can trade, and who can be quietly erased. This piece is about two radically different ways of organizing digital life. One’s a platform. The other’s a protocol. Getting the distinction straight isn’t academic. It’s the bare minimum for any real talk about tech and society.
What a Protocol Actually Is
A protocol is a rulebook for how machines talk to each other. Not a product. Not a company. It’s a specification, usually published as a public document, that anyone with the chops can implement. The Internet Protocol (IP), the Simple Mail Transfer Protocol (SMTP), the Hypertext Transfer Protocol (HTTP)—these are protocols. They spell out message formats, the sequence of operations, how to handle errors. They don’t say who gets to join or what kind of content is okay.
Protocols get hammered out in standards bodies like the Internet Engineering Task Force (IETF) or the World Wide Web Consortium (W3C). These groups aren’t saints. They have their own politics, their own biases, their own corporate fingerprints. But the core architecture of a protocol is decentralized. Anyone can write software that speaks SMTP. Anyone can spin up a mail server. The protocol doesn’t care about your identity. It cares whether your packets are properly formed.
That’s not a footnote. It’s a constitutional principle. When you build on a protocol, you’re not asking for permission. You’re not bound by a terms of service that can flip overnight. You’re not one policy change away from being booted off because the network owner decided your content was a problem. The protocol is indifferent to your politics, your business model, your passport. That indifference is a kind of freedom.
What a Platform Actually Is
A platform is a privately owned space. It uses protocols under the hood—HTTP, TCP/IP, and the rest—but it layers control on top. Facebook, YouTube, Twitter, TikTok: these are platforms. They’re walled gardens built on open ground.
The thing that defines a platform is intermediation. It wedges itself between you and your audience, between buyer and seller, between writer and reader. The platform decides what surfaces, what gets recommended, what disappears. It enforces a terms of service that’s a legal document, not a technical spec. Break those terms, and you lose access—not just to the platform, but to the people you reached through it.
Platforms aren’t evil by nature. They do useful things. They handle spam, abuse, and illegal content at a scale that open protocols can’t easily match. But they also hoard power. When a platform becomes the main way people communicate, the owner of that platform becomes a de facto speech regulator. That’s not a glitch. It’s the business model.
The Governance Gap
Protocols are governed by standards. Platforms are governed by executives. The difference bites. Disagree with a protocol decision? You can fork the standard, write your own implementation, or join a competing standards body. The barriers are technical and social, but they’re not legal. Disagree with a platform decision? You’ve got nothing. You can’t fork Facebook. You can’t run your own YouTube instance that talks to the main network. The platform is a monolith.
This governance gap is getting wider. In the early internet days, most communication ran over open protocols: email, Usenet, IRC. Today, most communication runs on platforms. The shift wasn’t fate. It was driven by convenience, network effects, and a deliberate strategy by venture-funded companies to capture value that protocols left lying around.
Protocols don’t have a business model. They’re public goods, kept alive by volunteers or underfunded nonprofits. Platforms have a very clear business model: hoard attention, sell ads, extract data. The asymmetry is baked in. Platforms can pour billions into user experience, moderation, and growth. Protocols depend on the goodwill of engineers who are often working for free.
The Email Example
Email is the cleanest illustration of the split. SMTP is a protocol. Anyone can run an email server. Gmail is a platform. Most people use Gmail. Google didn’t invent email. They built a slicker client and a better spam filter, and they gave it away. Over time, Gmail became so dominant that running your own email server turned impractical. Deliverability now hinges on reputation systems controlled by a handful of big providers. The protocol is still open, but the ecosystem isn’t.
That’s the platform playbook. Build on an open protocol. Add proprietary features. Hit scale. Use that scale to make the open ecosystem unlivable for anyone else. Then tighten the screws. Tweak the algorithm. Raise prices. Hoover up more data. The protocol remains as a fig leaf, but the real power has moved elsewhere.
Why This Is a Political Problem
Infrastructure is political because it shapes who gets what power. A world of protocols is a world where power is scattered among implementers, users, and standards bodies. A world of platforms is a world where power pools in a few corporate headquarters. The choice isn’t between efficiency and chaos. It’s between different forms of governance.
When a government wants to muzzle speech, it can lean on platforms far more easily than it can lean on protocols. A platform is a single point of failure. A protocol is a hydra. Cut off one implementation, and others keep going. That’s why authoritarian regimes love platforms. They offer a handy choke point. The Chinese government doesn’t need to block every website. It just needs to control WeChat.
But the political problem isn’t just about authoritarianism. In democratic societies, platforms exercise a kind of private governance that’s largely unaccountable. Content moderation decisions shape public discourse, but they’re made behind closed doors. Appeals processes are murky. The rules change without warning. That’s not how public infrastructure should work.
The Interoperability Question
One way to bridge the gap between platforms and protocols is to mandate interoperability. If a platform gets big enough, it should be required to expose APIs that let competing services interact with it on equal footing. That’s the idea behind data portability and the right to exit. If you can leave Facebook and still message your friends, Facebook stops being a prison.
Interoperability isn’t a magic fix. It brings security risks, privacy headaches, and coordination snags. But it’s a structural remedy for a structural problem. The goal isn’t to smash platforms. The goal is to stop them from becoming permanent fixtures of the digital landscape. A platform should be a service you pick, not a territory you’re born into.
The European Union’s Digital Markets Act is an attempt to write this principle into law. It requires large platforms to offer interoperability for messaging services and to allow third-party app stores. The details are messy, and the implementation will be fought tooth and nail. But the direction is right. Lawmakers are starting to grasp that digital infrastructure is infrastructure, and infrastructure needs regulation.
The Historical Pattern
This isn’t the first time society has faced a choice between open and closed infrastructure. The 19th-century railroad barons built proprietary rail networks with incompatible gauges. The Bell System controlled telephone infrastructure for decades, blocking third-party devices from connecting. In each case, the early phase of proprietary control gave way to regulation, standardization, and eventually common carriage.
The internet repeated this pattern in fast-forward. The early internet was a network of protocols. The Web 2.0 era was a land grab by platforms. We’re now in a third phase, where the political fallout of platform dominance is getting too loud to ignore. The question is whether we’ll respond with the same tools our predecessors used: antitrust enforcement, interoperability mandates, and public investment in open alternatives.
History hints that platforms don’t last forever. They’re vulnerable to technological shifts, regulatory pressure, and user revolt. But the shift from platform to protocol isn’t automatic. It takes deliberate political action. It takes people who understand that the architecture of a network is a form of law.
What You Can Do
Grasping the difference between a platform and a protocol is step one. Step two is acting on that understanding. Use services built on protocols when you can. Support organizations that maintain open standards. Push for interoperability mandates. Run your own server if you’ve got the skills. If you don’t, pay someone who does.
This isn’t a call for digital puritanism. You don’t need to delete all your platform accounts and retreat to a cabin with a self-hosted email server. But you should be clear-eyed about the tradeoffs you’re making. Every time you post on a platform, you’re building value on land you don’t own. Every time you use a protocol, you’re investing in infrastructure that no single entity controls.
The difference between a platform and a protocol is the difference between a shopping mall and a public road. The mall is private property. The owner sets the rules. The road is a commons. Anyone can use it, and no one can be excluded without due process. We need both. But we should be honest about which is which, and we shouldn’t let the mall owners convince us that their private rules carry the weight of public law.
FAQ
What is the main difference between a platform and a protocol?
A protocol is an open set of rules for communication that anyone can implement without permission. A platform is a privately owned service that uses protocols but adds a layer of control, sitting between users and deciding what content or behavior is allowed.
Why do platforms tend to dominate over open protocols?
Platforms can invest heavily in user experience, moderation, and network effects because they have a business model—usually advertising or data monetization. Protocols, as public goods, often lack funding and dedicated teams, making them slower to evolve and harder for average users to adopt.
Can a platform become a protocol?
Not easily. A platform can open its APIs or adopt standards that allow interoperability, but the core control usually stays with the owning company. True protocols are defined by open specifications and decentralized governance, which is fundamentally different from a single company’s product roadmap.