IndieSats: The Platform That Doesn't Own Your Music
A Nostr-first architecture means you publish once, own forever, and never ask permission.
Most music platforms trap your data. They store your tracks in their database, serve your RSS from their servers, and if they decide to change your profile or take down your music, you have no recourse. Your creative work becomes a row in their Postgres that they control.
IndieSats does the opposite.
You Publish to Nostr. We Render It.
When you publish a track through IndieSats, here's what actually happens:
1. You build a Nostr event (kind 36787 — Amethyst music track format)
2. You sign it with your key — either your browser extension or your nsec
3. It broadcasts to relays — Primal, nos.lol, and ours
4. That's it. Your music now lives on the open relay network, signed and immutable
IndieSats doesn't store your tracks in a database. We don't host your audio. We don't generate your RSS from our API. We query the Nostr network, cache it briefly, and render it. We are a renderer, not a host.
What This Means for You as an Artist
Your Profile Is Yours
Your artist profile is your Nostr kind 0 event. Want to change your lightning address? Update your Nostr profile. The change reflects instantly across every IndieSats RSS feed, every podcast app, every relay — no ticket to support, no 24-hour wait.
Your Music Can't Be Delisted
Because every track event is signed with your key and lives on 10+ independent relays, no single platform can remove your music. If IndieSats goes offline, your events are still on Primal, nos.lol, and every other relay. Any app can query them. Any developer can build a new renderer.
Your RSS Feed Is Portable
Traditional platforms generate RSS from their database. Their product, their control. IndieSats generates RSS fresh on every request from your live Nostr events. The feed is a view on data you already own. Take your npub to any Nostr-aware tool and the same data is there.
You Prove Authorship
Every track is cryptographically signed. That signature verifies you created it. No platform badge needed — mathematics does the attestation.
One Feed, Everything
Whether you publish one single or fifty albums, you get one RSS feed URL:
https://indiesats.com/api/feed?npub=YOUR_NPUB
Podcast apps, Fountain, Castamatic — they all subscribe to the same feed. New tracks appear automatically. No re-submission. No platform gatekeeping.
The Architecture in One Sentence
IndieSats renders music that artists own, rather than hosting music that platforms control.
Why This Matters
Platforms with a central database store your profile, tracks, and RSS as rows in their infrastructure. They can modify your metadata, change your splits, or delist your work because they hold the keys to the storage. Wavlake, for example, runs on Postgres — your tracks live in their database and their RSS is generated from their API.
IndieSats has no database for music metadata. The "database" is the Nostr relay network. We read from it. You write to it. That's the whole relationship.
For the Technical Minds
- No custody: We don't hold your sats, your keys, or your data
- No keysend forwarding liability: You receive directly to your lnaddress
- Deterministic GUIDs: SHA1-based, stable across republishes and re-renders
- Kind 36787 + Podcast Index spec: Standard events, standard RSS, maximum compatibility
- Client-side wallets: NWC, LNC, WebLN — your credentials never touch our server
The Bottom Line
Publish via IndieSats and you're not "uploading to a platform." You're writing to an open, global, censorship-resistant publishing layer that happens to have a really nice music renderer attached.
Your music outlives us. That's the point.
Try it: https://indiesats.com/publish.html
#music #nostr #indiesats #bitcoin #lightning #openmusic #value4value
A Nostr-first architecture means you publish once, own forever, and never ask permission.
Most music platforms trap your data. They store your tracks in their database, serve your RSS from their servers, and if they decide to change your profile or take down your music, you have no recourse. Your creative work becomes a row in their Postgres that they control.
IndieSats does the opposite.
You Publish to Nostr. We Render It.
When you publish a track through IndieSats, here's what actually happens:
1. You build a Nostr event (kind 36787 — Amethyst music track format)
2. You sign it with your key — either your browser extension or your nsec
3. It broadcasts to relays — Primal, nos.lol, and ours
4. That's it. Your music now lives on the open relay network, signed and immutable
IndieSats doesn't store your tracks in a database. We don't host your audio. We don't generate your RSS from our API. We query the Nostr network, cache it briefly, and render it. We are a renderer, not a host.
What This Means for You as an Artist
Your Profile Is Yours
Your artist profile is your Nostr kind 0 event. Want to change your lightning address? Update your Nostr profile. The change reflects instantly across every IndieSats RSS feed, every podcast app, every relay — no ticket to support, no 24-hour wait.
Your Music Can't Be Delisted
Because every track event is signed with your key and lives on 10+ independent relays, no single platform can remove your music. If IndieSats goes offline, your events are still on Primal, nos.lol, and every other relay. Any app can query them. Any developer can build a new renderer.
Your RSS Feed Is Portable
Traditional platforms generate RSS from their database. Their product, their control. IndieSats generates RSS fresh on every request from your live Nostr events. The feed is a view on data you already own. Take your npub to any Nostr-aware tool and the same data is there.
You Prove Authorship
Every track is cryptographically signed. That signature verifies you created it. No platform badge needed — mathematics does the attestation.
One Feed, Everything
Whether you publish one single or fifty albums, you get one RSS feed URL:
https://indiesats.com/api/feed?npub=YOUR_NPUB
Podcast apps, Fountain, Castamatic — they all subscribe to the same feed. New tracks appear automatically. No re-submission. No platform gatekeeping.
The Architecture in One Sentence
IndieSats renders music that artists own, rather than hosting music that platforms control.
Why This Matters
Platforms with a central database store your profile, tracks, and RSS as rows in their infrastructure. They can modify your metadata, change your splits, or delist your work because they hold the keys to the storage. Wavlake, for example, runs on Postgres — your tracks live in their database and their RSS is generated from their API.
IndieSats has no database for music metadata. The "database" is the Nostr relay network. We read from it. You write to it. That's the whole relationship.
For the Technical Minds
- No custody: We don't hold your sats, your keys, or your data
- No keysend forwarding liability: You receive directly to your lnaddress
- Deterministic GUIDs: SHA1-based, stable across republishes and re-renders
- Kind 36787 + Podcast Index spec: Standard events, standard RSS, maximum compatibility
- Client-side wallets: NWC, LNC, WebLN — your credentials never touch our server
The Bottom Line
Publish via IndieSats and you're not "uploading to a platform." You're writing to an open, global, censorship-resistant publishing layer that happens to have a really nice music renderer attached.
Your music outlives us. That's the point.
Try it: https://indiesats.com/publish.html
#music #nostr #indiesats #bitcoin #lightning #openmusic #value4value
2❤️1💐1💜1😂1
