Self-hosted music scrobble database to create personal listening statistics and charts
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
krateng b8944b4954 Reorganized containerfile to allow caching 2 months ago
.github Renamed workflows, fix GH-181 3 months ago
auxiliary Fixed scrobbler 2 months ago
container/root/etc/s6-overlay/s6-rc.d Add permission check and docs for PUID/PGID usage 3 months ago
dev Added cool tag list script 2 months ago
install Simplified container build 1 year ago
maloja More convenient album saving for 3.2 upgrade 2 months ago
.dockerignore Move image base to linuxserverio alpine base 3 months ago
.gitignore Added lint configuration and reorganized gitignore 1 year ago Update 1 year ago
APKBUILD Updated requirements 1 year ago
Containerfile Reorganized containerfile to allow caching 2 months ago Genericized containerfile 1 year ago Minor fixes 3 years ago
LICENSE Create LICENSE 5 years ago Add permission check and docs for PUID/PGID usage 3 months ago
example-compose.yml Added example compose file 1 year ago
pylintrc Added lint configuration and reorganized gitignore 1 year ago
pyproject.toml Bumped doreah version, fix GH-200 3 months ago
requirements.txt Bumped doreah version, fix GH-200 3 months ago
requirements_extra.txt Automated all distribution files 1 year ago
screenshot.png Added stresstest and new screenshot 1 year ago Updated 2 months ago Potentially fixed pyproject-based build and upload 1 year ago


Simple self-hosted music scrobble database to create personal listening statistics. No recommendations, no social network, no nonsense.


You can check my own Maloja page as an example instance.

Table of Contents


  • Self-hosted: You will always be able to access your data in an easily-parseable format. Your library is not synced with any public or official music database, so you can follow your own tagging schema.
  • Associated Artists: Compare different artists' popularity in your listening habits including subunits, collaboration projects or solo performances by their members. Change these associations at any time without losing any information.
  • Multi-Artist Tracks: Some artists often collaborate with others or are listed under "featuring" in the track title. Instead of tracking each combination of artists, each individual artist competes in your charts.
  • Custom Images: Don't rely on the community to select the best pictures for your favorite artists. Upload your own so that your start page looks like you want it to look.
  • Proxy Scrobble: No need to fully commit or set up every client twice - you can configure your Maloja server to forward your scrobbles to other services.
  • Standard-compliant API: Use existing, mature apps or extensions to scrobble to your Maloja server.
  • Manual Scrobbling: Listening to vinyl or elevator background music? Simply submit a scrobble with the web interface.
  • Keep it Simple: Unlike and similar alternatives, Maloja doesn't have social networking, radios, recommendations or any other gimmicks. It's a tool to keep track of your listening habits over time - and nothing more.

How to install


Maloja should run on any x86 or ARM machine that runs Python.

I can support you with issues best if you use Alpine Linux.

Your CPU should have a single core passmark score of at the very least 1500. 500 MB RAM should give you a decent experience, but performance will benefit greatly from up to 2 GB.


You can install Maloja with

	pip install malojaserver

To make sure all dependencies are installed, you can also use one of the included scripts in the install folder.

From Source

Clone this repository and enter the directory with

	git clone
	cd maloja

Then install all the requirements and build the package, e.g.:

	sh ./install/
	pip install -r requirements.txt
	pip install .

Docker / Podman

Pull the latest image or check out the repository and use the included Containerfile.

Of note are these settings which should be passed as environmental variables to the container:

  • MALOJA_DATA_DIRECTORY -- Set the directory in the container where configuration folders/files should be located
    • Mount a volume to the specified directory to access these files outside the container (and to make them persistent)
  • MALOJA_FORCE_PASSWORD -- Set an admin password for maloja

You must publish a port on your host machine to bind to the container's web port (default 42010). The container uses IPv4 per default.

An example of a minimum run configuration to access maloja via localhost:42010:

	docker run -p 42010:42010 -v $PWD/malojadata:/mljdata -e MALOJA_DATA_DIRECTORY=/mljdata krateng/maloja

Linux Host

NOTE: If you are using rootless containers with Podman this DOES NOT apply to you.

If you are running Docker on a Linux Host you should specify user:group ids of the user who owns the folder on the host machine bound to MALOJA_DATA_DIRECTORY in order to avoid docker file permission problems. These can be specified using the environmental variables PUID and PGID.

To get the UID and GID for the current user run these commands from a terminal:

  • id -u -- prints UID (EX 1000)
  • id -g -- prints GID (EX 1001)

The modified run command with these variables would look like:

	docker run -e PUID=1000 -e PGID=1001 -p 42010:42010 -v $PWD/malojadata:/mljdata -e MALOJA_DATA_DIRECTORY=/mljdata krateng/maloja


  • If you'd like to display images, you will need API keys for and Spotify. These are free of charge!

  • Put your server behind a reverse proxy for SSL encryption. Make sure that you're proxying to the IPv6 or IPv4 address according to your settings.

  • You can set up a cronjob to start your server on system boot, and potentially restart it on a regular basis:

@reboot sleep 15 && maloja start
42 0 7 * * maloja restart

How to use

Basic control

Start and stop the server in the background with

	maloja start
	maloja stop
	maloja restart

If you need to run the server in the foreground, use

	maloja run


If you would like to import your previous scrobbles, use the command maloja import *filename*. This works on:

⚠️ Never import your data while maloja is running. When you need to do import inside docker container start it in shell mode instead and perform import before starting the container as mentioned above.

	docker run -it --entrypoint sh -v $PWD/malojadata:/mljdata -e MALOJA_DATA_DIRECTORY=/mljdata krateng/maloja
	cd /mljdata
	maloja import my_last_fm_export.csv

To backup your data, run maloja backup, optional with --include_images.


  • Have a look at the available settings and specifiy your choices in /etc/maloja/settings.ini. You can also set each of these settings as an environment variable with the prefix MALOJA_ (e.g. MALOJA_SKIP_SETUP).

  • If you have activated admin mode in your web interface, you can upload custom images for artists or tracks by simply dragging them onto the existing image on the artist or track page. You can also manage custom images directly in the file system - consult in the /var/lib/maloja/images folder.

  • To specify custom rules, consult the file in /etc/maloja/rules. You can also apply some predefined rules on the /admin_setup page of your server.

How to scrobble

You can set up any amount of API keys in the file apikeys.yml in your configuration folder (or via the web interface). It is recommended to define a different API key for every scrobbler you use.

Some scrobbler clients support Maloja's native API. You can also use any scrobbler that allows you to set a custom Listenbrainz or GNUFM server. See for details.

If you're the maintainer of a music player or server and would like to implement native Maloja scrobbling, feel free to reach out!

If you can't automatically scrobble your music, you can always do it manually on the /admin_manual page of your Maloja server.

How to extend

If you'd like to implement anything on top of Maloja, visit /api_explorer.