Your Spotify - Self-hosted application
License: MIT. Source: https://github.com/Yooooomi/your_spotify.
services: server: image: yooooomi/your_spotify_server restart: always ports: - "8080:8080" links: - mongo depends_on: - mongo environment: API_ENDPOINT: http://localhost:8080 # This MUST be included as a valid URL in the spotify dashboard (see below) CLIENT_ENDPOINT: http://localhost:3000 SPOTIFY_PUBLIC: __your_spotify_client_id__ SPOTIFY_SECRET: __your_spotify_secret__ mongo: container_name: mongo image: mongo:6 volumes: - ./your_spotify_db:/data/db web: image: yooooomi/your_spotify_client restart: always ports: - "3000:3000" environment: API_ENDPOINT: http://localhost:8080
Self-hosting gives you three things SaaS can’t: data ownership (the files live on disks you control), cost predictability (a one-time setup vs. recurring per-seat fees that grow with your household or team), and longevity (open-source means the app keeps working even if the maintainers move on, since you can pin a working version). The trade-off is that you take on the operational work of running a server, applying updates, and handling backups.
Most self-hosted apps run comfortably on modest hardware — a Raspberry Pi 4, a mini PC, a NAS with Docker support, or a small VPS is usually enough for personal or family use. CPU and RAM requirements scale with how many simultaneous users or how much data you push through Your Spotify. Storage requirements depend on the kind of data you keep; check the README for guidance on data retention.
Last verified: 2026-04-21