Self-hosted streaming for indie artists, labels, and communities — with federation, Web3, and Subsonic support.
New here? Start with the Getting Started guide. It walks you from an empty machine to a running instance with music in it — install, first login, adding your library, and listening — in about 10 minutes.
Once you're up and running, the guides below go deeper.
| Doc | Description |
|---|---|
| Getting Started | Install → first login → add music → listen (start here) |
| Adding Music | Library layout on disk, scanning, and draft → public release — the reference for getting audio in |
| Deploy on Railway | One-click deploy on Railway — no VPS required, HTTPS included |
| API & Services Setup | Step-by-step configuration for Stripe, Google Drive, AI, and other integrations |
| Nginx Configuration | Reverse proxy setup for SSL, WebSocket, and HLS |
| Backup & Migration | Database backup, restore, and moving your instance |
For listeners and artists using a TuneCamp instance.
| Doc | Description |
|---|---|
| Roles & Permissions | What each role (Owner, Manager, Curator, Listener) can do |
| Radio | Broadcasting an always-on station from your library (playlists + genre mixes) |
| Subsonic Protocol | Connecting external clients (DSub, Symfonium, Tempo, Substreamer) |
| Social & Community Features | Posts, comments, and fan interactions |
| Collab | Multi-artist collaborative track building: stems, version snapshots, no realtime |
| Becoming an Artist & Selling | Artist request flow and the can_sell sales gate |
| Payments & Monetization | Stripe checkout, crypto on-ramp, and on-chain purchases |
For people running a TuneCamp instance.
| Doc | Description |
|---|---|
| Federation | ActivityPub and HTTP gossip discovery — how instances find each other |
| Sidecamp Desktop | Desktop application for Sidecamp, Soulseek, and Torrents |
| Monitoring | /health endpoint, the admin System Resources panel, Sentry crash reporting, and uptime checks |
| Scaling | SQLite / single-process limits and mitigations |
| MCP Setup | Exposing the TuneCamp catalog to AI clients via MCP |
For contributors and people building on TuneCamp.
| Doc | Description |
|---|---|
| Contributing | Code contribution guidelines and pull request process |
| Development Guide | Local dev environment setup, running, and testing |
| Backend Architecture | Express server, SQLite, ActivityPub, federated discovery, and the full data model / database schema |
| Webapp Architecture | React, Vite, Zustand, and instance discovery in the frontend |
| API Contracts | REST endpoints, authentication, and supported protocols |
| FID Identity | Self-sovereign identity and instance passports via FID + Zen SEA |
Optional third-party services you can connect to your instance.
| Doc | Description |
|---|---|
| AI Integrations | Metadata automation and recommendations via OpenRouter |
| Smart Contracts | Solidity contracts (Factory, NFT, Checkout) on Base |
| Google Drive | Cloud storage backend for media files |
| Sidecamp | P2P acquisition (Soulseek, BitTorrent, yt-dlp) via the desktop companion app |
| Telegram Bot | Rapid file ingestion and remote management |
| Doc | Description |
|---|---|
| Project Overview | Goals, tech stack, repository structure, source tree, and webapp component catalog |
| Status & Maturity | Honest maturity level of each area and known limitations |
| Comparison with Funkwhale | Differences in models and features |
| Audio Fingerprinting | How TuneCamp deduplicates tracks in the library |
| Payments Security Review | Internal security review findings for the payments flow |
Last updated: August 22, 2026