[{"data":1,"prerenderedAt":268},["ShallowReactive",2],{"blog-\u002Fblog\u002Fnostrfi-relay-0-2-0":3},{"id":4,"title":5,"author":6,"body":7,"date":253,"description":254,"draft":255,"extension":256,"lastReviewed":253,"meta":257,"navigation":258,"owner":6,"path":259,"seo":260,"sitemap":261,"stem":262,"tags":263,"__hash__":267},"blog\u002Fblog\u002Fnostrfi-relay-0-2-0.md","Nostrfi Relay 0.2.0: run your own Nostr relay and see what it is doing","Nostrfi",{"type":8,"value":9,"toc":243},"minimark",[10,14,25,30,33,36,40,62,65,69,135,139,163,171,175,178,209,222,226,233],[11,12,13],"p",{},"Nostrfi Relay is a self-operable Nostr relay with an operator dashboard.\nVersion 0.2.0 is released, it is open source, and Nostrfi runs it in\nproduction. Anyone can run it today.",[15,16,18],"callout",{"type":17},"info",[11,19,20,24],{},[21,22,23],"strong",{},"Released (v0.2.0) and running in production."," Before 1.0, a release may\nstill change configuration between versions.",[26,27,29],"h2",{"id":28},"why-we-built-it","Why we built it",[11,31,32],{},"Starting a Nostr relay is easy. Operating one well is harder. An operator has\nto get protocol compatibility, storage, moderation, rate limits, monitoring,\nbackups and capacity right, often without much visibility into what the relay\nis actually doing. Who is connected? What is being stored? What was rejected,\nand why? How much headroom is left? Will the backup restore?",[11,34,35],{},"Nostrfi Relay is built to answer those questions. It pairs a compatible relay\nwith a dashboard for the person who runs it.",[26,37,39],{"id":38},"who-it-is-for","Who it is for",[41,42,43,50,56],"ul",{},[44,45,46,49],"li",{},[21,47,48],{},"Client and app teams"," that need a relay they control, for availability,\ndata policy or interoperability testing.",[44,51,52,55],{},[21,53,54],{},"Communities and organisations"," that want their own relay with their own\nmoderation and retention rules.",[44,57,58,61],{},[21,59,60],{},"Individual operators"," running public relay infrastructure.",[11,63,64],{},"If you are looking for a Nostr client or a hosted account, this is not it.",[26,66,68],{"id":67},"what-you-get","What you get",[41,70,71,83,94,104,114,124],{},[44,72,73,76,77,82],{},[21,74,75],{},"A relay that works with compatible Nostr clients."," It supports NIP-01, 02,\n09, 11, 17, 22, 28, 40, 42, 50, 70, 71, 77, 86 and 98, including NIP-42\nauthentication, NIP-50 search and NIP-77 Negentropy sync. The\n",[78,79,81],"a",{"href":80},"\u002Fdocs\u002Frelay\u002Freference\u002Fprotocol-support","protocol support"," page states the\nlimits and what is still being tested.",[44,84,85,88,89,93],{},[21,86,87],{},"An operator dashboard"," you sign in to with your own Nostr key, through a\nNIP-07 or NIP-46 signer. It shows live connections, rates and rejections,\nstored events by period and kind, and the configuration the relay is actually\nenforcing. See the ",[78,90,92],{"href":91},"\u002Fdocs\u002Frelay\u002Foperations\u002Fadmin-dashboard","admin dashboard",".",[44,95,96,99,100,93],{},[21,97,98],{},"An event browser"," for finding stored events by kind, author, content,\ntime range and tags. See the ",[78,101,103],{"href":102},"\u002Fdocs\u002Frelay\u002Foperations\u002Fevent-browser","event browser",[44,105,106,109,110,93],{},[21,107,108],{},"Moderation through NIP-86."," Ban pubkeys and events, and block IPs, from\nthe dashboard or any NIP-86 client. See\n",[78,111,113],{"href":112},"\u002Fdocs\u002Frelay\u002Foperations\u002Fmoderation","moderation",[44,115,116,119,120,93],{},[21,117,118],{},"Backups you can check."," A restore is checked against row counts, not\nassumed. See ",[78,121,123],{"href":122},"\u002Fdocs\u002Frelay\u002Foperations\u002Fbackup-and-retention","backup and retention",[44,125,126,129,130,134],{},[21,127,128],{},"Measured capacity."," The ",[78,131,133],{"href":132},"\u002Fdocs\u002Frelay\u002Foperations\u002Fcapacity","capacity page","\npublishes memory and throughput figures from load tests in a development\nsandbox, and how to reproduce them on your own hardware.",[26,136,138],{"id":137},"what-is-new-in-020","What is new in 0.2.0",[41,140,141,144,147],{},[44,142,143],{},"The event browser filters by several tags at once, including multi-letter\ntags.",[44,145,146],{},"The Overview and Metrics pages show relay status and uptime at a glance.",[44,148,149,150,154,155,158,159,162],{},"The relay answers every NIP-42 ",[151,152,153],"code",{},"AUTH"," message with an ",[151,156,157],{},"OK",", so clients that\nwait for it, such as ",[151,160,161],{},"nak"," and go-nostr, no longer time out.",[11,164,165,166,170],{},"The ",[78,167,169],{"href":168},"\u002Fdocs\u002Frelay\u002Fchangelog","changelog"," has the details for operators.",[26,172,174],{"id":173},"what-it-does-not-do-yet","What it does not do yet",[11,176,177],{},"We publish the limits as well as the features. The main ones today:",[41,179,180,187,192,203],{},[44,181,182,183,186],{},"It runs as a ",[21,184,185],{},"single instance",", by design. Nostr gets its redundancy\nfrom clients using several relays, so most operators never need to scale\none out.",[44,188,189],{},[21,190,191],{},"Search results are not ranked.",[44,193,194,195,198,199,202],{},"There is ",[21,196,197],{},"no encryption at rest"," and ",[21,200,201],{},"no TLS in the application",". Put it\nbehind a reverse proxy, as the quickstart does.",[44,204,194,205,208],{},[21,206,207],{},"no service-level objective"," yet.",[11,210,211,212,216,217,221],{},"The full list, with the reasons and any compensating controls, is on the\n",[78,213,215],{"href":214},"\u002Fdocs\u002Frelay\u002Flimitations","current limitations"," page. The\n",[78,218,220],{"href":219},"\u002Fdocs\u002Frelay\u002Fsecurity\u002Ftrust-and-data","trust and data"," page explains what a\nrelay operator can see, and links to the threat model.",[26,223,225],{"id":224},"run-it","Run it",[11,227,165,228,232],{},[78,229,231],{"href":230},"\u002Fdocs\u002Frelay\u002Fgetting-started\u002Fquickstart","quickstart"," takes you from\nnothing to a running relay with its dashboard and TLS, using Docker Compose,\nin about ten minutes. You then sign in with your Nostr key and connect a\nclient.",[11,234,235,236,242],{},"The source is on ",[78,237,241],{"href":238,"rel":239},"https:\u002F\u002Fgithub.com\u002Fnostrfi\u002Frelay",[240],"nofollow","GitHub",". Issues and\nquestions are welcome there.",{"title":244,"searchDepth":245,"depth":245,"links":246},"",2,[247,248,249,250,251,252],{"id":28,"depth":245,"text":29},{"id":38,"depth":245,"text":39},{"id":67,"depth":245,"text":68},{"id":137,"depth":245,"text":138},{"id":173,"depth":245,"text":174},{"id":224,"depth":245,"text":225},"2026-11-16","Nostrfi Relay is a self-operable Nostr relay with an operator dashboard. Version 0.2.0 is released and running in production. Here is what it does, who it is for, and its limits.",false,"md",{},true,"\u002Fblog\u002Fnostrfi-relay-0-2-0",{"title":5,"description":254},{"loc":259,"lastmod":253},"blog\u002Fnostrfi-relay-0-2-0",[264,265,266],"nostr relay","release","nostrfi relay","uXKUz6e1tW0Efb7OVbvEcPB2mR_32lmNcGsYDNPDlg0",1794954745400]