Music doesn't belong
to platforms.
It belongs to
the people who make it.

I — The problem

Somewhere along the way, the music industry made peace with a new arrangement: artists hand over their catalogue, their metadata, their fans' attention — and in return they receive fractions of a cent per stream, delivered monthly, through a dashboard they do not control, on a platform that can change the rules at any moment and frequently does.

The platforms are not evil. They solved a real problem — distribution at scale — and they solved it well. But they kept the relationship. The listener subscribes to the platform. The artist gets a percentage of the remainder. There is no direct line between the person who made the music and the person who loves it.

That missing line is not a technical accident. It is a business model.

II — What we believe

We believe a musician with a server and a domain should be as discoverable as one with a major label deal. Not theoretically — actually, in practice, on the same network, with the same tools.

We believe self-hosting is not for nerds. It is for anyone who wants to own their relationship with their audience. The email protocol proved that a decentralized communication layer can reach billions of people without anyone owning the address book. Music has no equivalent. We think it should.

We believe the right model is not subscription, not per-stream royalty, not algorithmic placement. The right model is the one the artist chooses — free, pay-what-you-want, fixed price, token-gated, whatever fits. The infrastructure should not have an opinion about this.

III — How it works

Tunecamp is a piece of software you run on hardware you control. It speaks standard protocols — Subsonic for mobile clients, ActivityPub for the Fediverse, HTTP for everything else. It does not phone home. It does not aggregate your listeners' data into a product someone else sells.

Instances find each other through HTTP gossip — no central registry, no company in the middle. When you start a Tunecamp server, you join a network of independent nodes. Your catalogue is yours. Your listeners connect to you. If you turn the server off, your music goes offline — not into someone else's archive.

That last sentence might sound like a downside. It is not. It means no one else can monetize your back catalogue without your knowledge, silence your releases for licensing reasons, or serve ads against your music while you receive nothing.

IV — What this is not

This is not a Web3 pitch. You do not need a wallet to listen to music. Smart contracts are optional tooling for artists who want on-chain ownership mechanics — not a precondition of participation.

This is not a piracy tool. Every Tunecamp instance is run by the artist or someone they trust. The music is there because its owner put it there.

This is not anti-commerce. Artists should earn money. Tunecamp supports Stripe, direct payments, and cryptocurrency — because we think artists should be able to sell without a platform taking a percentage of a percentage of a fraction.

V — The archive problem

Here is a question nobody asks until it's too late: where does the music go when the platform dies?

You do not own the music on your streaming service. You own a licence to access it — revocable, tied to a subscription, governed by agreements between labels and platforms that you are not party to and cannot read. When those agreements end, the music disappears. Not from the world, hopefully. But from your ears, immediately.

This has already happened hundreds of times. Stores close. Catalogues move. Labels pull out. Artists get delisted for reasons that are never explained. An entire generation of digital-native music — netlabel releases, early Bandcamp experiments, forum-shared underground records — exists today in a state of quiet emergency, scattered across dying servers and unmaintained links.

The physical record was a terrible format for many reasons. But the person who owned it owned it. It could be played on any turntable, lent to a friend, passed to the next generation, discovered in a box forty years later. The MP3 was supposed to democratize that. Instead we traded physical ownership for cloud dependency — and called it progress.

Tunecamp is not just a streaming server. It is a personal archive. You seed your music as torrents. You back it up. You scan and preserve files from drives, from Telegram, from anywhere they survive. The library you build on your instance outlasts any platform — because it lives on hardware you control, in a format that plays on anything, copyable, redundant, yours. Not because a corporation decided to keep the servers running this month.

VI — Curation is preservation

Every person who runs a Tunecamp instance and fills it with music they love is doing something more than organizing a personal collection. They are making a curatorial decision — this matters, this deserves to exist, this will be findable by the next person who looks.

A federated network of such decisions is, quietly, a distributed archive. No single institution, no centralized catalogue, no agreement required between rights holders who may not even exist anymore. Just people with servers and taste.

Libraries have always worked this way. One copy here, one there, no central authority deciding what survives. The internet was supposed to make this easier, not harder. Somewhere in the rush to subscription models we forgot that. Tunecamp is a reminder.

VII — The bet

The bet is simple: most artists don't need a platform. They need infrastructure. They need a server that works, a player people can use, and a way for other instances to find their music. Everything else — the audience, the relationship, the money — they can build themselves, the same way they always have, one listener at a time.

The internet was built on this idea. The web is a network of servers no one owns. Email is a protocol no one controls. The phone network routes calls between carriers that compete. We got used to music being different — to there being one place where music lives and one company that decides what gets recommended and to whom.

We don't think that's inevitable. We think it was a temporary state of affairs produced by the technical difficulty of running a server in 2005. That difficulty is gone. The arrangement it justified should go with it.

Run your instance. Put your music on it. Tell your listeners where to find you. That's the whole thing.

We'll be here, and so will every other server on the network — none of us in charge of any of it.