sleepingpanda4/jellypulse — explained in plain English
Analysis updated 2026-05-18
Let Jellyfin users report playback issues like glitching or wrong subtitles in one click.
Give a Jellyfin server admin a live dashboard of viewers, CPU, RAM, and transcoding activity.
Get notified in Discord, Slack, or email whenever a new playback report comes in.
| sleepingpanda4/jellypulse | 0xkinno/neuralvault | 0xmayurrr/ai-contractauditor | |
|---|---|---|---|
| Stars | 1 | 1 | 1 |
| Language | TypeScript | TypeScript | TypeScript |
| Setup difficulty | moderate | hard | easy |
| Complexity | 3/5 | 4/5 | 2/5 |
| Audience | ops devops | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires Docker Compose and a Jellyfin server with a dedicated API key.
JellyPulse is a self hosted companion dashboard for Jellyfin, the open source media server. It gives everyday users an easy way to report playback problems they run into, like glitching or wrong subtitles, and gives administrators a single place to see live activity, review those reports, and keep the server running smoothly. Users sign in with their existing Jellyfin account, and JellyPulse never stores Jellyfin passwords itself. When someone hits a problem, a one click report automatically captures details like which show, which device, what point in playback, and the issue type, along with five minutes of surrounding server telemetry to help diagnose it later. Administrators see live viewer cards showing who is watching what, along with CPU, memory, optional GPU, and transcoding activity, and can send notifications through services like Discord, Slack, email, Telegram, and several others when new reports come in. The project is designed to run in Docker, most easily through a ready made Docker Compose stack that includes JellyPulse itself, a PostgreSQL database, automatic secret generation, and a restricted proxy so the dashboard can only see the parts of Docker it actually needs. It is commonly deployed through Portainer for people managing their home server through a web interface, but can also be run directly with Docker Compose from a terminal. Because it can see sensitive account and server information, JellyPulse encrypts stored API keys, notification credentials, and telemetry tokens, and the documentation recommends only exposing it over HTTPS and keeping the database and its Docker proxy private rather than published to the internet directly. If Jellyfin runs on a different machine than JellyPulse, an optional lightweight telemetry agent can be deployed alongside it to report that machine's CPU and memory back to the dashboard. Regular backups of both the database and the secrets volume together are important, since the encryption key used to protect stored secrets cannot be recovered if it is lost or replaced.
A self-hosted dashboard companion for Jellyfin that lets users report playback problems in one click and gives admins live monitoring, analytics, and notifications.
Mainly TypeScript. The stack also includes TypeScript, Docker, PostgreSQL.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
double-check against the repo, no cap.