Chapter 7: The Platform Play

The open-source economy has a secret. The companies that understood it earliest built the most valuable businesses in the world. The companies that missed it changed their licenses in desperation and watched their communities revolt.

The secret is this: the code has no commercial value. All the value is in the layer above it.

A research consortium studying forty-four open-source developer tool companies between 2020 and 2025 distilled the insight into a single sentence: "Control of distribution and operational infrastructure matters more than control of code." That sentence inverts forty years of assumptions about where power lives in the software industry. It says that the thing the open-source movement fought to liberate — source code — is no longer the thing that determines who profits. The battlefield has moved. The code is free. The servers are not.

The Code Is Free, the Servers Are Not

In May 2020, a New Zealand developer named Paul Copplestone changed one line on his company's website. He replaced the tagline "Realtime Postgres" with "The Open Source Firebase Alternative." Within three days, the number of hosted databases on his platform went from eight to eight hundred.

The company was Supabase. It had been founded a few weeks earlier. It had no venture capital, a tiny team, and a product that was, by any reasonable standard, unfinished. But the tagline worked because it answered a question that thousands of developers were asking: Where do I go if I don't want to be locked into Google's Firebase?

Copplestone grew up on a farm near Kaikoura, on the northeast coast of New Zealand's South Island. He started coding at eighteen, moved to Singapore, and joined an accelerator where he met Ant Wilson, a British engineer. They lived together for a year. When Copplestone decided to build an open-source alternative to Firebase, he pitched Wilson the idea over coffee. Wilson said yes. The founding story is almost comically understated.

The pitch was straightforward. Firebase, Google's backend-as-a-service platform, handled databases, authentication, file storage, and real-time data syncing — the plumbing that every app needs but no one wants to build from scratch. But Firebase was proprietary, tightly coupled to Google Cloud, and increasingly expensive at scale. Developers who built on Firebase discovered, over time, that leaving Firebase meant rebuilding everything.

Copplestone's insight was that every capability Firebase offered could be replicated with existing open-source tools. The database was PostgreSQL. The API layer was PostgREST. Authentication was GoTrue. None of these tools were novel. What Supabase built was the glue — the dashboard, the developer experience, the managed infrastructure that made them work together seamlessly. And then it open-sourced the glue, too.

Every major component of its technology stack is published under permissive open-source licenses. Anyone can download the entire stack and run it on their own servers, free of charge, forever. The documentation includes detailed guides for self-hosting. The Docker Compose configuration is maintained alongside the cloud product. The company makes its money from the people who would rather not do any of that.

Supabase Cloud provisions a dedicated Postgres instance for you, configures the API layer, sets up authentication, handles backups, manages scaling, monitors performance, patches security vulnerabilities, and provides a dashboard that makes all of it accessible to a developer who has never touched a database before. You can do all of this yourself with the open-source code. It will take you a week to set up and the rest of your career to maintain. Or you can pay twenty-five dollars a month and have it running in ninety seconds.

Five years later, Supabase is valued at approximately five billion dollars. It manages over a million active databases. Annual recurring revenue reached approximately seventy million dollars by September 2025, with growth of more than 250 percent year over year. In April 2025, the company raised two hundred million dollars at a two-billion-dollar valuation. Six months later, another hundred million at five billion. The stated catalyst was "vibe coding" — the use of AI tools to generate applications. Every AI-generated app needs a database. Two thousand five hundred new databases were being created on the platform every day.

On the other side of the open-source economy, a similar story unfolded with different details and the same underlying logic. Guillermo Rauch, an Argentine software developer, released Next.js in 2016 — a React framework licensed under MIT, with no premium tier, no gated features, no enterprise edition. The framework is worth, in commercial terms, nothing. Rauch's company, Vercel, is valued at $9.3 billion. The gap between those two numbers is the entire thesis of this chapter.

Rauch described open source as "a speedrun to product-market fit." If developers will not use your software when it is free, when the source code is available, when there are no barriers to adoption whatsoever — then you are building the wrong thing. Open source is the harshest possible filter for product quality. Next.js survived. More than survived — it became the default framework for building React applications. By 2025, it was being downloaded tens of millions of times per week, powering the web properties of Walmart, TikTok, and Nike. It was the foundation of an ecosystem so large that the framework had, for practical purposes, become infrastructure.

