Nostr Relay

Nostr relay is a simple server that accepts, stores, and forwards the cryptographically signed messages — events — that make up the Nostr network. Relays are deliberately "dumb": they hold signed events and serve them to clients that ask, but they cannot create, alter, or forge messages on your behalf, because they never hold your private key. Every event is signed by its author's key and verified by every client that receives it, so a malicious relay's worst powers are refusing to store, refusing to serve, or serving stale data — all of which are defeated by the standard practice of connecting to several relays at once.

How relays actually work

The protocol is minimal by design: a relay speaks WebSocket and understands a handful of verbs — clients publish events, subscribe with filters (by author, by event kind, by time range, by tag), and receive matching events as they arrive. There is no server-side timeline algorithm, no account system, no federation handshake between relays. Relays do not even need to talk to each other; clients bridge the network by reading from and writing to multiple relays simultaneously. This radical simplicity is a survival trait: a relay can be implemented in a weekend, audited in an afternoon, and run by anyone — which is precisely what makes the network hard to capture.

Running your own relay

Relay software is lightweight enough to run on a Raspberry Pi, a home server, or alongside a Bitcoin full node — popular implementations run comfortably in a few hundred megabytes of RAM with modest disk. Running your own relay means a permanent copy of your notes lives on hardware you control, immune to any third party's moderation decisions, business failures, or database purges. It also lets you set policy: a private relay for your family or team, a paid relay to filter spam, an archive relay that keeps everything you have ever published. The storage math is friendly, too: text events are small, so even years of a personal feed occupy megabytes rather than gigabytes — media is typically hosted separately, with events carrying only links — and the relay's database backs up like any other file. Start with one of the mature implementations behind a reverse proxy with TLS, and you have durable, censorship-resistant storage for your public life in an afternoon. Many sovereign Bitcoiners pair a personal relay with their node so that both their money and their speech depend on infrastructure they own — and back up their nsec with the same discipline as a seed phrase, since the key, not the relay, is the identity.

Why relays decentralize the network

There is no master relay, no directory of "approved" servers, no committee that admits new ones. This is the key difference from federated networks, where servers must peer with each other and de-federation is a censorship tool: on Nostr, anyone can stand up a relay, and clients route around hostile or offline servers automatically — your identity and social graph travel with your keys, not with any server. Censorship therefore requires suppressing every relay a user can reach, including ones they run themselves behind their own router. The more independently operated relays exist, in more jurisdictions, on more kinds of hardware, the more that suppression cost diverges toward impossible. Each new self-hosted relay is one more layer of the communications stack decentralized — the same one-layer-at-a-time project that running a node advances for money.

D-Central's sovereign self-hosting catalog covers relay options alongside other self-hosted services.

See relevant NIPs in the Nostr NIPs reference (94).

Full open-data reference: Nostr Relay Implementations — CSV / JSON + REST API, CC BY 4.0.