Standing on Giant Shoulders: The Invisible Infrastructure Powering a Generation of Builders

There's a running joke in startup circles: every "self-made" founder built their company on the backs of a hundred tools they got for free. It's funny because it's true—and it's also something most of the tech industry doesn't talk about nearly enough.

The digital commons is real, it's massive, and it's quietly subsidizing innovation at a scale that would make even the most generous venture fund blush. We're talking about publicly maintained APIs, community-run databases, open protocol standards, and collaborative knowledge platforms that collectively power billions of daily interactions—without a single line of VC capital behind them.

So how does it all work? And who actually keeps it running?

What We Mean by the Digital Commons

The term "commons" comes from an old concept in land use—shared resources that a community maintains collectively, like a town pasture or a public well. The digital version is conceptually similar but operates at a completely different scale.

Think about Wikipedia. As of 2024, it hosts over 60 million articles across hundreds of languages, runs on a nonprofit model, and is used as a foundational data source by AI companies, search engines, app developers, and students writing term papers at 2 a.m. The Wikimedia Foundation operates on roughly $150 million annually—a figure that sounds large until you realize the economic value flowing through that platform likely runs into the tens of billions.

Or consider OpenStreetMap, a collaboratively built geographic database that rivals Google Maps in raw coverage and surpasses it in openness. Ride-sharing apps, logistics startups, humanitarian organizations, and urban planners all dip into OSM's data regularly. It's maintained by a global volunteer community and a small nonprofit. The companies building on top of it? Some are worth hundreds of millions.

This gap—between what the commons costs to maintain and the value it generates for those who use it—is what economists sometimes call the "free rider" problem. But it's also, in a very real sense, the engine of the modern startup economy.

The Builders Who Got It

Meet the kind of founders who've figured this out—and built their businesses around it rather than in spite of it.

Jamila Osei spent three years bootstrapping a civic data platform that helps local governments in the Southeast visualize infrastructure needs. Her entire data layer runs on OpenStreetMap and a combination of open federal datasets from data.gov. "I genuinely could not have done this with investor money," she says. "Not because investors wouldn't have funded me, but because the moment you take that money, you're optimizing for scale and exit. I was optimizing for usefulness."

Her story isn't unique. Across the US, a quiet generation of builders—many of them outside the traditional tech hubs of San Francisco and New York—are leveraging the digital commons to compress what used to be multi-million-dollar infrastructure costs into a few hundred dollars a month in hosting fees.

This is the hidden economy the headline numbers miss. When analysts measure the "value" of the tech sector, they're largely measuring what's been monetized. The commons, by definition, doesn't show up on a balance sheet.

Protocol Standards: The Unsexy Backbone of Everything

If Wikipedia is the most visible part of the digital commons, protocol standards are the least glamorous—and arguably the most important.

HTTP, SMTP, TCP/IP, RSS, ActivityPub. These aren't products. They're agreements—shared languages that allow software systems to talk to each other regardless of who built them. The internet as we know it is essentially a stack of layered open standards, each one developed through a collaborative (and often contentious) process involving academics, engineers, and standards bodies like the IETF and W3C.

Every time a developer builds a new app that sends an email, loads a webpage, or federates with a social network, they're drawing on decades of collective intellectual work that nobody owns and everybody benefits from.

The recent resurgence of interest in ActivityPub—the protocol behind Mastodon and a growing wave of federated social platforms—is a good example of what happens when builders return to the commons model after years of platform centralization. Developers aren't starting from scratch; they're inheriting a standard that was designed, debated, and documented by a community.

The Sustainability Problem Nobody Wants to Talk About

Here's the uncomfortable part. The digital commons is not self-sustaining by magic. It requires ongoing human labor—developers filing bug reports, contributors updating data, foundations writing grant proposals, and a small army of volunteers doing work that the companies profiting from it rarely compensate.

The Log4Shell vulnerability in 2021 was a wake-up call. A critical security flaw was discovered in Log4j, an open-source Java logging library maintained largely by a handful of volunteers. The library was embedded in software used by thousands of enterprises, including major US government systems. The maintainers were not paid. The companies whose products depended on it were, in many cases, worth billions.

This isn't an isolated story. It's a structural feature of how the commons operates under capitalism—immense value extraction paired with chronic underinvestment in maintenance.

Some organizations are trying to change this. The Open Collective platform allows open-source projects to receive and distribute funding transparently. GitHub Sponsors lets individual developers get paid directly. The Sovereign Tech Fund in Germany (and similar efforts being discussed in US policy circles) explores public investment in open digital infrastructure the same way governments fund roads and bridges.

What Would Honest Accounting Look Like?

If you wanted to actually price the digital commons into the economy, you'd need a framework that doesn't currently exist in mainstream finance. Some researchers have tried. Estimates of Wikipedia's "replacement value"—what it would cost to produce the same information commercially—run into the hundreds of billions of dollars. OSM's data, if licensed commercially, would cost most startups more than their entire operating budget.

The point isn't to monetize these resources. It's to make visible what's currently invisible—and to build a culture in the tech industry where contributing back to shared infrastructure is treated as a genuine business responsibility, not a PR exercise.

For builders reading this: the next time you pull a library from npm, query an open API, or base a product on a publicly maintained dataset, take a second to think about what that's worth to you. Then ask whether there's a way to give something back—time, money, documentation, bug fixes.

The commons got built by people who believed in collective progress. Keeping it alive requires the same belief—and a little more intentional action from those who've benefited most.

---

Have you built something meaningful on open infrastructure? We'd love to hear your story. Find us at netbux.org or drop us a note on our community forum.