I did what everyone does at first. I clicked through logs, stared at device names, and tried to match (computing)” target=”blank” rel=”noopener noreferrer”>bandwidth so people I had never met could binge shows.

Traditional tools like Tracearr interesting to me is not that it reproduces the usual stats. It layers rules on top of that raw data, like “impossible travel” when an account appears in New York and London within half an hour, or simultaneous locations from the same profile at the same time. It shows velocity when an account burns through way too many IPs in a short window.

In my house, that matters. My wife might watch from the living room and then from her phone on the train, so a couple of IPs is normal. My son will absolutely spike bandwidth with games and streaming at the same time. Those patterns are noisy but still human. Fifteen unique IPs in a month for one account, across countries, is a different story.

That is not “my cousin on vacation.” That is an account making the rounds.

Self-hosting with actual boundaries

Here is where I land on it. Self-hosting is a net positive, but only if you keep some control. Hosting Plex, Jellyfin, or Emby for friends can feel generous at first, until the server starts lagging, the storage fills, and you realize you do not recognize half the devices hitting your box.

Having trust scores, geo rules, concurrent stream limits, and even the option to kill sessions from a UI is not about turning into Netflix. It is about not accidentally becoming free infrastructure for people you never agreed to support.

If I am paying for the hardware in my rack and the fiber into my house, I want my generosity to be intentional, not assumed.