The whole shelf lives here: source audits, deep research, app maps, NIP references, field guides, long reads and the routes that keep a huge archive actually usable.
Our archive of major Nostr apps, clients, signers, discovery services, media tools and developer libraries.
Nostr becomes understandable when the protocol is connected to actual products. This index maps the clients and tools that readers will encounter in the Nostr universe.
The quick readOur archive of major Nostr apps, clients, signers, discovery services, media tools and developer libraries.
Nostr App and Tool Profiles: a research-and-archive scene for the Nostr atlas.Nostr App and Tool Profiles: a research-and-archive scene for the Nostr atlas.
How to use this app archive
This is not a ranking and not an endorsement list. It is a structured map. Some projects are consumer clients, some are developertools, some are mediaapps and some are signer or infrastructure products.
The main lesson for us is that the same protocol can support very different surfaces. we should therefore be a focused Crays-facing client, not a generic clone of existing apps.
Nostr App and Tool Profiles belongs to the research and source material layer. The page should help you answer one concrete question instead of forcing you through a generic Nostr essay.
The short version is: our archive of major Nostr apps, clients, signers, discovery services, mediatools and developer libraries. The deeper version is to see which concept, standard, product surface or human decision actually changes because of it.
Evidence quality
The useful machinery around Nostr App and Tool Profiles 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 app-profiles 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.
Source type. Standard, repo, monitor, directory, essay or research paper?
Claim. What claim does this source support?
Next use. Which article should absorb the insight?
Nostr App and Tool Profiles: a research-and-archive scene for the Nostr atlas.Nostr App and Tool Profiles: a research-and-archive scene for the Nostr atlas.
What it can verify
Test Nostr App and Tool Profiles 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 app-profiles 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.
What it does not prove
In the app-profiles 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 app-profiles 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.
Where the knowledge should feed
For us, Nostr App and Tool Profiles 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 app-profiles 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.
Library path around it
The best next step from Nostr App and Tool Profiles is not a generic link pile. Connect it to the closest prerequisite, the closest technical standard and the closest practical example.
In the app-profiles 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.
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.
