Nostr Operators
The people who keep the relays running.
NostrOps is short for Nostr Operators: administrators of Nostr relay servers. Relays store and forward signed events. Operators decide what lives, who can write, and whether the lights stay on.
The job
A relay is a small program. Running one is not a small job.
Nostr has no central server. Clients publish signed events to
relays over WebSockets (wss://), and other clients
fetch them back. Anyone can run a relay. The network’s resilience
depends on people who actually do.
Operators set persistence, access policy, and uptime. Users can switch relays freely — that is the point — but a note that is not stored anywhere is gone. A personal relay is the identity-layer equivalent of running your own node: you stop hoping a public inbox will keep your archive.
This site is a field guide, not a vendor pitch. It synthesizes what production operators, NIP authors, and relay implementers have written about the work.
The guide
Start where the work is.
Six chapters. Read them in order, or jump to the pressure you already feel.
Concerns
Spam, disk growth, policy, jurisdiction, the commons, and admin surfaces.
02Relay types
Personal, community, paid public, specialized. Start restrictive.
03Practices
TLS, NIP-11, ingest filters, backups, systemd, and a restore runbook.
04Software
strfry, nostr-rs-relay, nostream, and the rest of the production set.
05NIPs
The protocol surface that belongs on an operator’s desk, not a client’s.
06Sources
NIPs and production guides this site synthesizes. Read them before you copy a config.