Consumer

Music scrobbling aggregation across sources

Tallyrow · One listening history from every music app, server and player you use

WatchingDraft scoreMature market · since 2002 · AI estimate

41PWAS score

Confidence

Based on 8 of 9 factors

Overview

AIThis description was written by a model from public signals. The facts behind it are listed under Evidence.

Problem: People listen to music across multiple sources and services (Spotify, YouTube Music, local servers, etc.), but music tracking services like Last.fm only integrate with some of them, leaving listening history fragmented and incomplete across different platforms and clients.
Solution concept: A scrobbling aggregator that connects to multiple music sources simultaneously and forwards play events to multiple tracking backends, unifying listening history across all music services a person uses, including both mainstream streaming and self-hosted alternatives.
Who has it: Music listeners and enthusiasts who use multiple music sources and want to maintain a unified listening history; users of self-hosted music servers like Jellyfin, Plex, or Subsonic.
How they handle it today: Today, users manually manage listening history across fragmented music services, or use limited integrations that only work with specific streaming platforms, leaving gaps in their personal music data when they switch between different music sources.
Why now: Proliferation of self-hosted music services, decentralized music platforms, and multiple streaming subscriptions have made unified listening history increasingly fragmented; containerization (Docker) and open protocols make aggregation more feasible.
How it could charge: Likely free or freemium model, with potential premium tier for advanced features, API access, or self-hosted deployment support; alternately, subscription for cloud hosting of the aggregation service rather than self-hosting.

Verdict

Computed from the factor scores below, never written by a model. It decides nothing on its own: only the gate makes an opportunity a build candidate.

Score breakdown

A model sorted each factor into a rubric bucket; code turned buckets into numbers. Unknown factors are left out of the score and lower confidence instead.

Market validation

Confidence 70 · 2 evidence · Multiple established tracking backends (Last.fm, ListenBrainz, Maloja) and self-hosted music servers (Jellyfin, Subsonic, Plex, Mopidy) show existing products in the ecosystem addressing related needs, and the project's broad integration support indicates clear demand across multiple music sources.

Revenue evidence

Unknown

No evidence provided about pricing, paid customers, or revenue for this or competing aggregation services.

Growth

Confidence 95 · 1 evidence · The GitHub repository shows 1263 stars over 2161 days, which is approximately 0.58 stars per day—a modest, steady accumulation rather than rapid growth or breakout momentum.

Problem severity

Confidence 30 · Judged from the description · Fragmented listening history across multiple music sources is recurring friction that enthusiasts and multi-platform users encounter regularly, but they can work around it through manual tracking or selective service use.

Economic proximity

Confidence 30 · Judged from the description · Scrobbling aggregation is a data organization and tracking utility; it does not directly sit in checkout, sales automation, lead generation, or cost-saving workflows.

Distribution

Confidence 30 · Judged from the description · The aggregator produces unified listening history that users share on their profiles or export to services like Last.fm, which other users may see, but the primary value is internal to the individual user.

Buildability

Confidence 30 · Judged from the description · Building a scrobbling aggregator requires integrating with multiple music platform APIs (Spotify, YouTube Music, Deezer, etc.) and self-hosted server APIs (Jellyfin, Subsonic, Mopidy), plus forwarding to multiple tracking backends—a moderate challenge with standard API integration patterns.

Differentiation

Confidence 70 · 2 evidence · There is a clear gap that users encounter and existing services like Last.fm do not fully address: the ability to seamlessly aggregate plays from both mainstream streaming services and self-hosted music servers into a single unified history.

Retention and timing

Confidence 30 · Judged from the description · Music listening is a daily or near-daily recurring workflow for the target audience, and the growth of self-hosted music infrastructure adoption and multi-source listening represents a timing tailwind as fragmentation increases.

Risk penalties

Depends on one platformThe aggregator's success depends on maintaining integrations with multiple third-party APIs (Spotify, YouTube Music, Last.fm, ListenBrainz, Maloja, Jellyfin, Subsonic, Plex, Mopidy, Deezer). Any single platform changing or restricting API access could break functionality.−6

Score history

41 · confidence 41 · config v1First score · 11 Oct 2026

Music scrobbling aggregation across sources

Overview

Verdict

Build this business

Score breakdown

Risk penalties

Score history

Validation gate

Evidence · 4 items

Market validation

Growth

Market

Existing products

Build

Legal reconstruction check

Community