Open-source infrastructure: what the license really gives you

"Open-source" in infrastructure is a floor, not a ceiling: the license guarantees you can read the code, and tells you nothing about who runs it, how it is funded, or whether the network survives its first crisis. The nine live protocols in this population are genuinely open - and they differ wildly in what the openness is worth. This page maps that difference, because "open-source" is the most commonly abused trust signal after "decentralized" - median entry across the population is $0.16, and the honest comparison is never the license; it is the whole stack.

Open-washing: the standard abuse pattern

Because the label works, it gets borrowed [1]. The patterns to check for:

• The stale-repo live-service split - a GitHub org with years-old code in front of a live closed service. The repo is real; the connection is not.
• Open-core where the product is closed - the mining OS is open, the fleet dashboard you actually use is not. Read the boundary before you depend on the label.
• License laundering - "built on open-source" meaning "forked once, closed since." The provenance matters less than the current license of the thing you run.

None of this makes open source weak - it makes verification mandatory, which is the entire spirit of the license anyway.

What the license guarantees - and what it does not

The honest ledger [1][4]:

• A license is auditable. You can verify what the code does - the single strongest anti-scam property in this market, and the reason open-source rows rank well on transparency.
• A license is not an SLA. Uptime, support and incident response are operational choices by whoever runs the network. Crust's documentation is honest about exactly this - engineer-grade docs, no fixed price, no SLA [1].
• A license is not a business model. Open code with no live economics is a museum piece; the scam watch archive is full of open-source fronts with closed treasuries.

The self-hosting dividend

Open clients are what make self-hosting real, and self-hosting is where the license turns into money [4]:

• Mining OS images - an open GPU mining OS is the difference between renting rigs on your terms and trusting a closed dashboard.
• Staking nodes - open validator software means you can hold your own keys; the staking hub prices the custody difference.
• Your own node for critical paths - the endgame of the rpc hub fallback stack is only possible because the node software is open.

The honest comparison is total cost of operation - your time, your hardware, your incident response - against the closed service's bill. Open source is not free; it moves the cost from the invoice to your calendar.

The nine live protocols, sorted honestly

• Ens, Namecoin - naming at opposite poles: deep integration with yearly rent versus company-free with technical setup. Covered in depth in the community-owned hub.
• Lido, Rocket Pool - open-source staking protocols where the license is the least interesting part; the governance and commission structure is the product [4].
• Autonomi - pay-once storage with a published pricing formula and post-quantum ambitions - novel design on a young network [3].
• Walrus - the most transparent pricing in decentralized storage, billing on encoded size - where the encoded-size multiplier makes small files dearer than the headline suggests [2].
• Crust - long-running CRU-paid storage market: honest docs, no SLA, engineer-grade onboarding, and a token at commodity prices - cheap in theory, high-uncertainty in practice [2].
• Space ID - an aggregator over multiple name systems, renewal-based, with pricing that requires contact - open-source where it counts, closed where the business model lives.

Live from our database - caveats and sources in each linked review.

How to verify an open-source claim

Three checks, in order [1]:

1. The repository exists and the license is real - not a README with a LICENSE folder that says "all rights reserved."
2. The running product matches the repo. Version history, recent commits, and the release your instance claims to run. A live service pointing at a stale repo is open-washing.
3. The maintenance signal is alive. Commit history, release cadence, responsive maintainers. Dead code is open-source too - it is just dead. 0 operators in our archive had open repos; the repos survived, the operators did not.

The legit check tool runs the first two automatically. The third - maintenance - is where 90% of this population's rows carry facts we verified ourselves, and where your own read of the commit log is the evidence no ranking can substitute. 10 protocols make the live population; 80% of them need no identity at any point, which is the open-source dividend most people undervalue until they need it.