English
Maloja Hosting
Track your music listening history and scrobbles on a private, self-hosted alternative to Last.fm.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Tech
- Docker image
- krateng/maloja:latest
- Default port
- 42010
How Maloja works
Maloja receives scrobbles from compatible players or clients and stores each listening event in a personal database. The interface turns that history into charts, time-based statistics, artist and track views, listening patterns, and manually corrected metadata. An API key lets authorised clients submit new events.
Compatibility endpoints can accept formats used by ListenBrainz or GNU FM clients, while the native API supports Maloja-specific integrations. Existing history can be imported from official Spotify or ListenBrainz exports, a Last.fm export in a supported format, or another Maloja instance. Manual scrobbling is available when a player cannot report directly.
Key Maloja features
The application emphasises ownership and customisation of listening history. Users can define artist associations, merge naming variations, add custom images, and adjust metadata to make charts reflect the catalogue they recognise. External image sources such as Last.fm or Spotify may require separate API credentials.
Maloja is not a music streaming server and does not provide songs, subscriptions, or player accounts. It records listening activity supplied by compatible clients. If the scrobbling application, endpoint, API key, or player integration is misconfigured, playback can continue while the personal history remains incomplete.
Maloja vs Last.fm
Maloja is a self-hosted scrobble database that produces private charts and statistics from submitted listening events. Last.fm operates a hosted profile service with desktop and mobile applications, integrations for major music platforms, personalised reports, social listening history, artist information, and recommendations.
Last.fm may suit listeners who want a broad commercial integration network and a hosted profile that works across supported services. Maloja appeals to users who value local control of their history and are willing to configure clients, API keys, metadata corrections, image providers, imports, storage, and backups.
Who uses Maloja
Music enthusiasts use Maloja to preserve long-term listening history, compare artists or tracks across time, and create charts independent of a streaming provider. Users moving from another scrobbling service can import supported exports, while developers can connect personal tools through the native API.
The accuracy of statistics depends on the events and metadata received. Duplicate scrobbles, inconsistent artist names, missing album information, or disconnected clients can distort charts. Periodic review and correction are part of maintaining a useful personal listening archive.
Self-hosting Maloja: requirements and cost
Demand grows with scrobble volume, imported history, chart calculations, concurrent visitors, image caching, custom artwork, API calls, and retained local data. The catalogue records PostgreSQL and MariaDB as Not required; the persistent Maloja data directory contains the history and configuration that must remain protected together. Maloja is storage-driven, so 50 GB on Plan 3 is a realistic starting point and 100 GB on Plan 4 better suits a large library.
On AvaHost, Maloja uses Plan 1 at €2. The hosted Maloja package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. The catalogue deployment supplies a generated administrator password, and Maloja exposes an API key from its settings for compatible players. Music subscriptions, audio files, scrobbling clients, player configuration, and optional image-provider credentials are not included.
F.A.Q
Maloja starts at €2 on Plan 1. A personal scrobble history with light browsing fits the entry plan, while large imports, many years of events, image caching, chart generation, API traffic, and multiple viewers can raise demand. Storage is significant: Plan 3 offers 50 GB and Plan 4 offers 100 GB.
Sign in with the generated administrator password, then obtain the API key shown in Maloja settings. Configure a compatible player, browser extension, mobile client, or supported server with the final Maloja URL and that key. Test several tracks and verify artist, title, timestamp, and album metadata before importing a large historical dataset.
A custom hostname can expose Maloja through automated HTTPS once DNS points to AvaHost. Update every scrobbling client with the final address and confirm submissions after the change. Old endpoints stored in players can silently stop recording history, so check the recent-scrobble view before assuming all devices have migrated.
No. Maloja records listening events and displays personal statistics; it does not supply songs, streaming subscriptions, player accounts, or Last.fm access. Users provide lawful playback services and compatible scrobbling clients. Optional artist-image providers may also need separate API credentials, and missing client events cannot be reconstructed automatically by the hosting platform.