Complete history
Extended streaming history is imported, normalised and reconciled, so a play from 2009 sits in the same table as one from this morning.
Independent studio · Gothenburg
SpotRecap is a private analytics platform for music. It holds every play you have ever streamed, grows a model of taste from that record, and answers questions about it in plain language.
Live in private beta · EU data region · 271,712 plays indexed
Measured against the reference history on 9 November 2026.
The product
Most listening stats stop at a wrapped year. SpotRecap starts with the complete record — every play, track, feature and date — and keeps learning from what you listen to next.
Extended streaming history is imported, normalised and reconciled, so a play from 2009 sits in the same table as one from this morning.
Audio features, listening context and explicit feedback build a per-track vector space — the basis for every recommendation the product makes.
Ask “what did I play the week I moved?” and get a real answer with the numbers behind it, streamed back as it is computed.
The assistant keeps durable notes about your taste and past questions, so context carries between sessions instead of resetting.
The phone client is in build now: a 380 px design width, installable, one-handed. Anything not usable there does not ship.
Six model backends sit behind one abstraction layer, with a fallback chain and per-request routing. No lock-in to a single vendor.
Why it exists
The insight a listener actually wants is not an annual summary. It is the long view: what changed, what stayed, which records keep coming back after a decade.
SpotRecap was built to answer that question for one listener first — a testbed that had to survive seventeen years of messy exports before it was allowed to become a product.
Single-tenant storage, no advertising pipeline, no resale of listening data. Export at any time.
Every number on screen is traceable to records you own — down to the individual play.
Recommendations carry the evidence that produced them: features, neighbours and history.
A cost ladder is a first-class roadmap phase, not an afterthought once the bill arrives.
Roadmap
Phases ship in public order. A phase is finished when it is deployed, measured on a phone, and has a test that fails loudly if it breaks.
Full history import, 14-table schema, materialised views and vector indexes, plus the analytics API that everything else reads from.
Thirteen question handlers, answers streamed as they are computed, and a provider abstraction with an ordered fallback chain.
Track vectors, listening context and feedback stored so the model improves with use and context survives between sessions.
An installable progressive web app at a 380 px design width, with the dashboard, explore and chat surfaces in one shell.
Year recaps, streaks and artist trajectories, followed by playlist tools and a discovery engine that explains itself.
The team
Founder · Engineering
Data platforms and backend systems. Built the ingestion pipeline and the query layer the product runs on.
Product · Design
Product direction and interface design. Responsible for the phone-first shell and the visual language.
ML · Infrastructure
Recommendation models, evaluation and the cloud estate — from cost controls to release automation.
Private beta
Access is granted in small batches so the model has time to learn each history properly. Tell us what you listen to and we will be in touch.