Community

Apps

Creatr

Creatr is Nostr.wine's creator-access relay at wss://creatr.nostr.wine: exclusive creator notes and media, subscriptions, pay-per-view access, Nostr login, NIP-42 relay auth and policy-heavy paid content.

Creatr icon
Apps route creator access Use it when the reader is mapping creator content, paid access and Nostr-native audience relationships.
Back to Nostr
Apps

Apps shelf

Apps pages collect clients, signers, tools, developer libraries and product research without turning the app into the whole network.

Apps All Apps pages App routeProduct profiles, categories, tools and source links Browse appsClose shelf

App orientation

App categories

App profiles

0xchatadvanced-nostr-searchAegisAlbyAlby GoAlby HubAlby HubAlby SDKAmberAmberAmethystAmethystApp and product researchApplication-specific dataBlossomBlossom spec NIP-B7BookstrBorisBouquetCalendar by FormstrChachiNostr Apps DirectoryCoracleCoracleCorny ChatCreatrDamusDamusDeveloper stack researchDittoDittodiVineDocstrDTANEmojitoFlotillaFlycatFormstrFountainFreeFromFundstrfutrGIF BuddyGittrgo-nostrGossipGossipGrimoireGroups NIP-29HablaHablaHello Nostr — ResourcesHighlighterHiveTalkhomebrew-nostrHORNET StorageHugo2NostrHyperNoteIrisIrisJumblekanbanstrKeys BandListrLNBits NostrmarketLumeLumilumiLUMINAMapstrMarmot Protocolmatrix-nostr-bridgeMeetstrMemestrMindsmonstrmostardMostronaknak — Nostr Army KnifeNalgorithmNarrnashboardNDKNegentropyngitNofluxNosNos Socialnos2xnosbinnosclNostorg Feature MatrixNostr App ManagerNostr Apps Directory GuideNostr clients feature listNostr Compass — ProjectsNostr Developer GuideNostr Development KitNostr Events MonitorNostr MCP ServerNostr NestsNostr PlaygroundNostr Service ProvidersNostr Writernostr-post-checkernostr-protocol/nostrnostr-rubynostr-sdknostr-sdk-ffinostr-sdk-flutternostr-to-rssnostr-toolsNostr.bandnostr.buildnostr.co.uk ClientsNostr.how — Clientsnostr.hsNostrabilityNostrAppsNostrApps category — AudioNostrApps category — CareerNostrApps category — CommunityNostrApps category — CurationNostrApps category — Direct MessageNostrApps category — DiscoveryNostrApps category — File SharingNostrApps category — Group ChatNostrApps category — MeatspaceNostrApps category — OnboardingNostrApps category — SignersNostrApps category — Toolsnostrchecknostrdbnostrdb-rsNostreeNostreonNostriaNostridNostrium / read.nostr.comNostrmoNostrubenoStrudelnoStrudelNostterNosturNosturNotedeckNpub.proNpub.worldnsec.appnsiteNsiteNstart.meObsidian Nostr WriterOlasOpenvibeOracoloOstrich WorkOwn Your PostsP2P BandPazPeridotPhoenixPlebeian MarketPostizPostr / write.nostr.comPrimalPrimalPrimal Article Editor / Reads authoringPrimal Studiopynostrpython-nostrRecommended Application HandlersRelay Toolsrsslayrust-nostrrust-nostr docsSatelliteSatellite EarthSatlantisSatShootShakespeareShopstrSlidestrSnortSnortStemstrswift-nostr-clientTreasuresWavlakeWavlakeWikifreediaWikistrYakiHonneYakiHonneYakiHonne mobile/web app directoryYondar

App pages

Deep dives

Field guides

Awesome Nostr branches

Research and library

Source inventory

