Algorave is a permanent, decentralized archive for live coding music sets. Every set is published on the AT Protocol network, the same infrastructure that powers the open social web. Once published, your set exists on the network's relays and personal data servers. No single company, server, or person controls it. Think of it as a public library for algorave performances, not a streaming platform.

GitHub stores code but has no standard way to publish structured metadata alongside it. Pastebin is temporary. A normal database is controlled by a single server operator. AT Protocol is an open network where your set lives on relays run by different people around the world. No single company can delete it, no server going down makes it disappear. Publishing to AT Protocol also makes your set part of a larger ecosystem: tools like Bluesky can reference it, other archives can discover it, and you keep full control through your own PDS. It is the closest thing we have to a permanent, portable, decentralized storage layer for structured creative work.

Go to /publish, paste your code, fill in the details. The system publishes your set to the AT Protocol network as a signed record. You need a handle on the network. No registration on this site, no email, no account, no database. Your set lives on the network, not on this server.

The catalog at /sets indexes every published set by title, artist, language, genre, BPM, tags, and the source code itself. You can search for drum patterns, synthesizer techniques, specific rhythms or effects. The search engine reads inside your code, not just the metadata. If someone wrote a killer bassline pattern in Strudel, you can find it by searching what it does, not just what it is called.

TidalCycles, Strudel, Sonic Pi, SuperCollider, FoxDot, and anything else that compiles to sound. When you publish, select the language from the list. The source code is stored as plain text so it stays readable and searchable forever, regardless of which tool you used to write it.

Every set is a signed record on the AT Protocol network, hosted across relays and personal data servers around the world. Once published, no single person, company, or government can delete it. You control your data through your own PDS. The network is open. Anyone can run a relay or host a PDS.

Yes, only the author can edit or delete their own sets. Edits create a new version (the old one stays visible in the history). Deletion removes the record from public relays. The network is append-only by design, so your set never truly disappears from personal archives, but it will no longer appear in the catalog.

A live coding set performed at a specific event, like a festival or an algorave night, carries different context than a studio sketch. Adding the event name, location, and date turns a code snippet into a historical document. Future live coders searching for sets from that night, or that venue, or that scene will find yours. Metadata is what makes an archive searchable across time, not just across code.

The default is CC BY-NC-SA 4.0, which allows sharing and adaptation with attribution for non-commercial use. If you want your code reused freely, choose CC0 or MIT. We recommend an open license so other live coders can study, remix, and learn from your work. You pick the license when publishing.