Autopulse

Autopulse is a lightweight web service that receives notifications from media organizers like Sonarr, Radarr, and Lidarr and updates the corresponding items…

  • Automation
  • Media Applications
  • Media Servers
  • Other
  • Productivity
  • Tools & Utilities
Autopulse is a lightweight web service that receives notifications from media organizers like Sonarr, Radarr, and Lidarr and updates the corresponding items in media servers like Plex, Jellyfin, and Emby. It is designed to be efficient, only updating the items that have changed to reduce the load on media servers.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

71/100 Good

Maintained
100last commit 13 days ago
Popular
55556 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
70no serious findings, 8 minor, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 23 days ago

GitHub stars
556
Open issues
10
Last commit
2026-11-08
Latest release
v2.0.0
License
MIT
Activity
declining

Checked 8 days ago - source: GitHub (dan-online/autopulse)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set a username and password Set auth.username and auth.password in your YAML before starting the app. Without them, you may leave the web interface unprotected, so anyone who can reach the port could use Autopulse. source
  • Choose the right web port Set app.port (the example uses 2875) and make sure that port is reachable where you'll open the web page. If it's wrong or blocked, Autopulse may be running but your browser won't be able to connect. source
  • Keep the database file safe Point app.database_url to a SQLite (small file-based database) location you can back up, such as sqlite://autopulse.db. It stores Autopulse's internal state, so losing it or making it read-only can break event tracking and retries. source

Fetched 47 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do Sonarr, Radarr, or Lidarr tell autopulse about new files?

They call an autopulse trigger endpoint when a file is ready to be processed. The manual trigger endpoint defaults to /triggers/manual.

Can autopulse verify a file before updating Plex or Jellyfin?

Yes. It can check that the file exists before updating the target and optionally wait for the file to match a provided hash.

Which Docker tag supports both Postgres and SQLite?

Use the latest tag, which is the full image with support for both Postgres and SQLite. The latest-postgres and latest-sqlite tags are smaller images for a single database.

Answers sourced from github.com

Community

Collected 47 days ago - public community threads