Deep Research: Clients, apps and product surfacesDeep Research: Developer stack and toolingResearch Map: nostrapps.comResearch Source: 0xchatResearch Source: 0xchat — NostrApps pageResearch Source: advanced-nostr-searchResearch Source: Aegis — NostrApps pageResearch Source: AlbyResearch Source: Alby — NostrApps pageResearch Source: Alby GoResearch Source: Alby HubResearch Source: Alby Hub GitHubResearch Source: Alby SDKResearch Source: AmberResearch Source: Amber — NostrApps pageResearch Source: AmethystResearch Source: Amethyst GitHubResearch Source: Awesome Nostr ResourcesResearch Source: BookstrResearch Source: BorisResearch Source: Boris — NostrApps pageResearch Source: BouquetResearch Source: Bouquet — NostrApps pageResearch Source: Calendar by FormstrResearch Source: ChachiResearch Source: Chachi — NostrApps pageResearch Source: CoracleResearch Source: Coracle — NostrApps pageResearch Source: Corny ChatResearch Source: DamusResearch Source: Damus — NostrApps pageResearch Source: DittoResearch Source: Ditto — NostrApps pageResearch Source: DocstrResearch Source: DTANResearch Source: DTAN — NostrApps pageResearch Source: EmojitoResearch Source: Emojito — NostrApps pageResearch Source: Flotilla — NostrApps pageResearch Source: FlycatResearch Source: FormstrResearch Source: Formstr — NostrApps pageResearch Source: FountainResearch Source: FreeFromResearch Source: FreeFrom — NostrApps pageResearch Source: FundstrResearch Source: futrResearch Source: futr — NostrApps pageResearch Source: GIF BuddyResearch Source: GIF Buddy — NostrApps pageResearch Source: GittrResearch Source: go-nostr GitHubResearch Source: GossipResearch Source: Gossip — NostrApps pageResearch Source: GrimoireResearch Source: Grimoire — NostrApps pageResearch Source: HablaResearch Source: Habla — NostrApps pageResearch Source: Hello Nostr — ResourcesResearch Source: HighlighterResearch Source: HiveTalkResearch Source: HORNET Storage — NostrCompassResearch Source: IrisResearch Source: Iris — NostrApps pageResearch Source: JumbleResearch Source: Jumble — NostrApps pageResearch Source: Keys BandResearch Source: Keys Band — NostrApps pageResearch Source: ListrResearch Source: LNBits NostrmarketResearch Source: LumeResearch Source: LumilumiResearch Source: LUMINAResearch Source: MapstrResearch Source: Marmot ProtocolResearch Source: MeetstrResearch Source: MemestrResearch Source: MindsResearch Source: monstr GitHubResearch Source: mostardResearch Source: MostroResearch Source: my.nostr.comResearch Source: nak — Nostr Army KnifeResearch Source: nak GitHubResearch Source: NalgorithmResearch Source: Narr — NostrApps pageResearch Source: nashboardResearch Source: NDK GitHubResearch Source: NDK NPMResearch Source: NegentropyResearch Source: Noflux — NostrApps pageResearch Source: Nos SocialResearch Source: Nos Social — NostrApps pageResearch Source: nos2xResearch Source: nos2x — NostrApps pageResearch Source: nosbinResearch Source: noscl GitHubResearch Source: Nostorg Feature MatrixResearch Source: Nostr App ManagerResearch Source: Nostr Book — KindsResearch Source: Nostr DesignResearch Source: Nostr Developer GuideResearch Source: Nostr NestsResearch Source: Nostr Nests — NostrApps pageResearch Source: Nostr PlaygroundResearch Source: nostr-post-checkerResearch Source: nostr-protocol/nostr GitHubResearch Source: nostr-sdk crates.ioResearch Source: nostr-sdk-ffi GitHubResearch Source: nostr-tools GitHubResearch Source: nostr-tools NPMResearch Source: Nostr.BandResearch Source: nostr.buildResearch Source: nostr.co.uk ClientsResearch Source: Nostr.howResearch Source: Nostr.how — ClientsResearch Source: Nostr.how — ProtocolResearch Source: Nostr.how — What is Nostr?Research Source: Nostr.orgResearch Source: NostrabilityResearch Source: NostrAppsResearch Source: NostrApps category — AudioResearch Source: NostrApps category — CareerResearch Source: NostrApps category — CommunityResearch Source: NostrApps category — CurationResearch Source: NostrApps category — Direct MessageResearch Source: NostrApps category — DiscoveryResearch Source: NostrApps category — File SharingResearch Source: NostrApps category — Group ChatResearch Source: NostrApps category — MeatspaceResearch Source: NostrApps category — OnboardingResearch Source: NostrApps category — SignersResearch Source: NostrApps category — ToolsResearch Source: nostrcheckResearch Source: nostrdb GitHubResearch Source: NostreeResearch Source: Nostree — NostrApps pageResearch Source: NostriaResearch Source: Nostria — NostrApps pageResearch Source: NostridResearch Source: Nostrmo — NostrApps pageResearch Source: Nostrmo GitHubResearch Source: NostrubeResearch Source: noStrudelResearch Source: noStrudel — NostrApps pageResearch Source: NostterResearch Source: NosturResearch Source: Nostur — NostrApps pageResearch Source: NotedeckResearch Source: Npub.proResearch Source: Npub.worldResearch Source: nsec.appResearch Source: NsiteResearch Source: Nstart.meResearch Source: Nstart.me — NostrApps pageResearch Source: Obsidian Nostr Writer — NostrApps pageResearch Source: OlasResearch Source: Olas — NostrApps pageResearch Source: OpenvibeResearch Source: OracoloResearch Source: Oracolo — NostrApps pageResearch Source: Ostrich WorkResearch Source: P2P BandResearch Source: PazResearch Source: PeridotResearch Source: Peridot — NostrApps pageResearch Source: PhoenixResearch Source: Phoenix — NostrApps pageResearch Source: Plebeian MarketResearch Source: Plebeian Market — NostrApps pageResearch Source: PrimalResearch Source: Primal — NostrApps pageResearch Source: Primal Article Editor / Reads authoringResearch Source: Primal StudioResearch Source: pynostr GitHubResearch Source: python-nostr GitHubResearch Source: Registry of KindsResearch Source: Relay Tools — NostrApps pageResearch Source: rsslayResearch Source: rust-nostr docsResearch Source: rust-nostr GitHubResearch Source: SatelliteResearch Source: SatShootResearch Source: ShakespeareResearch Source: Shakespeare — NostrApps pageResearch Source: ShopstrResearch Source: Shopstr — NostrApps pageResearch Source: SlidestrResearch Source: SnortResearch Source: start.nostr.netResearch Source: StemstrResearch Source: TreasuresResearch Source: WavlakeResearch Source: WikifreediaResearch Source: Wikifreedia — NostrApps pageResearch Source: WikistrResearch Source: Wikistr — NostrApps pageResearch Source: YakiHonne mobile/web app directoryResearch Source: YondarResearch Source: Yondar — NostrApps page
Apps25 min readcreator subscriptions, paid relay access, NIP-42 auth and exclusive media on Nostr

