A Thousand Red Hats

Listen to this Article

In 1993, a small company called Red Hat began selling support, documentation, and deployment expertise around Linux — software that anyone could download for free. By 1999, Red Hat's IPO raised $84 million in a single day. The code was free. The market wasn't.

This dynamic is about to repeat itself, potentially dozens of times over, thanks to an unusual licensing strategy employed by the Network Theory Applied Research Institute (NTARI). Understanding why requires a brief detour into the nature of public land.

The Permanent Commons

When the U.S. government opened the Oklahoma Territory to settlement in 1889, the land was free. There were no purchase prices, no licensing fees. What wasn't free was time. The settlers who staked their claims earliest built the farms, the towns, the infrastructure. Latecomers could settle too — but the best land was gone, the supply chains were established, and the reputations were earned. The land was a commons. The advantage was not.

NTARI operates on the same principle, encoded in law.

All software developed under NTARI's organizational framework is released under the GNU Affero General Public License version 3.0 (AGPL-3). Under this license, anyone on earth can download, deploy, and build commercial businesses on NTARI's software — for free, with no royalties, no licensing calls, no permission required. The code is public land.

But AGPL-3 contains a crucial provision that standard open-source licenses do not: network copyleft. Under AGPL-3, any organization that deploys NTARI software as a networked service must release their modifications back to the public under the same terms. You can build a profitable business on it. You cannot privately enclose it. Every improvement returns to the commons, available to everyone — including your competitors.

This is not a loophole. It is the design.

What NTARI Is Actually Building

To understand the opportunity, it helps to know what NTARI is releasing into this commons.

SoHoLINK is a federated compute marketplace that turns idle home and small office hardware — desktops, NAS devices, mini-PCs — into income-generating compute nodes. It features a Kubernetes-inspired scheduler, dual-rail payments via Stripe and the Lightning Network, ML-driven load balancing, and a 3D globe visualization of the network. It is, in short, a community-owned alternative to AWS — with a 1% platform fee, structured to route approximately 97% of revenue directly to hardware providers.

Agrinet is a decentralized agricultural trading platform connecting producers, consumers, and service providers with transparent supply chains, contract markets, cooperative coordination, and SMS access for users without reliable internet. It applies platform cooperative principles to food systems — markets where information asymmetry has historically extracted value from the people doing the growing.

The Janus Facing Application framework provides the architectural blueprint for transforming any extractive platform — ridesharing, delivery, housing coordination, care services — into a democratic cooperative with full algorithmic transparency, role-switching capability, and integrated governance. Municipalities can use clean-room development methodology to legally recreate the coordination functions of proprietary platforms, release them under AGPL-3, and deploy them as community-owned infrastructure.

All of it is free to deploy. All of it is permanently free to deploy.

The First-Mover Advantage That Can't Be Unlicensed Away

Here is the structural reality that NTARI's licensing strategy creates, and why it differs from every conventional software market:

In a proprietary software market, the moat is the license. Competitors are legally excluded. The code is the barrier.

In a permissive open-source market (MIT, BSD, Apache), there is no moat at all. A well-funded competitor can take your code, build a proprietary product, and out-market you with your own work.

NTARI's AGPL-3 strategy creates a third structure: a market where the code is free but corporate enclosure is structurally impossible. A large technology company cannot fork SoHoLINK, build a proprietary version, and dominate the market — because deploying it as a network service requires releasing all modifications. The AGPL-3, as NTARI's own documents describe it, functions as "an immune system against corporate capture." Incorporating AGPL-3 code into a proprietary product requires opening the entire platform.

This is what discourages the well-capitalized incumbents — and what creates the window for first movers.

The organization or entrepreneur who deploys SoHoLINK in their region first builds the node operator relationships, the customer trust, the operational expertise, and the local reputation. A later entrant can deploy the identical codebase — but they cannot buy those relationships or that reputation. The code is shared. The market position is not.

This is not theoretical. It is the mechanism by which Red Hat became a billion-dollar company on top of free software. It is how Canonical built Ubuntu's enterprise business. It is how Automattic built WordPress.com. The pattern is consistent across three decades of open-source economics: expertise, relationships, and deployment timing compound in ways that code access alone cannot replicate.

NTARI is not releasing one Linux. It is releasing infrastructure for federated compute markets, agricultural coordination networks, platform cooperatives for transportation and care services, and civic information infrastructure. Each represents a distinct market. Each represents a distinct first-mover opportunity. Each is governed by the same permanent commons principle.

The Compounding Improvement Problem

There is a second dynamic at work that makes early deployment particularly valuable, and it runs in both directions.

Under AGPL-3's network copyleft provision, every modification a deployer makes to the software must be released back to the commons. This means that every early deployer's improvements — every bug fix, every performance optimization, every feature built for their specific market — becomes available to all subsequent deployers.

From a competitive standpoint, this might sound like giving away your advantage. In practice, it means something different: early deployers shape what the commons becomes. The organization that deploys Agrinet first in a given agricultural region, encounters the real-world friction points of that market, and fixes them — has contributed to a codebase that is now demonstrably better for their region than what existed before. They have the operational experience. They have the customer relationships built during that improvement process. And their improvements are returned to a commons that now validates their expertise and implementation approach as the reference standard.

Late entrants inherit better software, but they also inherit the reputation framework established by those who built it.

What This Is Not

It is worth being precise about what distinguishes this from extractive platform economics, because the distinction is not merely rhetorical — it is structural.

In conventional platform markets (Uber, Amazon, DoorDash), early advantage compounds through network effects that are deliberately designed to exclude competitors and extract value from participants. The platform captures the surplus. Participants — drivers, sellers, farmers — receive diminishing returns as the platform's market position strengthens.

NTARI's model inverts this at the architectural level. The platforms built on NTARI infrastructure are designed as Janus Facing Applications: all pricing, matching algorithms, and platform economics are transparent to all participants. Democratic governance is built into the architecture. Value circulates within communities rather than extracting to distant shareholders.

Early deployers gain market advantage, but they gain it by building genuine service relationships in a transparent system — not by engineering information asymmetry. Their competitors, when they arrive, operate under the same transparency requirements. No one can build a proprietary moat on NTARI infrastructure. The immune system prevents it.

This is also why NTARI's enforcement philosophy is explicitly cooperative rather than punitive. When organizations use NTARI software without AGPL-3 compliance, NTARI's preferred resolution is not litigation — it is cooperative membership. The goal is not to extract penalties but to expand the network of organizations operating cooperative infrastructure. Violators are invited to become participants.

The Window

Red Hat's opportunity existed because Linux was mature enough to deploy commercially but not yet widely deployed by service businesses. The window was a gap between technical availability and market saturation — a gap that took time, expertise, and risk tolerance to cross.

NTARI's software is in an analogous position. SoHoLINK exists. Agrinet exists. The Janus Facing Architecture framework exists. The licenses are in place. The preservation infrastructure is built. The code is on GitHub, GitLab, Docker Hub, the Internet Archive, and the Software Heritage permanent archive.

The market deployments are not.

That gap is the opportunity. The organizations and entrepreneurs who cross it first — who build the regional compute cooperatives, the agricultural coordination networks, the municipal platform alternatives — are building on infrastructure that cannot be enclosed, in markets that cannot be licensed away from them, with improvements that return to a commons they helped shape.

Dozens of Red Hats are possible. The land is open. The clock is running.

The Network Theory Applied Research Institute develops open-source cooperative infrastructure under AGPL-3 licensing. For licensing and policy questions, contact info@ntari.org. For technical inquiries, contact tech@ntari.org.