Apache ECharts vs Your Spotify
| Tagline | Powerful, declarative charting library for embedding interactive visualizations | Record your Spotify listening history and explore personal statistics via a web app |
| Category | BI & Dashboards | BI & Dashboards |
| Replaces | Tableau, Power BI | Tableau, Looker, Power BI |
| GitHub stars | 67k | 4.5k |
| Language | TypeScript | Nodejs |
| License | Apache-2.0 | MIT |
| Self-host difficulty | 2/5 Easy | 3/5 Moderate |
| Deploy options | Manual Docker | Docker Docker Compose |
| Managed hosting | ||
| Last updated | 7 days ago | 23 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.
Apache ECharts
- Library only; no built-in query layer or data connector UI
- Requires custom development to build a full dashboard application
- No user management or saved-dashboard persistence out of the box
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 Apache ECharts if you want the lower-effort setup; choose Apache ECharts for the larger community and ecosystem. Apache ECharts has seen more recent development. Open each guide below for deploy steps and the full feature gap.
Apache ECharts
Powerful, declarative charting library for embedding interactive visualizations
Your Spotify
Record your Spotify listening history and explore personal statistics via a web app