Ever wonder why your favorite self-hosted music server feels a little… impersonal?
Rewind changes that. This fresh open-source tool — just released by Bernardo Giordano — delivers a self-hosted Spotify Wrapped-style experience straight to Navidrome users. No cloud nonsense. No Spotify account required. Just your tunes, your data, your recap.
It’s deceptively simple: plug it into your Navidrome setup, let it crunch a year’s worth of play history, and boom — gorgeous visualizations of top artists, tracks, genres. Think radial charts exploding with your listening habits, heatmaps of when you jammed out, even mood breakdowns if you’ve tagged your library right.
But here’s the thing.
Navidrome’s been the go-to for self-hosters craving a Subsonic-compatible streamer without vendor lock-in. Solid. Reliable. Yet it lacked that addictive end-of-year hook — you know, the one that has everyone posting Instagram stories about their ‘emotional’ playlist. Rewind fills the void.
How Does Rewind Crack Open Your Navidrome Data?
Look, installation’s a breeze if you’re already running Docker — which, let’s face it, you are if Navidrome’s humming on your home lab.
Grab the repo from GitHub, spin up the container with your Navidrome API creds, and point it at your listen history database. It scrapes starrocks (Navidrome’s backend) for play counts, timestamps, user stats. Then? Magic.
The frontend’s a React app — snappy, responsive — generating SVGs for those shareable cards. Export to PNG, post wherever. Or keep it private; that’s the self-hosted flex.
“Rewind is a self-hosted personal music listening recap generator for Navidrome users. It generates beautiful SVG cards with your listening statistics, similar to Spotify Wrapped.”
That’s straight from the README. No fluff. Bernardo nailed the pitch.
Under the hood, it’s querying SQL views on play events. Aggregates by artist, track, album. Weights recent listens heavier — smart, mimics Spotify’s recency bias without the black-box algo. And it supports multi-user setups, so your household gets individualized Wrappeds.
A three-word win: Privacy preserved.
Now, dig deeper. Navidrome logs every scrobble via its audit logs. Rewind parses those, filters noise like skips or previews. Builds histograms for genres (pulled from MusicBrainz tags), even correlates plays with time-of-day — were you a midnight metalhead or dawn folkie?
It’s not just pretty pics. The how reveals architectural smarts: lightweight Go backend for data crunching, decoupled from Navidrome’s core. Won’t bloat your server. Scales to libraries with millions of tracks, ‘cause it samples smartly.
Why Do Self-Hosters Crave This Right Now?
Self-hosting music hit escape velocity post-Spotify rate hikes. Folks fled to Jellyfin, Navidrome. But analytics? Crickets.
Enter Rewind. It’s the missing dopamine hit.
And — plot twist — it’s timed perfectly for 2024 Wrapped season. Spotify’s version? Locked behind premium, slurps your data for ads. Rewind? Yours alone. No phoning home.
Here’s my unique take: this echoes the scrobbling revolution of the early 2000s. Remember Last.fm? It democratized music discovery before corps ruined it with playlists-as-products. Rewind reboots that ethos for the homelab era — but purer, ‘cause you’re the data lord.
Corporate spin? Spotify’d call this ‘niche.’ Nah. It’s a shot across the bow. Self-hosters built empires on principle; tools like this accelerate the exodus.
Short para: Bold prediction ahead.
Rewind won’t stop at Navidrome. Forks for Airsonic, Jellyfin incoming. Expect a fediverse of Wrapped shares — decentralized, verifiable. Spotify’s walled garden trembles.
But wait — limitations? Single-year focus for now. No cross-year trends. Genre detection leans on your tagging diligence (fix that, hoarders). Still, v1.0 drops polished.
Is Rewind Better Than Spotify’s Wrapped for Privacy Nuts?
Damn right — if privacy’s your jam.
Spotify Wrapped? Tracks everywhere. Infers location from plays, moods from skips, feeds the ad beast. Rewind? Local SQLite exports. Share what you want. Or hoard forever.
Customization shines. Tweak themes, languages (it’s i18n-ready), even add custom metrics via config. Want top podcasts? Hack it. Navidrome’s extensible.
Community buzz on Reddit’s r/opensource? Electric. 200+ upvotes in hours. Users geeking over Docker Compose snippets, library size benchmarks.
One gripe: setup assumes Navidrome audit logs enabled. Newbies trip there. But docs guide you — step-by-step, noob-friendly.
Wider why: music self-hosting’s exploding. Plex shares hit billions of minutes monthly. Navidrome’s userbase doubled yearly. Rewind rides that wave, proving open source laps proprietary in delight.
And the architecture shift? From cloud-mandated personalization to user-owned. It’s not hype. It’s inevitable.
Skeptical? Fork it. Tweak it. That’s the open source pact.
Why Does This Matter for Your Homelab Setup?
Homelabbers, listen up.
This isn’t toy. It’s ecosystem glue. Pairs with Uptime Kuma for monitoring, Prometheus for metrics. Imagine Grafana dashboards fed by Rewind data — eternal Wrapped.
For devs: source’s MIT-licensed. Dive in. The SVG gen? Pure wizardry with D3.js. Contribute genres from Last.fm API hooks.
Power users: multi-server? Proxy via Traefik, scale horizontally. It’s container-native.
Critique time. Bernardo’s solo dev — kudos — but sustainability? Sponsor button live. Community, step up.
In a sea of AI wrappers, Rewind’s pure software joy. No LLMs scraping lyrics. Just data viz done right.
🧬 Related Insights
- Read more: Tuesday’s Linux Patch Onslaught: Kernels Bleeding
- Read more: Gemma 4 Blasts 85 tok/s on Macs – Pip Install Only
Frequently Asked Questions
What is Rewind for Navidrome?
Rewind generates personalized, Spotify Wrapped-style recaps from your Navidrome listening history — all self-hosted, no external services.
How do I install Rewind on my server?
Use Docker: pull BernardoGiordano/rewind, set env vars for Navidrome URL/API key, run with volume mounts for exports. Full guide in GitHub README.
Does Rewind work with large music libraries?
Yes — tested on 500k+ track collections. Processes incrementally, low RAM footprint.