And Vercel monetized the infrastructure — not the framework. The company built the best deployment platform for Next.js applications: one-click deployments, global edge network, automatic scaling, serverless functions, image optimization. The platform worked with any framework, not just Next.js. But the integration with Next.js was, unsurprisingly, the smoothest, the fastest, the most fully realized. Developers who adopted Next.js because it was free and excellent discovered that deploying it on Vercel was free and more excellent.

Then Vercel launched v0, an AI-powered code generation tool that could build entire application interfaces from natural language descriptions. Three and a half million users adopted it within months. v0 had its own subscription tier — twenty dollars per month — but its real economic function was to accelerate the creation of applications that would be deployed on Vercel's infrastructure. Every application v0 generated was a potential Vercel customer. The AI product was not separate from the platform business. It was a funnel into it. By early 2025, v0 was estimated to contribute over forty million dollars in annual recurring revenue — roughly a fifth of Vercel's total.

Rauch and Copplestone understood the same thing, though they expressed it in different languages. The value of open-source software is not in the software itself. The software is a public good — abundant, non-rivalrous, available to everyone. The value is in the operational context around the software: the servers that run it, the network that delivers it, the tools that monitor it, the team that maintains it, the experience that makes it easy. That operational context is scarce, rivalrous, and expensive. It is, in economic terms, the perfect thing to sell.

The equity analyst in me recognizes this pattern immediately. It is the software version of a principle that media companies learned decades ago: content is king, but distribution is emperor. A brilliant movie is worth nothing without theaters to show it. A brilliant database is worth nothing without servers to run it. GitHub stars are a measure of developer attention. Operational infrastructure is a measure of developer dependency. Attention is fickle. Dependency is durable.

In the open-source world, this principle has a specific and somewhat uncomfortable implication. It means that the Four Freedoms — Stallman's moral architecture for free software — apply to a layer of the technology stack that is no longer commercially decisive. The code is free. The freedom of the code is real. And the freedom of the code is economically irrelevant. The money is somewhere else.

A Browser Engine and the Web

What happens when a trillion-dollar company applies the same pattern at planetary scale?

In September 2008, Google released Chrome and simultaneously published its source code as an open-source project called Chromium. Anyone could take the code. Google chose a permissive license — no copyleft obligations, no reciprocity requirements. Here is our rendering engine, Blink. Here is our JavaScript runtime, V8. Build what you like. The code is free.

Eighteen years later, Chromium-based browsers account for more than eighty percent of desktop web traffic worldwide. Google Chrome alone holds between sixty-five and seventy-one percent of the global browser market. Microsoft Edge runs on Chromium. So does Brave, the privacy-focused browser with seventy million users. So does Opera, Vivaldi, and Samsung Internet. Only two independent browser engines remain in the wild: Apple's WebKit and Mozilla's Gecko, which powers Firefox — declined from over ten percent market share a decade ago to roughly two to three percent across all platforms today.

Google gave away a browser engine and won the web.

The irony is exquisite. The browser wars of the 1990s were fought over proprietary control of the web. The resolution of the 2020s is a different kind of control — one built on openness.

The most telling moment in this story does not involve Google at all. In 2015, Microsoft launched Edge on its own EdgeHTML rendering engine — the successor to Trident, which had powered Internet Explorer through two decades and an antitrust trial. Edge was supposed to be the fresh start. It was modern, fast, standards-compliant. Microsoft shipped it as the default browser on every Windows 10 machine.

It did not matter. Developers built for Chrome. Websites optimized for Chrome. Chrome's extension ecosystem dwarfed Edge's. In 2017, Satya Nadella pushed his team toward a conclusion that would have been unthinkable to a previous generation of Microsoft executives: replace the in-house engine with an open-source one. The internal deliberation lasted over a year. In December 2018, the decision was announced. Microsoft would abandon EdgeHTML and rebuild Edge on Chromium.

The new Edge launched in January 2020. It was, by most accounts, a better browser. It handled enterprise features — group policy, device management — better than Chrome itself. Microsoft did genuinely useful work on top of the Chromium codebase. But the strategic reality was stark. The company that had once dominated the browser market so thoroughly that the United States Department of Justice tried to break it up had surrendered. Not to a better technology. Not to a superior business model. To an open-source project controlled by its biggest competitor.

