PLEKT / WHY
One watch history. Every server in sync.
Use Plekt as a private manual tracker, a bridge to Trakt, or the local source of truth for a whole mixed media stack.
Build your setup.
YOUR STARTING POINT
No history to import? Start private and local.
Search for a title, mark it watched, choose the date, and keep the record on your own instance. Add connections whenever your stack grows.
PlektWHY THE MIDDLE MATTERS
A bridge is useful when it remembers.
Media players are good at playback. Trackers are good at sharing. Plekt keeps the durable, explainable record between them.
One local record
Every watched event, resume position, source, and rewatch has a durable place to land before it is sent anywhere else.
One bridge, fewer conflicts
Connected services do not need to write directly to each other. Plekt is the point of comparison that prevents stale state from winning silently.
One visible result
Sync Activity records the origin, every destination, the outcome, and the retry path when a provider is unavailable or a title needs matching.
WHEN THE STACK CHANGES
Your history does not have to start over.
Servers go offline, libraries get rebuilt, and providers occasionally disagree. Plekt keeps the local archive steady while the rest catches up.
See sync tools and recovery paths- A media server is rebuilt: push the local record back when the library is ready.
- A provider is offline: keep the local history and retry only the missing destination later.
- Two services report the same watch: collapse the delivery echo, preserve a genuine rewatch.
- You add another server: connect it to the same record instead of starting over.