Creatr

Creatr is the Nostr.wine experiment that asks a blunt question: what happens if creator subscriptions are not built as another closed platform, but as access to a Nostr relay where creators can publish exclusive notes and media for supporters?

The quick readCreatr is a real Nostr.wine product and relay at `wss://creatr.nostr.wine`. Its NIP-11 metadata calls it a Patreon-inspired relay for Nostr content creators, reports version 0.2.1, requires authentication, and supports NIPs 1, 2, 4, 9, 11, 12, 15, 16, 20, 22, 28, 33 and 42. The website adds creator discovery, Nostr login, subscriptions, purchases and featured creator profiles. The catch is equally important: paid creator access introduces platform policy, payment intermediation and content-license terms, so portability is not the same as ordinary public posting.

A paid relay that acts like a creator club

Creatr is one of the cleaner examples of a Nostr product that is not merely a client. It is a business idea expressed as a relay. The public site calls the product "Creativity powered by Nostr" and invites you to support creators directly from a Nostr client. The practical promise is simple: creators publish exclusive notes and media; supporters unlock access; the transport is a Nostr relay rather than a normal social-media database.

That shape is worth slowing down for. A normal creator platform wants you to think in accounts, subscriptions, posts, locked galleries, payment processors and moderation rules. Nostr wants you to think in signed events, relays, clients, keys and discovery. Creatr sits exactly between those two worlds. It does not throw away the old paid-content model. It tries to move that model closer to Nostr by making the relay itself the access surface.

