95% of Nostr Relays Can't Cover Costs. Here's Why That Matters.
Source: Dev.to
Running on Faith
You run a relay because you believe in something: censorship resistance, permissionless publishing, a social protocol that nobody controls. You set it up on a VPS, configure the software, open the WebSocket port, and tell people to add your URL.
And then the bills came.
You’re not alone. Roughly 95 % of Nostr relays cannot cover their operational costs. Of over 1,000 tracked relays, 343 have already gone dark. The rest are held together by goodwill, side‑projects, and the stubborn hope that something will change.
This article isn’t about selling you a solution. It’s about understanding why the problem is structural — and why fixing it matters for the future of the protocol.
The Network Is Healthy. The Infrastructure Isn’t.
As of early 2026, the Nostr network has grown to over 315,000 profiles with bios or contact lists. More than 228,000 daily events flow across 178+ relays, each hosting at least 5 % of the network’s content. In total, over 11 million events have been published. Jack Dorsey’s $10 million donation signals that serious stakeholders are taking this protocol seriously.
Demand side:
- People are publishing.
- People are reading.
- Clients are improving.
- NIPs are evolving.
- The protocol is alive.
Infrastructure layer:
- The relays that store and serve all this data are in trouble.
- A third of all tracked relays have gone offline.
- Most of the remaining relays are subsidized by their operators’ other income.
- Running a relay is, for most people, a volunteer activity.
The question isn’t whether Nostr works—it does. The question is whether its infrastructure can survive contact with economic reality.
The Models That Exist Today
The Nostr community isn’t ignoring the relay‑funding problem. Several paid‑relay models have emerged, each taking a different approach.
Subscriptions – nostr.wine
| Feature | Details |
|---|---|
| Price | ≈ $7 / month |
| Auth | NIP‑42 authentication for DM privacy |
| Infrastructure | Regional mirrors in the US, Finland, and Japan |
| Search | Full‑text search via NIP‑50 |
| Optional filter | filter.nostr.wine – 10 000 sats / month to filter the global firehose to your contacts (requires a nostr.wine membership) |
Pros: Works for power users who want premium features.
Cons: Creates a two‑tier system—those who can afford better relay service versus everyone else.
One‑Time Payments – expensive-relay & nerostr
| Relay | Payment Method | Notes |
|---|---|---|
expensive-relay | Single Lightning payment (whitelists a public key) | Reference implementation by Fiatjaf, Nostr’s creator. GitHub |
nerostr | Single Monero payment (whitelists a public key) | GitHub |
Problem: One‑time payments don’t scale with ongoing costs (bandwidth, storage, compute). A payment covers day 1, not month 6.
Free Relays – The Majority
Most relays are free, often supported by donations. A few run on low‑cost platforms such as Cloudflare Workers (e.g., Nosflare) to keep expenses minimal.
Challenge: As the network grows, operational costs rise, and there’s no built‑in mechanism to fund these relays beyond the operator’s personal wallet.
Why None of Them Scale
Each model has merit, but they share a structural limitation: they don’t align payment with the thing that actually costs money.
What costs money on a relay? Writes
- Every stored event consumes disk space, indexing overhead, and bandwidth when later retrieved.
- Reads are cheap – serving cached data is what commodity infrastructure does well.
- Writes are expensive – they require validation, storage, and propagation.
Problems with current pricing models
- Subscriptions charge a flat fee regardless of how much you write. Heavy writers subsidize light users, and light users may not subscribe because the value proposition isn’t clear enough.
- One‑time payments create the same mis‑alignment: a user who writes 10 000 events pays the same as one who writes 10.
- Free relays absorb the cost entirely, which works until it doesn’t – as the 343 offline relays demonstrate.
The structural problem is this: Nostr’s economic model lacks a built‑in mechanism for the people who create costs to bear those costs. The protocol is beautifully designed for censorship resistance and client portability, but it has no native concept of “this event costs something to store.”
Imagine if email servers had no business model. That’s where Nostr relays are today.
Why This Matters Beyond Relay Operators
This isn’t just a relay‑operator problem; it’s a protocol‑level risk.
- Censorship resistance depends on relay diversity. If you can add your events to dozens of independent relays, no single authority can silence you.
- If most relays can’t sustain themselves, the network consolidates around a few well‑funded operators. That’s not censorship resistance – it’s a different kind of centralization.
The math is uncomfortable: an 82.5 % growth in Lightning‑addressed Nostr profiles shows the community is increasingly comfortable with payments. People are zapping posts and sending sats to content creators. The willingness to pay is there, but the payment layer and the relay‑infrastructure layer aren’t connected.
- Zaps reward content creators.
- Nobody zaps a relay.
There’s a gap between “I’ll pay for content I like” and “the infrastructure that delivers this content needs funding.” Until that gap closes, relay operators will continue to subsidize the network out of their own pockets—until they can’t anymore.
“Nostr will only scale if it can incentivize users to run relays.” – Nasdaq
The broader tech world is watching, and they see the same problem we do.
The Question
This article doesn’t have a product to pitch, but it does have a question:
What if the protocol itself could make relays economically viable?
Not through donations, not through subscriptions, and not through one‑time payments that don’t align with ongoing costs. Instead, imagine a model where the act of writing to a relay—the very action that costs the relay money—also funds it.
- Pay per write
- Free to read
The protocol already separates event creation from event storage: clients sign events, relays store them. What if that boundary were also an economic boundary?
That’s not a rhetorical question—people are already working on it. Regardless of the approach, the Nostr community needs to have this conversation, because the current trajectory—where 95 % of relays run at a loss and a third have already shut down—is not sustainable.
The protocol works. Now it needs to survive.
If you operate a relay, I’d love to hear about your experience with costs, revenue experiments, and what you think a sustainable model looks like. The conversation matters more than any single solution.