Maloja

Maloja is an open-source self-hosted music scrobbler that records every track you play and turns the history into personal listening charts, time-pulse graphs, top-artist rankings, and yearly summaries. It is the closest community alternative to the data side of Last.fm — the part of the service that gradually shrank as Last.fm pivoted toward editorial content and away from being the canonical home for personal listening history. Scrobbles flow into Maloja from any client that already speaks the Last.fm API, plus direct integrations with Plex, Jellyfin, Navidrome, multi-scrobblers, mpdscribble, and a long tail of community bridges, so the same instance can capture plays from your phone, your home media server, your desktop player, and your car all at once.

Common Use Cases

Music nerds and long-time Last.fm users self-host Maloja to keep building a personal listening archive that they fully own — surviving any pricing, policy, or feature change at a third-party scrobbling service. Plex, Jellyfin, and Navidrome users wire their server's scrobble webhook into Maloja to capture every play across the household with proper artist, album, and track normalization. Privacy-conscious listeners route their phones, desktop players, and DJ software into Maloja instead of public scrobblers so the metadata about what they listen to stays inside their own infrastructure. Hobbyist data analysts treat Maloja as a personal listening data warehouse, exporting scrobbles via the API into Jupyter notebooks, custom dashboards, or year-in-review visualizations. Music collectors maintain an authoritative play count alongside their library to inform what to rip, repurchase, or queue up next. Households with shared media setups split scrobbles across separate accounts so each member keeps a personal listening history without polluting a household-wide stream.

Key Features

• Personal scrobble database with chart pages for top artists, albums, and tracks across configurable time ranges
• Last.fm-compatible API endpoint that accepts scrobbles from any client speaking the standard Last.fm protocol
• Direct integrations with Plex, Jellyfin, Navidrome, multi-scrobblers, mpdscribble, and other community-maintained bridges
• Pulse-style time graphs showing how often you listen to a given artist, album, or track over weeks, months, and years
• Metadata enrichment via Last.fm, Spotify, MusicBrainz, and TheAudioDB for artist images, album art, and tag data
• Optional Last.fm proxy scrobbling so your existing public profile keeps updating while you also build a private archive
• API key management with multiple keys for separating scrobble sources (phone, server, scripts) and for revocation
• Manual scrobble entry and editing for fixing mis-tagged plays, importing legacy listening history, or correcting metadata mistakes
• Album-aware tracking that handles compilations, remixes, and split-artist credits using configurable parsing rules
• Bulk import workflows for ingesting Last.fm exports, Spotify extended history, and other historical scrobble dumps
• Lightweight Python + SQLite stack with predictable resource usage on small VPS instances
• Configurable scrobble thresholds, vanity tiers (gold/platinum/diamond), and chart styles to make the dashboard your own

Why deploy Maloja on Hostinger VPS

Running Maloja on a Hostinger VPS gives you a private, vendor-independent home for personal listening data that may need to outlive any individual scrobbling service. Self-hosting means scrobbles, API keys, and enriched metadata all stay inside infrastructure you control — important if you treat listening history as personal data and don't want it sold to advertisers or merged into a third-party recommendation graph. Dedicated CPU and disk on a VPS handle continuous scrobble ingestion from multiple players plus periodic metadata refreshes without throttling, and the small Python + SQLite footprint comfortably runs alongside other self-hosted services on the same instance. Persistent volume storage keeps years of scrobble history durable across container restarts, host upgrades, and VPS migrations, so the data set you spent time curating doesn't vanish when an image changes. Combined with Traefik-based HTTPS routing, the API endpoint your players post scrobbles to is encrypted end-to-end, and your dashboards are reachable from any device on a clean branded URL.