Disclosure: this article contains affiliate links. If you buy through them we may earn a commission at no additional cost to you. Our recommendations are based on the evidence recorded alongside this article, and prices were verified on the date shown.

If you're reading about Orion because you want a torrent client and media server you fully control, the verdict is simple: it's self-hosted, open-source software on GitHub, not a subscription app — you supply the server, the setup, and the maintenance. Skip it if you want something that works without touching a terminal.

What changed and why it matters

On August 20, 2026, a Show HN post titled "Orion - A Self-hosted torrent client and media server" appeared, submitted by user flarbooga and pointing to the project's source at github.com/guyavrhm/orion. That's the entire public record right now: a project announcement and a source repository, not a company or a product launch.

Why that matters if you're evaluating Orion: it isn't a business shipping a hosted product you sign up for. It's code you clone, build, and run on infrastructure you own or rent — which turns the buying decision from "which plan do I pick" into "where do I run this myself."

The detail

Orion is described, by its own Show HN submission, as a self-hosted torrent client and media server — two functions in one project: adding and managing torrent downloads, and serving that media back to you afterward. Beyond that description, the only public source is the GitHub repository itself; there's no separate spec sheet, pricing page, or hosted demo listed for it.

"Self-hosted" is the operative term if you're new to it: the software runs on hardware you control — a home server, a VPS, a NAS — not on servers Orion's author manages for you. You take on setup, updates, and security patching yourself. That's the tradeoff for not paying a subscription: the code is free on GitHub, but you supply everything else. If you want a torrent client or media server with a support line, an app-store listing, and zero server administration, Orion — and self-hosted tools generally — isn't it. Skip it and look at a managed alternative instead.

What it means for you

Running Orion means running a persistent process with access to disk storage — the opposite of a stateless request-response app. That's why the practical question isn't "which torrent client" but "where does the always-on part of my stack live." For the storage- and process-heavy piece — the actual torrent and media workload — a VPS with attached block storage is a closer fit than serverless functions. The compromises there, droplets versus object storage versus managed databases, are broken down in Self-Hosting a Web Archive on DigitalOcean: Droplets, Spaces and Managed PostgreSQL Compared, which works through the same self-hosting math for a different persistent workload.

Not every part of a self-hosted project has to live on that same box, though. If you end up building a status page, an API front end, or a dashboard to sit alongside a tool like Orion, that piece is stateless and a natural candidate for serverless hosting rather than tying up your VPS. See current pricing at the merchant shows the current plan tiers and limits before you decide whether the web-facing half of your stack belongs there or on the same server as everything else.

The decision isn't whether Orion is good — the evidence here doesn't cover its performance or reliability, so this piece doesn't claim either way. The decision is whether you're willing to run and maintain a server for it. If yes, plan for the persistent workload and the web-facing pieces separately. If no, this isn't the project for you yet.