01
Nostr
Nostr is an open protocol for signed events. Your account is your keypair, not a username in one company database.
Beginner friendly guide
What are Nostr, Nsites, and gateways?
If you are new to this stack, this page gives the practical mental model for how a sovereign storefront appears online.
02
Nsite
An Nsite is site content and metadata published over Nostr-compatible rails. It can be cloned to another key and updated without platform lock-in.
03
Gateway
A gateway is the web-facing domain that resolves Nsite data into regular HTTP pages, such as *.nsite.cloud, *.nsite.run, and *.nsite.lol.
Tips for managing and key safety
Treat your key like the password to your store. Keep it private, backed up, and controlled.
Safety checklist
- - Clear your clipboard after copying your key.
- - Store your key in a secure password manager.
- - Keep backup copies in separate safe places.
- - Never paste your nsec into unknown websites.
Browser signer (Nos2x)
Use a browser extension signer so websites can request signatures without directly handling your key.
Simple flow
- 1. Merchant controls a Nostr keypair.
- 2. Merchant publishes storefront manifest and content pointers.
- 3. Relays and servers distribute the data.
- 4. Gateway resolves and renders the storefront for browsers.
Why it matters
- - Lower platform dependence.
- - Easier migration and cloning.
- - User-owned merchant identity.
- - Open ecosystem interoperability.