vintikzzzz

There are currently around 14 individual components involved — torrent engine, HLS pipeline, subtitles, storage, APIs, etc.

It’s technically possible to run everything manually without Docker, but you’d need to wire all services together, manage configs, ports, and background jobs.

That’s why I strongly recommend the Docker setup — it’s the easiest way to get things running.

You can absolutely take a look at the Dockerfile (https://github.com/webtor-io/self-hosted/blob/main/Dockerfil...). It should give you a clear idea of how things are connected, if you want to replicate it manually on FreeBSD.

Good question.

Even though Webtor doesn’t host or index any content itself, users can generate direct links like https://webtor.io/{infohash} to access specific torrents. Sometimes these links get shared publicly — on forums, blogs, or aggregators — and that’s usually how DMCA notices find their way to me.

When that happens, I remove access to that specific infohash from the hosted service. It’s not about removing stored files (since there’s no persistent storage), but about disabling further processing of that particular torrent.

The content is only partially downloaded to the servers, and only on demand. Storage is limited — old, inactive cached data is removed when space is needed for new requests.

There’s also the ability to revisit previously used content via direct links like https://webtor.io/{infohash} — this lets users bookmark a stream or return to it later. However, availability still depends on whether the content is cached or needs to be fetched again.

I actually experimented with making content indexable in the past, but many torrents turned out to be pirated — and eventually triggered DMCA notices. So I chose not to publicly expose anything on the hosted version.

Automation is possible: there’s a public API and a lightweight SDK for embedding content into external websites.

True, Popcorn Time was slick — but if I remember correctly, it runs as a local app and immediately connects you to the swarm. That means your IP is exposed and you’re technically distributing content while watching it.

Webtor works differently — all torrent traffic goes through the backend, and your browser just receives the stream over HTTPS. No swarm connection from the user side at all.

So it’s not as feature-rich maybe, but it’s built with privacy and accessibility in mind — especially for people who can’t or don’t want to touch P2P directly.

That’s a valid concern, and I’m aware of the risks involved.

Webtor is a tool, not a content provider — it doesn’t index or host anything itself. Users supply their own torrent or magnet links, and the system processes them on demand, like a torrent client with a browser interface.

That said, if someone uses the hosted version to stream content that triggers a copyright complaint — yes, I may receive a DMCA notice, and in that case I’ll take the content down as required.

This is also exactly why the project is fully open-source and self-hostable — anyone can run it privately, with full control and different legal boundaries depending on their jurisdiction.