Nostr Apps Directory Guide
How to understand the Nostr app ecosystem: social clients, publishing, search, relays, media, wallets, developer tools and creator products.
The Nostr app ecosystem is not one product category. It is a set of clients and services that use the same identity and event substrate for different experiences.
App categories to know
Nostr Apps and Awesome Nostr show how wide the ecosystem already is. You will find social clients, mobile clients, desktop clients, long-form publishing tools, relay tools, search tools, chat apps, live-streaming experiments, music products, marketplaces, file tools, wallets and developer libraries.
- Social clients. Damus, Amethyst, Primal, Nos, Nostur, Coracle, Snort, Iris, Nostrudel and YakiHonne.
- Writing. Habla, YakiHonne and long-form NIP-23-oriented tools.
- Media. Wavlake, live-streaming tools and file metadata experiments.
- Infrastructure. Relay dashboards, server tools, signing tools and libraries.
What directories are good for
Directories are not endorsements. They are discovery maps. Use them to understand what builders are attempting, which categories are crowded and where the ecosystem still has missing product quality.
How we should read the app market
We should not copy generic social clients. It should learn from them and build a purpose-specific Crays client layer: profile, creator monetization, fan access, award voting, venue routing and reputation.
App profile index
The app archive breaks major clients and tools into their own pages so readers can move from broad categories into concrete examples.
CraysCrays Nostr client and ecosystem front door. we are the Crays-facing Nostr surface: profile, creator access, status, venues, awards, payments and portable identity in one lifestyle layer.
What job this product does
Nostr Apps Directory Guide belongs to the clients, tools and interfaces layer. The page should help you answer one concrete question instead of forcing you through a generic Nostr essay.
The short version is: How to understand the Nostr app ecosystem: social clients, publishing, search, relays, media, wallets, developer tools and creator products. The deeper version is to see which concept, standard, product surface or human decision actually changes because of it.
Key and signer behavior
The useful machinery around Nostr Apps Directory Guide is client UX, signer safety, relay defaults, platform limits and supported NIPs. Name those moving parts directly, because vague protocol language is where confusion starts.
In the apps chapter, A strong page gives you enough context to recognize the term in another client, NIP, relay policy, wallet prompt or source document without pretending every reader is already a protocol engineer.
- Identity. Does it use a signer, raw key, remote signer or account wrapper?
- Relays. Can you see where reads and writes go?
- Exit. What remains usable in another client?
Relay and data assumptions
Test Nostr Apps Directory Guide by asking what is signed, where it is stored, who renders it, which relays or services are involved and what survives when the first app or server is unavailable.
In the apps chapter, That test keeps the explanation tied to reality. It also tells us which internal links belong in the body: foundations first, then standards, then practical examples.
NIPs and services to check
In the apps chapter, The main risk is that a polished interface can still hide weak custody, weak relay handling or limited interoperability. The page should say that plainly and then show the safer reading: what works today, what is experimental and what needs source verification.
In the apps chapter, This is where dense content beats long content. Give the reader facts, constraints, examples and next steps instead of repeating broad claims about openness or decentralization.
Interoperability test
For us, Nostr Apps Directory Guide matters only when it improves understanding or helps a real flow: identity, publishing, relay choice, signing, payment, media, moderation, commerce, venue context or governance.
In the apps chapter, That does not mean every page has to become our product pitch. It means the page should make the connection visible when the topic affects our ecosystem, and stay purely educational when it does not.
Where it sits in the app map
The best next step from Nostr Apps Directory Guide is not a generic link pile. Connect it to the closest prerequisite, the closest technical standard and the closest practical example.
In the apps chapter, A large archive becomes useful when every page behaves like a node in a knowledge graph: this explains one thing, points to what it depends on and shows where the idea is used.
Read next from Nostr Apps Directory Guide
Complete Nostr Apps CatalogApps and clients
Apps and ProductsApps hub
Nostr App and Tool ProfilesApps and clients
Nostr ClientsApps and clients
Nostr Developer ToolsApps and clients
People and UsersPeople hub
Nostr Resources and LinksResearch map
NIP-47: Nostr Wallet ConnectProtocol and NIPs
Nostr Keys and IdentityCore concepts
NIP-07: Browser SignersProtocol and NIPs