The result is not pure protocol romanticism. The site has a web app, sign-in, discovery, subscriptions, purchases, a terms page, a footer with version 0.2.1, and a visible list of featured creators. It looks and behaves like a product. It also exposes the relay address `wss://creatr.nostr.wine` and tells users to add that relay to a Nostr client. That is the strange and useful thing about Creatr: it is both a website and a relay endpoint. You can inspect it as a consumer product, but you should judge it as infrastructure too.

As checked on June 6, 2026, I did not find a reliable public GitHub code trail for Creatr itself. That matters. Some Nostr apps are fully open repositories; Creatr's strongest public evidence is different: the live site, the Nostr.wine site, the Terms of Service, NIP-11 relay metadata and NostrApps discovery data. So this article treats Creatr as a real product with a less transparent code/operator trail than an open-source client like Coracle, Citrine or Boris.

The product is the relay

The most important technical fact is the relay information document. When `https://creatr.nostr.wine/` is requested with the Nostr relay information header, it returns NIP-11 metadata for `creatr.nostr.wine`. The description calls it a Patreon-inspired relay for content creators on Nostr. It lists `wino@nostr.wine` as contact, a relay pubkey, software pointing back to `https://creatr.nostr.wine`, version `0.2.1`, and `auth_required: true`. It also reports generous relay limits: up to 2,000 tags, max limit 2,000, max message length 524,288, max subid length 71, and no proof-of-work requirement.

The supported NIPs are revealing. Creatr says it supports NIP-01 basics, NIP-02 contacts, NIP-04 encrypted direct messages, NIP-09 deletions, NIP-11 relay information, NIP-12 generic tag queries, NIP-15 marketplace-style event treatment, NIP-16 replaceable and ephemeral events, NIP-20 command results, NIP-22 comments, NIP-28 public chat, NIP-33 parameterized replaceable events and NIP-42 authentication. For a creator relay, that combination makes sense. It needs ordinary notes and profiles, access-gated reading, comments and conversations, authenticated relay sessions, and event kinds that can carry more than simple public text.

Notice what is absent from the NIP-11 metadata too. The relay metadata says payment is not required at the relay limitation level, even though the product itself clearly has paid creator access. That is not necessarily a contradiction. It suggests the relay does not describe its whole business model through the generic `payment_required` relay flag. The product layer can still decide which supporter sees which creator content, which transactions unlock access, and what the web app exposes. In other words, do not assume the NIP-11 JSON tells the entire commerce story.

The NIP-42 piece matters most. The relay requires authentication, and Nostr.wine's broader site makes a strong claim about using authentication to stop passive observers from seeing certain private-event access patterns. Creatr's own relay metadata aligns with that: this is not an open public firehose where anyone can subscribe anonymously. If you are building or studying creator access on Nostr, this is the hinge. Paid and semi-private social products need some way to know who is asking for events without turning every piece of data into a platform-only account.

What creators and supporters are actually doing

Creatr's home page shows the consumer version of the product. It has Nostr login, featured creator cards and profile pages. The visible categories include art, programming courses, photography, video, Spanish Bitcoin education, tutoring resources, handmade goods, writing resources and adult creator content. That mix is useful because it makes the product less abstract. Creatr is not only for one narrow creator type. It is testing whether paid Nostr relay access can support educational material, art drops, fan access, digital downloads, classes, behind-the-scenes work and other creator/customer relationships.

