Metabase vs Your Spotify
| Tagline | Easy-to-use open-source BI and embedded analytics for everyone | Record your Spotify listening history and explore personal statistics via a web app |
| Category | BI & Dashboards | BI & Dashboards |
| Replaces | Tableau, Power BI, Looker | Tableau, Looker, Power BI |
| GitHub stars | 48k | 4.5k |
| Language | Clojure | Nodejs |
| License | AGPL-3.0 | MIT |
| Self-host difficulty | 2/5 Easy | 3/5 Moderate |
| Deploy options | One-Click Docker Docker Compose Kubernetes Manual | Docker Docker Compose |
| Managed hosting | ||
| Last updated | today | 20 days ago |
| View repo | View repo |
Where each falls short
The honest trade-offs — what you give up with each, versus the proprietary tools they replace.
Metabase
- Advanced data modeling, row-level security, and SSO are gated behind the paid Pro/Enterprise editions
- Charting and visualization depth is more limited than Tableau or Power BI
- No deep semantic modeling layer like Looker's LookML
- Performance can degrade on very large datasets without careful tuning or caching
Your Spotify
- Limited to Spotify data only; no support for other music services
- Requires setting up a Spotify developer app and OAuth credentials
- No custom alerting, reports, or data export features
- MongoDB dependency adds operational overhead compared to simpler dashboards
Bottom line
Choose Metabase if you want the lower-effort setup; choose Metabase for the larger community and ecosystem. Metabase has seen more recent development. Open each guide below for deploy steps and the full feature gap.
Your Spotify
Record your Spotify listening history and explore personal statistics via a web app