Chromium is genuinely open source. The code is on GitHub. Google accepts contributions from other companies, including Microsoft, which employs hundreds of engineers working on Chromium. In theory, this is the open-source ideal. In practice, Google sets the direction. Google employs the majority of core contributors. Google decides which features ship. When Google introduced Manifest V3 — a change to Chrome's extension architecture that many ad-blocking developers said would cripple their tools — the other Chromium-based browsers could accept the change, delay it, or fork the codebase and maintain the old behavior. Most accepted it. The cost of diverging from upstream Chromium is prohibitive for all but the largest companies. By mid-2025, Google had completed the transition, removing MV2 extension support in Chrome 138. The most visible casualty was uBlock Origin — the most popular ad blocker — which has no MV3 version. Firefox, pointedly, continues to support both MV2 and MV3, preserving full ad-blocking functionality. One of the few concrete advantages the independent engine still offers.

This is the browser monoculture problem, and it echoes a concern as old as agriculture: when everything depends on one strain, a single vulnerability becomes a systemic risk. If a security flaw is found in Chromium's rendering engine, it affects not just Chrome but Edge, Brave, Opera, Vivaldi, Samsung Internet, and every other browser built on the same foundation. If Google makes an architectural decision that prioritizes its advertising business over user privacy, the alternatives that run on Google's engine have limited room to resist.

Mozilla, the nonprofit behind Firefox, has become the canary in this coal mine. Firefox's Gecko engine is the only rendering engine on the open web that is fully independent of both Google and Apple. Its decline to below three percent market share is not just a business story. It is a story about the structural conditions under which a truly independent alternative can survive when a trillion-dollar company is giving away a very good product for free.

And there is a deeper irony. Mozilla's primary source of revenue is a search deal with Google — roughly four hundred million dollars a year, approximately 86 percent of Mozilla Corporation's total revenue. The independent browser survives on a subsidy from the company whose dominance it is supposed to check. The DOJ's antitrust case against Google initially proposed prohibiting such default search agreements entirely. In September 2025, the court rejected the most aggressive remedies — Google was not required to divest Chrome — but ruled that default search agreements could no longer be exclusive. The last independent engine on the open web depends, financially, on the company that made it irrelevant.

The Fifty-Million-Dollar Bet

The Chromium story is one half of the platform play. The other half is more consequential by an order of magnitude.

In 2005, Larry Page and Sergey Brin heard about a small company called Android Inc. Andy Rubin's original idea had been an operating system for digital cameras. By the time Google came calling, the vision had shifted to phones. The price was fifty million dollars. David Lawee, Google's vice president of corporate development, would later call it the company's "best deal ever."

The first Android phone shipped in September 2008 — the same month Google launched Chrome. The timing was not coincidental. Both products served the same strategic purpose: to ensure that Google's services had unimpeded access to users, whether on desktops or in their pockets.

Google published the full Android operating system under the Apache 2.0 license — permissive, corporate-friendly, no copyleft restrictions. Any manufacturer could take the code, build a phone, and ship it without paying Google a cent.

By 2026, approximately 3.9 billion devices run Android. The operating system holds seventy-two to seventy-three percent of the global mobile market. No piece of software in human history has been installed on more devices.

But the global averages obscure a story more important than market share statistics. In India, Android's share is ninety-five percent. In Indonesia, eighty-seven percent. In Brazil, eighty-one percent. For billions of people, a sub-two-hundred-dollar Android phone is the internet. A farmer in Uttar Pradesh checking crop prices. A student in Lagos accessing Khan Academy. A seamstress in Jakarta managing orders on WhatsApp. These are not users who chose Android over iOS after comparing feature sets. These are users for whom Android is the only economically viable path to the digital world.

Samsung is the largest Android manufacturer, with roughly twenty percent of global smartphone shipments. But the companies that matter most for the digital divide story are the ones that most Americans have never heard of: Xiaomi, Vivo, Oppo, and Transsion. Transsion — which sells phones under the Tecno, Infinix, and itel brands — holds eight and a half percent of the global market, almost entirely in Africa and South Asia. Its cheapest phones sell for under fifty dollars. They run Android. They come with the Play Store. They work.

