This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Plembfin
Explainable watch sync for Plex, Emby, Jellyfin and Trakt
Plembfin is a local-first watch-state hub for Plex, Emby, Jellyfin and Trakt. Keep watched history, resume progress and rewatches canonical in SQLite, then sync each destination with an explainable activity ledger, targeted retries, backups and a private dashboard. Self-host it with Docker Compose and see every delivery reason instead of trusting a single sync status. Website: https://plembfin.com
Hi Product Hunt. I built Plembfin for the point where one media server becomes three and “watched” is no longer a trustworthy fact.
Plembfin keeps a private canonical record on your own hardware, then reconciles watched state, resume progress, and repeat plays across Plex, Emby, Jellyfin, and Trakt. The feature I care most about is the Sync Activity ledger: it shows the source, destination, outcome, reason, and retry context for each delivery instead of hiding everything behind one sync status.
The current release is v1.0.0, AGPL-3.0, self-hosted, and available through Docker Compose. It also includes Now Playing, history, stats, metadata, Seerr integration, and backups.
I would love feedback from people with a mixed media stack: what would you need to see before trusting a local tool with your watch history?
The implementation was heavily AI-assisted under my direction. I reviewed the generated changes, tested the integrations and browser flows, and maintain and review the project. AI is not required at runtime.
No comment highlights available yet. Please check back later!
About Plembfin on Product Hunt
“Explainable watch sync for Plex, Emby, Jellyfin and Trakt”
Plembfin was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #121 on the daily leaderboard. Plembfin is a local-first watch-state hub for Plex, Emby, Jellyfin and Trakt. Keep watched history, resume progress and rewatches canonical in SQLite, then sync each destination with an explainable activity ledger, targeted retries, backups and a private dashboard. Self-host it with Docker Compose and see every delivery reason instead of trusting a single sync status. Website: https://plembfin.com
Plembfin was featured in Open Source (68.9k followers) and GitHub (41.4k followers) on Product Hunt. Together, these topics include over 45.4k products, making this a competitive space to launch in.
Who hunted Plembfin?
Plembfin was hunted by New User. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Plembfin stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
New User
Hi Product Hunt. I built Plembfin for the point where one media server becomes three and “watched” is no longer a trustworthy fact.
Plembfin keeps a private canonical record on your own hardware, then reconciles watched state, resume progress, and repeat plays across Plex, Emby, Jellyfin, and Trakt. The feature I care most about is the Sync Activity ledger: it shows the source, destination, outcome, reason, and retry context for each delivery instead of hiding everything behind one sync status.
The current release is v1.0.0, AGPL-3.0, self-hosted, and available through Docker Compose. It also includes Now Playing, history, stats, metadata, Seerr integration, and backups.
I would love feedback from people with a mixed media stack: what would you need to see before trusting a local tool with your watch history?
The implementation was heavily AI-assisted under my direction. I reviewed the generated changes, tested the integrations and browser flows, and maintain and review the project. AI is not required at runtime.