--- title: "Nosflare FAQ" description: "Answers to common questions about Nosflare: what it is, what it costs, how long deployment takes, storage limits, supported NIPs, and whether coding is required." canonical: "https://nosflare.com/docs/faq.md" --- # Frequently Asked Questions ## What is Nosflare? Nosflare is a serverless [Nostr](https://github.com/nostr-protocol/nips) relay built for Cloudflare Workers, Cloudflare D1 (SQLite at the edge), and Durable Objects. It lets anyone run a Nostr relay without a server, scaling automatically across 300+ Cloudflare edge locations. It is open source under the MIT license. ## Do I need to know how to code to run a relay? No. [Nosflare Deploy](https://deploy.nosflare.com) is a one-click, no-code deployment for a one-time fee of 21,420 sats. It provisions a fully customized relay onto your own Cloudflare account in under a minute, and you can keep updating it afterwards at no extra cost. Developers can instead fork the repository and deploy manually. ## How long does deployment take? Under one minute with one-click deploy. A manual deployment - configure `src/config.ts`, run `npm run build`, create a D1 database, create the Worker, bind the database, and add a custom domain - typically takes 15-30 minutes the first time. ## What does it cost to run? The one-click deploy is a one-time 21,420 sats. After that you pay only Cloudflare usage for Workers, Durable Objects, and D1. Nosflare typically costs 75-90% less than traditional relay hosting because it bills for use rather than for provisioned capacity. See [Pricing](https://nosflare.com/docs/pricing.md). ## Can I charge people to use my relay? Yes. Pay-to-relay is built in and enabled by default. You set a price in sats and an npub to receive payments; access is paid over the Bitcoin Lightning Network through Nostr zaps, and payment verification is automatic. See [Pay-to-relay](https://nosflare.com/docs/pay-to-relay.md). ## Which NIPs does Nosflare support? 19 NIPs: 1, 2, 4, 5, 9, 11, 12, 13, 15, 16, 17, 20, 22, 25, 28, 33, 40, 42, and 57. NIP-50 (search) and NIP-65 (relay lists) are on the roadmap. See [Supported NIPs](https://nosflare.com/docs/supported-nips.md). ## How much data can the relay store? A Cloudflare D1 database provides up to 10 GB of storage. D1 read replication is used to place read-only copies of the database near clients, which lowers read latency and scales read throughput. ## How does it handle real-time event delivery? Client WebSocket connections are held by Durable Objects using the WebSocket Hibernation API, arranged as a multi-regional mesh across 9 locations. New events are broadcast across the mesh, so real-time delivery is not bottlenecked on a single Durable Object location, and idle-but-connected clients do not accrue Duration charges. ## How does Nosflare stop spam? Several independent layers: optional NIP-05 address validation with domain allow/blocklists, content hashing to reject duplicate events (per-pubkey or globally), rate limiting per pubkey, blocked words and phrases, and allowlists or blocklists for pubkeys, event kinds, and tags. Enabling pay-to-relay also puts a hard cost on write access. See [Anti-spam](https://nosflare.com/docs/anti-spam.md). ## Can I try a Nosflare relay without deploying one? Yes. Add `wss://relay.nosflare.com` to your Nostr client's relay list. It is a live, paid instance of this relay implementation. ## Is Nosflare open source? Yes, MIT licensed, at https://github.com/Spl0itable/nosflare. Issues, feature requests, and pull requests are welcome. ## Who maintains Nosflare? Nosflare is maintained by [21 Million LLC](https://nostrservices.com). You can reach the maintainer through GitHub Discussions or on Nostr at `npub16jdfqgazrkapk0yrqm9rdxlnys7ck39c7zmdzxtxqlmmpxg04r0sd733sv`. ## What is the "Send It" blaster? `wss://sendit.nosflare.com` is a companion relay, included in the repository as `send-it.js`, that rebroadcasts a note to as many online relays as possible using NIP-66 relay discovery.