The fact that this infrastructure is built on open-source code is not incidental. It is the reason it exists. No proprietary operating system could have achieved this distribution. Microsoft tried with Windows Phone and failed. Nokia tried with Symbian and was overtaken. BlackBerry tried and was forgotten. Only a free operating system — free as in price, free as in code — could have persuaded hundreds of manufacturers across dozens of countries to build an ecosystem of this scale without demanding licensing revenue that would have priced their cheapest devices out of existence.

Android's openness connected the world. And Android's openness is also the instrument of Google's control.

There is a version of this story that is purely celebratory. It would emphasize that Google built the infrastructure on which billions of people access education, healthcare information, financial services, and communication with their families. It would note that this infrastructure is built on open-source code that any government, any company, any developer can inspect and modify. It would observe that nothing in the history of proprietary software has achieved anything comparable in terms of equitable global distribution.

That version of the story is true. It is also incomplete.

The Revenue Paradox

The economics of Android are counterintuitive until you understand what Google is actually selling.

Apple's iOS holds roughly twenty-eight percent of the global mobile market but captures sixty-seven percent of global app spending. In 2024, the App Store generated over $103 billion in consumer spending while Google Play generated roughly $47 billion — despite serving a market nearly three times as large. Some of this gap is explained by demographics. The average iPhone user earns fifty-three thousand dollars a year. The average Android user earns thirty-seven thousand. iOS dominates the United States, Japan, and the premium segment globally — the markets where consumers have the most disposable income. Android dominates everywhere else.

But the revenue gap is not a problem Google needs to solve, because app store revenue is not what Google is after. Apple charges a thirty-percent commission on app purchases and fights over every percentage point. Google takes the same commission but cares less about the revenue it generates. The Play Store is not a profit center. It is a distribution channel for the services that are. In 2024, Alphabet's total revenue reached $350 billion, with advertising accounting for roughly $230 billion. The advertising business depends on two things: user data and user attention. Android provides both. Every Android phone ships with Google Search as the default, Chrome as the default browser. Every search query, every website visit, every YouTube video, every Maps navigation generates data that feeds the advertising engine.

This is the open-core model applied at civilizational scale. The code is free. The data pipeline is not.

The mechanism of control is specific and well-documented, because the European Commission spent years investigating it. Android the operating system — AOSP — is open source. Google Mobile Services — GMS — is proprietary. GMS includes the Play Store, Google Search, Chrome, YouTube, Gmail, Maps, and several other applications. Manufacturers who want the Play Store must accept the entire bundle. They must pre-install Search and Chrome. They must agree not to sell devices running modified versions of Android that Google has not approved.

In July 2018, the European Commission fined Google 4.34 billion euros — at the time, the largest antitrust penalty in EU history. Google introduced a paid licensing option for GMS in Europe — manufacturers could, in theory, license the Play Store without bundling Search and Chrome. In practice, the fees made it economically irrational. The bundle remained the default.

Huawei discovered what this means in 2019, when United States sanctions cut off its access to GMS. The company built its own app store, its own mapping service, its own alternative to every Google service it lost. Its global smartphone sales still collapsed. Huawei shipped 33 million smartphones in the fourth quarter of 2020 — a 41 percent year-over-year decline — dropping from the world's largest smartphone maker to the sixth largest in a matter of months. By 2021, it had fallen out of the global top five entirely. The company that had briefly surpassed Samsung discovered what every Android manufacturer already knew: AOSP without GMS is a phone without a soul.

The open-source layer is the foundation. The proprietary layer is the building. And the building is where people actually live.

This is what makes the open-source critique so difficult to articulate. AOSP is a genuine public good. It has lowered the cost of smartphones worldwide. It has enabled competition among manufacturers in a way that no proprietary system has matched. It has given billions of people access to the internet. These are not marketing claims. They are observable facts. The critique is not that AOSP is fake open source — it is real open source, with a real permissive license and real source code that anyone can compile and run. The critique is that real open source can coexist with, and even enable, real market capture. The freedom of the code and the control of the ecosystem are not contradictions. They are complements.

The analyst in me finds this structure elegant. It solves the monetization problem that plagued open-source companies for decades — you do not need to charge for the code if the code generates demand for something else. Red Hat charged for support. MongoDB charged for hosting. Google charges for nothing. It gives away the platform and collects the data. The margin on advertising is effectively infinite because the input cost of the platform is zero. The open-source operating system is not the product, not the loss leader, not the gateway drug. It is the infrastructure that makes the actual product — the global advertising network — possible at a scale that no closed system could achieve.

