Programming language: TypeScript
License: GNU General Public License v3.0 only
Tags: Personal Dashboards    

Your Spotify alternatives and similar software solutions

Based on the "Personal Dashboards" category.
Alternatively, view Your Spotify alternatives based on common mentions on social networks and blogs.

Do you think we are missing an alternative of Your Spotify or a related project?

Add another 'Personal Dashboards' Software solution


Client CI Server CI Donate

Your Spotify

YourSpotify is a self-hosted application that tracks what you listen and offers you a dashboard to explore statistics about it! It's composed of a web server which polls the Spotify API every now and then and a web application on which you can explore your statistics.

Table of contents


  1. You have to own a Spotify application ID that you can create through their dashboard.
  2. You need to provide the Server environment the public AND secret key of the application (cf. Installation).
  3. You need to provide an authorized redirect URI to the docker-compose file.

A tutorial is available at the end of this readme.


Using docker-compose

Follow the docker-compose-example.yml to host your application through docker.

version: "3"

    image: yooooomi/your_spotify_server
    restart: always
      - "8080:8080"
      - mongo
      - mongo
      - 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__
      - CORS=http://localhost:3000,http://localhost:3001 # all if you want to allow every origin
    container_name: mongo
    image: mongo:4.4.8
      - ./your_spotify_db:/data/db

    image: yooooomi/your_spotify_client
    restart: always
      - "3000:3000"
      - API_ENDPOINT=http://localhost:8080

Some ARM-based devices might have trouble with Mongo >= 5. I suggest you use the image mongo:4.4.

Installing locally (not recommended)

You can follow the instructions here. Note that you will still have to do the steps below.


Key Default value (if any) Description
CLIENT_ENDPOINT REQUIRED The endpoint of your web application
API_ENDPOINT REQUIRED The endpoint of your server
SPOTIFY_PUBLIC REQUIRED The public key of your Spotify application (cf Creating the Spotify Application)
SPOTIFY_SECRET REQUIRED The secret key of your Spotify application (cf Creating the Spotify Application)
CORS all List of comma-separated origin allowed, or all to allow any origin
MAX_IMPORT_CACHE_SIZE Infinite The maximum element in the cache when importing data from an outside source, more cache means less requests to Spotify, resulting in faster imports
MONGO_ENDPOINT mongodb://mongo:27017/your_spotify The endpoint of the Mongo database
PORT 8080 The port of the server, do not modify if you're using docker
TIMEZONE Europe/Paris The timezone of your stats, only affects read requests since data is saved with UTC time
LOG_LEVEL info The log level, debug is useful if you encouter any bugs


You can edit the CORS for the server:

  • all will allow every source.
  • origin1,origin2 will allow origin1 and origin2.

Creating the Spotify Application

For YourSpotify to work you need to provide a Spotify application public AND secret to the server environment. To do so, you need to create a Spotify application here.

  1. Click on Create a client ID.
  2. Fill out all the informations.
  3. Copy the public and the secret key into your docker-compose file under the name of SPOTIFY_PUBLIC and SPOTIFY_SECRET respectively.
  4. Add an authorized redirect URI corresponding to your server location on the internet adding the suffix /oauth/spotify/callback.
    1. use the EDIT SETTINGS button on the top right corner of the page.
    2. add your URI under the Redirect URIs section.
    3. i.e: http://localhost:8080/oauth/spotify/callback or http://home.mydomain.com/your_spotify_backend/oauth/spotify/callback
    4. Do not forget to hit the save button at the bottom of the popup.

Importing past history

By default, YourSpotify will only retrieve data for the past 24 hours once registered. This is a technical limitation. However, you can import previous data by two ways.

The import process uses cache to limit requests to the Spotify API. By default, the cache size is unlimited, but you can limit is with the MAX_IMPORT_CACHE_SIZE env variable in the server.

Supported import methods

Privacy data

  • Request your privacy data at Spotify to have access to your history for the past year here.
  • Head to the Settings page and choose the privacy method.
  • Input your files starting with StreamingHistoryX.json.
  • Start your import.

Full privacy data

Full privacy data can be obtained by emailing [email protected] and requesting your data since the creation of the account.

  • Request your data by email.
  • Head to the Settings page and choose the full-privacy method.
  • Input your files starting with endsongX.json.
  • Start your import.


An import can fail:

  • If the server reboots.
  • If a request fails 10 times in a row.

A failed import can be retried in the Settings page. Be sure to clean your failed imports if you do not want to retry it as it will remove the files used for it.

It is safer to import data at account creation. Though YourSpotify detects duplicates, some may still be inserted. However, song search is pretty accurate since it filters on artist then search for the song name.


How can I block new registrations?

From an admin account, go to the Settings page and hit the Disable new registrations button.

Songs don't seem to synchronize anymore.

This can happen if you revoked access on your Spotify account. To re-sync the songs, go to settings and hit the Relog to Spotify button.

The web application is telling me it cannot retrieve global preferences.

This means that your web application can't connect to the backend. Check that your API_ENDPOINT env variable is reachable from the device you're using the platform from.

External guides


If you have any issue or any idea that could make the project better, feel free to open an issue. I'd love to hear about new ideas or bugs you are encountering.


I work on this project on my spare time and try to fix issues as soon as I can. If you feel generous and think this project and my investment are worth a few cents, you can consider sponsoring it with the button on the right, many thanks.