The site language is careful: support creators, unlock exclusive notes and media, use a Nostr client, add the relay. That suggests a workflow where creators post content to a restricted relay and supporters gain permission to fetch it. The web app then provides discovery, subscription and purchase surfaces for people who do not want to wire this together manually. This is a very Nostr-native business idea because it does not begin with a giant app store. It begins with a relay and asks clients to participate.

The Terms of Service make the business model much more concrete. Creatr defines a creator as a user who posts content for others to view, and a supporter as someone who follows a creator and can view that creator's content. It defines supporter/creator transactions as subscriptions, pay-per-view content payments and other interaction payments on a creator account. It also defines supporter payments as payments for those transactions or tips. That is not just a Nostr experiment; it is a commercial relationship.

The terms also say Creatr or related entities may act as payment intermediaries, collecting and processing supporter payments. When a supporter pays, the creator grants a limited, non-transferable, non-sublicensable and non-exclusive license to access the relevant content. The license can expire when payment fails, a subscription ends, content is removed, an account is suspended, or policy is breached. If you were hoping that Nostr automatically makes paid media permanently portable, this is the place to sober up. Creatr uses Nostr rails, but the paid-content license is a contract, not a magic open archive.

The Nostr.wine backbone

Creatr is part of the wider Nostr.wine product family. The main Nostr.wine site describes itself as a paid relay, lists Creatr among its relays, and markets a larger paid relay package with filter/broadcast access, regional mirrors, full-text search and payment via Bitcoin or Stripe. The headline fee shown on the checked page was a one-time admission fee of 18,888 sats for the general Nostr.wine relay. That does not automatically mean every Creatr creator transaction has the same price; it tells you what kind of operator environment Creatr belongs to.

Nostr.wine's broader pitch helps explain Creatr. The operator is not only running a creator page. It is selling reliability, spam reduction, relay access, search, paid membership and authenticated relay behavior. It offers a filter relay, Creatr, inbox, cellar and welcome relay surfaces, plus services such as search, translate, trending, event check and RelayGuardian. Creatr therefore sits inside a paid-relay business, not as a lonely side project.

That can be a strength. A creator-access product needs more than a button that says subscribe. It needs a relay that stays up, a way to control spam, a payment path, support contacts, search and enough operational discipline that creators do not feel they are placing their income on a weekend experiment. Nostr.wine is explicitly selling that operational layer. For the reader, the question is whether you trust that operator and whether the business terms fit the kind of content you want to publish or buy.

It also creates a dependency. Creatr may use Nostr events, but paid access is bound to the Creatr/Nostr.wine relay and account/payment system. If you subscribe to a creator there, the value is not simply that a note exists somewhere on Nostr. The value is that this relay recognizes you as an authorized supporter and serves the gated content. That is not a criticism. It is the actual architecture, and it should be described honestly.

Policy is not a side note here

Any paid creator platform has to answer boring questions that become important the moment money changes hands. Who is allowed to post? What happens if content is unlawful, stolen or reported? What rights does the creator grant the service? What can a supporter do with purchased media? What happens when an account is suspended? What happens if a private key is compromised? Creatr's terms spend real space on these questions.

The terms say users are responsible for their accounts and that Creatr is not responsible for lost, stolen or compromised accounts, private keys or unauthorized activity resulting from that. That sentence belongs in the article because it cuts through a lot of vague Nostr talk. If a product uses Nostr login and signed events, your key still matters. Paid access does not remove key hygiene. It makes key hygiene more expensive when things go wrong.

The terms also say content posted on Creatr may be accessed and used by other users or third parties, and that deleting an account will not necessarily prevent circulation of content that others recorded. Again, that is not anti-Nostr. It is Nostr realism. Digital content can be copied. Relays can be scraped. Supporters can save files. A creator platform can limit access and define licenses, but it cannot make screenshots and downloads impossible. Creatr's policy language is unusually direct about this for a page that also sells exclusive access.