The Pattern

Stand back from the details and the pattern is unmistakable.

Supabase: open the database, monetize the hosting. Vercel: open the framework, monetize the deployment platform. Chromium: open the browser engine, monetize the search and advertising services that run inside it. Android: open the mobile operating system, monetize the app store and data services that run on top of it.

The principle is the same at every scale. Open the layer that developers and manufacturers build on. Create an ecosystem so large and so dependent on your platform that the services layer becomes an inevitability. Then monetize the services.

But scale changes the moral equation. When Supabase gives away a database, the consequence is that startups have cheaper infrastructure. When Google gives away a browser engine, the consequence is that eighty percent of the web runs on code that Google controls. When Google gives away a mobile operating system, the consequence is that 3.9 billion people carry a device in their pockets that funnels their data through Google's services.

The code is open. The ecosystem is captured. And the capture is not achieved through the traditional mechanisms of monopoly — exclusive contracts, predatory pricing, acquisitions of competitors — though Google has employed those as well. The capture is achieved through generosity. The gift of the code creates the dependency on the service. The freedom of the platform enables the lock-in of the user.

The open-source movement was built on the premise that free code produces free ecosystems. Stallman's four freedoms were designed to ensure that no single entity could control the tools that society depends on. Chromium and Android satisfy every one of those freedoms. You can run AOSP on any device you build. You can study the Chromium source code down to the last line. You can modify either project without permission. You can distribute your modifications to anyone.

And yet. The web is dominated by one engine. The mobile internet is dominated by one company's services. The freedoms are intact. The concentration is total.

The platform play reveals a gap in the original open-source theory: the assumption that freedom at the code layer would produce freedom at the ecosystem layer. When the code is a consumer product used by billions — not a server tool used by thousands of developers — the dynamics are fundamentally different. Network effects, default settings, and the sheer cost of building alternatives do what licenses never could: they concentrate control in the hands of the entity that controls the upstream project.

This pattern matters because it is about to be applied to artificial intelligence. And in the AI context, the stakes are different.

The Copyist

In July 2024, Mark Zuckerberg published an essay that read like a strategic manifesto disguised as an open letter. The title was "Open Source AI Is the Path Forward." The occasion was Meta's release of Llama 3.1, a large language model with 405 billion parameters — the most powerful open-weight AI model released to that date.

The essay made philosophical, technical, and economic arguments for open-source AI. But buried in the middle was an explanation that illuminated the strategic logic more clearly than anything else Zuckerberg wrote.

He described how building Meta's services under Apple's constraints on iOS had been one of his "formative experiences" — the developer taxes, the restrictions on what Meta could build, the product innovations that Apple blocked. Apple's App Tracking Transparency framework, introduced in 2021, wiped an estimated ten billion dollars from Meta's annual advertising revenue by making it harder to track users across apps. Meta's CFO confirmed the magnitude in early 2022, stating that the iOS changes represented a headwind "on the order of $10 billion" for that year alone.

Zuckerberg learned the lesson that Google had taught with Chromium and Android. If you do not control the platform, the platform controls you. And his proposed solution — open-source AI models that anyone could run, modify, and deploy — was the same pattern in a new domain. Open the platform layer. Build the ecosystem. Ensure that the next generation of computing does not have a single gatekeeper.

The statement was remarkable for its honesty. Zuckerberg was not describing an abstract commitment to openness. He was describing a wound. A company valued at over a trillion dollars, with more than three billion monthly active users, had been constrained, taxed, and blocked by a proprietary platform. The thirty-percent App Store commission cost Meta billions. And the response was not to build a better proprietary alternative. The response was to copy Google's playbook — to open-source the foundation layer so that no one could do to Meta in AI what Apple had done to Meta in mobile.

Whether Meta's open-source AI strategy is genuinely different from Google's platform play — or whether it is simply the same capture pattern wearing new clothes — is the question that will define the next era of the technology industry.

The code is free. The servers are not. The companies that understood this distinction earliest built the most valuable open-source businesses in the world. Google gave away a browser engine and won the web. It gave away a mobile operating system and won the pocket. Now the same pattern is being applied to artificial intelligence, by a company that learned the hard way what it means to be on the wrong side of a platform. The scale changes everything — and the question is whether the freedom changes anything at all.