Most people tap and scroll through the internet without a second thought about the scaffolding beneath it. They open an app, fire off a message, and assume the magic just works. But the way that magic is structured—whether it runs on a protocol or a platform—decides who holds power, who can build something new, and who gets locked out when the rules change. Maren Solberg has spent years watching these architectural choices shape societies, and the distinction isn’t just technical. It’s deeply political.
What a Protocol Actually Is
A protocol is a shared language. It’s a set of rules that lets different systems talk to each other without needing to know anything about the other’s internal wiring. Take TCP/IP, the protocol that stitches the internet together. Any device, running any operating system, made by any manufacturer, can send a packet across the network as long as it follows the agreed format. Nobody owns TCP/IP. Nobody can revoke your access to it. The protocol doesn’t care about your identity, your location, or your intentions. It just routes data.
Email works the same way. SMTP handles sending; IMAP and POP3 handle receiving. Because these are protocols, a person on a Gmail account can message someone running a self-hosted server with software from 2003. The protocol is the common ground. It’s a treaty, not a product. When you build on a protocol, you don’t ask for permission. You just speak the language.
What Makes a Platform Different
A platform is a controlled environment. It might use protocols under the hood, but it layers identity, policy, and a business model on top. Facebook is a platform. You can post, comment, and share—but only inside Facebook’s walls. The company decides what content gets promoted, what gets quietly buried, and who can access the API. When you build on a platform, you’re a tenant. The landlord can raise the rent, remodel the building, or evict you entirely.
This isn’t necessarily malicious. Platforms reduce complexity. They handle spam, host your content, and hand you a ready-made audience. But the trade-off is sovereignty. A platform’s terms of service override any technical capability. You might be able to send a message, but the platform decides whether it actually gets delivered.
The Political Layer Beneath the Code
Infrastructure is never neutral. The choice between a protocol and a platform is a choice about governance. Protocols distribute power; platforms hoard it. When email shifted from a messy web of self-hosted SMTP servers to Gmail’s polished interface, convenience won. But so did centralized surveillance. Google now scans your inbox to serve ads and can cut off your account without meaningful recourse. The protocol is still there, humming underneath, but the platform mediates your access to it.
This pattern repeats across the stack. The web was built on HTTP, a protocol. But today, most people experience the web through platform browsers like Chrome, which filters what you see through Google’s Safe Browsing lists. The protocol remains, but the platform decides what’s safe, what’s visible, and what loads quickly. The open road is still there, but most of us drive on private tollways.
Why Protocols Outlast Empires
Protocols are boring. They don’t have splashy launch events or quarterly earnings calls. But that dullness is their superpower. HTTP is over 30 years old. SMTP is over 40. They’ve outlived every platform that tried to swallow them. AOL was a platform. CompuServe was a platform. They’re footnotes now. The open protocols they tried to wall off are still running the world.
The reason is structural. Protocols have no single point of failure. No CEO can be indicted, no server can be seized, no terms of service can be rewritten to kill a competitor. Governance is distributed among the people who implement the standard, and if a faction goes rogue, the rest can fork the spec and carry on. Platforms, with their legal departments and quarterly pressures, can’t match that resilience.
The Cost of Convenience
When a society shifts its communication from protocols to platforms, it loses more than technical diversity. It loses the ability to route around censorship. During the Arab Spring, activists used Twitter—a platform—to organize. But Twitter could be pressured by governments, and it was. Meanwhile, the internet’s underlying protocols allowed the creation of mesh networks and alternative channels that no single entity could shut down. The platform was convenient. The protocol was freedom.
This isn’t a thought experiment. In 2021, Nigeria banned Twitter. The platform complied by restricting access. But the internet protocols underneath didn’t care about the ban. Nigerians who understood the difference used VPNs—tools built on open protocols—to bypass the restriction. The platform obeyed the state. The protocol ignored it.
How to Tell the Difference in Practice
You can spot whether you’re dealing with a platform or a protocol by asking three questions:
- Who can implement it? If anyone can write software that speaks the language without asking permission, it’s a protocol. If you need an API key, a partnership agreement, or a terms-of-service checkbox, it’s a platform.
- Who controls the data? If your data is portable and you can move it to another provider without losing functionality, you’re likely on a protocol. If your data is locked in and your social graph belongs to the company, you’re on a platform.
- Who sets the rules? If the rules are defined by a public specification and enforced by the community, it’s a protocol. If the rules are set by a legal team and enforced by content moderators, it’s a platform.
These questions cut through the marketing fluff. A company might call its API a “protocol,” but if it requires a key and can be revoked at any time, it’s a platform feature wearing a protocol costume.
The Hidden Tax of Platform Dependence
Platforms aren’t just technical choices; they’re economic choke points. When a platform controls the interface between creators and audiences, it extracts rent. YouTube takes 45% of ad revenue. Apple’s App Store takes 30% of transactions. These aren’t fees for hosting or bandwidth—those costs are marginal. They’re taxes on access to the platform’s user base.
Protocols don’t extract rent. Nobody owns SMTP, so nobody can charge you for the act of sending email. You pay for your own server or a provider, but the protocol itself is free. This is why platforms often start on open protocols and then wall them off. Facebook began as a website anyone could visit. Then it built an app. Then it acquired Instagram and WhatsApp. Now it controls the feeds, the algorithms, and the ad revenue. The protocol—HTTP—is still there, but it’s buried under layers of platform control.
The Illusion of Openness
Platforms love to market themselves as open. They offer APIs, developer tools, and “ecosystems.” But these are walled gardens with gates, and the platform holds the keys. When Twitter cut off third-party clients in 2023, developers who had built businesses on the Twitter API were left with nothing. They had mistaken a platform’s temporary generosity for a protocol’s permanent neutrality.
This isn’t a bug; it’s the business model. Platforms must grow and monetize. Protocols simply exist. The moment a platform needs to boost shareholder value, it will tighten the screws on the people who depend on it. That’s not a conspiracy theory; it’s fiduciary duty.
Building on Protocols Is a Political Act
Choosing to build on a protocol rather than a platform is a political act. It’s a declaration that you value long-term resilience over short-term convenience. It’s a bet that open systems will outlast closed ones, as they always have. When you host your own email server, run your own website, or contribute to an open-source project, you’re not just using technology. You’re participating in a governance model that distributes power rather than concentrating it.
This doesn’t mean platforms are evil. They’re useful for specific tasks. But they should be treated as what they are: rented space. Don’t build your home on rented land. Use platforms for distribution, but keep your core infrastructure on protocols you control. Own your domain. Run your own mail server if you can. Use open standards for your data. When the platform pivots or dies, you’ll still be standing.
FAQ
Is HTTP a platform or a protocol?
HTTP is a protocol. It defines how clients and servers exchange hypertext documents. Anyone can implement an HTTP server or client without asking permission. The web itself is not a platform, though many platforms are built on top of it.
Can a platform become a protocol?
Rarely. A platform can open-source its code or publish its API specification, but the power dynamics usually remain. True protocols are governed by neutral standards bodies or community consensus, not by a single company’s interests. ActivityPub is an example of a protocol that emerged to decentralize social networking, but it competes against platforms that have no incentive to interoperate.
Why do protocols feel harder to use?
Protocols prioritize interoperability over user experience. They don’t have a single design team smoothing out rough edges. Platforms invest heavily in UX because they need to retain users and sell ads. The friction of protocols is the price of freedom. Tools like RSS readers and Mastodon clients are improving, but they’ll never be as slick as a billion-dollar platform. The question is whether you value control over convenience.
Are blockchains protocols or platforms?
Blockchains are protocols at the base layer—Bitcoin and Ethereum define rules for consensus and transaction validation that anyone can implement. But many applications built on top of them function as platforms, with centralized interfaces and governance. The distinction depends on where the control lies. A smart contract on Ethereum is a protocol; a custodial wallet is a platform.