There is another subtle point. Creatr is a Nostr product, but the terms include conventional platform commitments: moderation or review, suspension, removal, acceptable-use rules, complaint processes and policies around licensing. That is what happens when Nostr meets real commerce. You can decentralize identity and event publication, but money, intellectual property, safety and legal complaints still require governance. Creatr is interesting because it lets you see those layers sitting on top of the relay model instead of hiding them behind a glossy creator-dashboard story.

Where Creatr is strong and where it asks for trust

Creatr's strongest idea is simple: use the relay as the paid access boundary. That is more native to Nostr than bolting a private Patreon clone next to a public Nostr profile. A creator can point supporters at a relay, publish exclusive notes and media there, and use Nostr identity rather than asking everyone to create yet another conventional account. The visible creator directory also helps discovery, which Nostr often handles poorly when left entirely to users.

The second strength is that Creatr does not pretend to be only a vibe. The relay publishes NIP-11 metadata. The site exposes Nostr login. The terms define transactions and licenses. Nostr.wine describes its paid relay operations. You can inspect enough to understand the model. That is better than a product that says "Nostr-powered" and gives you nothing but a landing page.

The trust demands are just as real. The code trail is not public in the way many open Nostr clients are public. The relay operator controls admission, auth behavior, policy enforcement and the commercial website. The product can restrict access, suspend accounts and mediate payments. Supporters and creators therefore need to trust more than cryptography. They need to trust the operator's uptime, payment handling, moderation judgment, legal handling and communication.

That does not make Creatr bad. It makes Creatr honest terrain for the hard part of Nostr commerce. Purely public notes are easy to romanticize. Paid exclusive media is not. Someone has to decide who paid, who can read, how long the license lasts, what happens when a creator deletes content, and what happens when someone violates the rules. Creatr is a working attempt at that problem, with Nostr relays and Nostr login in the middle.

Who should study it

Creators should study Creatr if they are curious about paid Nostr access but do not want to run their own relay business from scratch. It is most relevant for people selling ongoing access, classes, behind-the-scenes posts, downloadable media, fan material, specialist instruction or niche community content. It is less relevant if all you need is public publishing, tips or occasional zaps. For that, a normal Nostr client plus Lightning address may be simpler.

Supporters should study it if they want to understand what they are buying. You are not only liking a public post. You are entering a supporter/creator transaction under Creatr's terms. That may be a subscription, a pay-per-view item or another paid interaction. The license is access, not ownership. The content may be available through the platform and relay rules, not automatically wherever you prefer to read Nostr. That distinction is not scary, but it is worth knowing before you pay.

Builders should study Creatr because it shows a possible route for Nostr businesses. Instead of saying "we will replace every creator platform overnight," it starts with a narrower, testable object: a creator relay with auth, discovery, payment logic and terms. You can critique the centralization, but you should not ignore the product lesson. The more money and rights enter the picture, the more Nostr apps need clear contracts, relay metadata, authentication and boring operational reliability.

Sources worth opening

Creatr's best public evidence is its live site, terms, relay metadata and the wider Nostr.wine infrastructure trail. Start here.

Back to the Crays Nostr page
Apps route visual cue 1
Apps route visual cue 2
Apps route visual cue 3
Apps route visual cue 4
Apps route visual cue 5

How to use this page

Find the product surface first.

Search clients, signers, product categories or developer tools when you need a specific app, source file or comparison clue.

AppsKeep exploring AppsApp routeProduct profiles, categories, signer guides and source links.Browse apps
Apps route visual cue 1
Apps route visual cue 2
Apps route visual cue 3
Apps route visual cue 4
Apps route visual cue 5

Bring something back

Ask, suggest, submit or nominate.

Use these links when something is missing, a source is stale, or a public Nostr builder belongs in the map.