Every relay.
None of the spam.

rly9 listens to hundreds of nostr relays at once and keeps only events from people with a real profile. Add one relay and read the whole network, clean.

21,000 sats a year

Paid over lightning. No account, no email.

Live71 relays connected
Events stored
3,701
Real authors
244
Spam dropped
2,332
Spam dropped counts events refused since the fetcher last started.

How every event is checked

  1. 1

    Collected

    rly9 keeps a live subscription open on the most-used online relays from profilestr's live list, so new notes arrive within seconds.

  2. 2

    Checked

    The author's pubkey is looked up on profilestr. No indexed profile means no human behind it, so the event is dropped as likely spam.

  3. 3

    Verified

    The id and signature are checked. Forged and malformed events never reach the database.

  4. 4

    Served

    Clean events are stored in Postgres and streamed to subscribers live, with replaceable events, deletions and expiry handled.

Set up in a minute

  1. 01

    Pay for your npub

    Enter your npub and pay a lightning invoice. Anyone can pay for anyone.

  2. 02

    Add rly8.com

    Put it in your client's relay list. When the client asks to authenticate, allow it: that's how rly9 knows you subscribe.

  3. 03

    Read and post

    Your feeds fill from the whole network without the bots. What you post is stored here and served to every other subscriber.

21,000 sats a year

Your subscription belongs to your pubkey. Paying needs no sign-in: only your key can authenticate as you, so paying for an npub is safe even if it's someone else's.

  • Read everything rly9 has collected, live and history.
  • Publish your own events, stored and served to every subscriber.
  • Renewing adds a year to the time you have left.

Subscribe or check your status

Client setup and limits

Which NIPs rly9 supports, how authentication works, what is kept and for how long.

Read the docs