Hardware & hosting

What should you actually run this on?

Almost anything that runs Docker can run some of this. The honest answer depends on how many people watch at once, how much you want to keep, and whether you'd rather pay once or pay monthly. Here's how to decide without overbuying.

01 · The short version

What each app needs

Most of these services sit idle most of the time. The ones that will actually stress your machine are Jellyfin when it transcodes, Immich when it processes a photo backlog, and Tube Archivist when it downloads. Everything else is comfortable on very modest hardware.

AppCPURAMGPUStorage
Jellyfin (direct play)LowLowNot neededHowever big your library is
Jellyfin (transcoding)Medium–HighMediumReally helpsSame, plus scratch space
JellyseerrLowLowNoSmall
Sonarr / Radarr / LidarrLowLowNoSmall — config and databases
BazarrLowLowNoSmall
JackettLowLowNoSmall
qBittorrent + GluetunLowLow–MediumNoWorking space for downloads
ImmichMediumMedium–HighHelps a lotLarge and always growing
KimaMediumMediumOptionalYour music library
Uptime KumaVery lowVery lowNoTiny
ArchiveBoxMediumMediumNoGrows steadily
Tube ArchivistMediumMedium–HighNoLarge — video adds up fast
RAM is usually the first thing you run out of. Immich and Tube Archivist both bring their own database and search containers along, and Kima bundles Postgres, Redis and audio-analysis models inside its single container — all of which quietly adds a couple of gigabytes before you've stored anything. 8 GB is a comfortable floor for a mixed stack; 16 GB means you stop thinking about it.
02 · The part people get wrong

Transcoding

Direct play is when the device you're watching on can already handle the file, so Jellyfin just hands it over. Almost no CPU. Transcoding is when it can't, so Jellyfin has to rebuild the video on the fly. That's where a weak machine falls over.

How to need less of it

Store files in formats your devices actually play, keep subtitles as separate files rather than burned-in where you can, and remember that remote viewing over limited upload bandwidth will force a transcode no matter how good your files are.

If you do need it, hardware transcoding is the difference between one struggling stream and several easy ones. Intel QuickSync — available on most Intel chips with integrated graphics — is the most straightforward option, well supported and cheap to get hold of in used and mini PC hardware. A dedicated GPU works too, but is rarely necessary at home.

Passing hardware into a container takes a little care. Hardware transcoding needs the right device mapped into Jellyfin's container and the right drivers on the host. It's very doable, but it's a step that catches people out, so treat it as a follow-up task rather than something to solve on day one.
03 · Pick a machine

Choosing a device

There's no single right answer here. These are the paths most people end up on, and what each one is genuinely good at.

Mini PC

The easy default

Small, quiet, low power, and most Intel models include QuickSync for transcoding. The best balance of effort and result for a first server.

  • Very low running cost
  • Storage usually needs an external enclosure
  • Sits happily on a shelf

Used business desktop

The cheapest good option

Ex-office machines are plentiful, well built and easy to work on. Room for several drives, easy to upgrade, and parts are everywhere.

  • Best value per pound spent
  • Bigger and louder than a mini PC
  • Check it has the ports and bays you need

NAS

When storage is the point

Purpose-built for always-on storage with drive redundancy. Most modern models run Docker, though usually with less CPU headroom than a comparable PC.

  • Drive redundancy handled for you
  • Simple to manage and expand
  • Weaker transcoding on entry models

Old laptop

Free, if you have one

A perfectly reasonable place to start. The built-in battery even acts as a small UPS, so a brief power cut won't take the server down.

  • Set it to stay awake with the lid shut
  • Storage expansion is limited
  • Watch heat if it lives in a cupboard

Raspberry Pi

Light stacks only

Fine for Jellyfin direct play, the *arr apps and Uptime Kuma. Not the machine for transcoding, Immich processing or heavy archiving.

  • Tiny power draw
  • Use an SSD, not an SD card
  • Some images need ARM builds

Custom build

When you know what you want

Maximum control over drives, transcoding and expansion. Worth it once you've outgrown something else and know what your bottleneck actually is.

  • Most expensive up front
  • Most work to plan and assemble
  • Best long-term headroom
Buy for the library, not the CPU. Most people's first upgrade isn't a faster processor — it's more drive space. Whatever you pick, think about how you'll add storage to it in a year.
04 · Running it at home

Self-hosting realities

The server itself is usually the easy part. The things that catch people out are the boring realities of a home internet connection.

Worth checking before you commit
  • Upload speed. Watching from outside your house uses upload, not download, and home connections are often lopsided. This is the single biggest limit on remote streaming.
  • CGNAT. Some providers don't give you a real public address, which makes traditional port forwarding impossible. A mesh VPN like Tailscale sidesteps this entirely.
  • A changing IP address. Most home connections don't keep the same address forever. Dynamic DNS or a tunnel solves it.
  • Power cuts. Decide whether the server should come back on by itself, and whether a small UPS is worth it.
  • Drives fail. Not if — when. Redundancy keeps you running; backups are what actually save your data. They aren't the same thing.
  • Noise and heat. A server in a living room has different requirements from one in a garage.
Think carefully before opening ports. Exposing admin interfaces straight to the internet is how self-hosted servers get compromised. A reverse proxy with proper certificates, or a mesh VPN so nothing is public at all, are both far safer starting points than forwarding a port and hoping.
05 · The rented option

When a VPS makes sense

A VPS is someone else's computer with good uptime and a real public address. That makes it excellent for some jobs in this stack and a poor fit for others, and the dividing line is almost always storage.

Good fits

Small, always-on, public
  • Uptime Kuma, so your monitoring isn't on the machine it monitors
  • A reverse proxy or entry point for remote access
  • A VPN endpoint back into your home network
  • Status pages and small websites

Poor fits

Anything that eats disk
  • A large Jellyfin library
  • A growing Immich photo collection
  • Tube Archivist and long-term archives
  • Anything where bandwidth charges could surprise you

The common pattern is a hybrid: bulk storage and media at home where drives are cheap, with a small VPS handling monitoring and the public-facing side of things. You get reliable remote access without paying monthly for terabytes.

06 · What it costs

Cost comparison

Owned hardware costs more on day one and almost nothing after that. Rented hardware is the reverse. Over a couple of years the gap is usually wider than people expect.

Used mini PC
Ex-office micro form factor
$100–200
up front
plus electricity

Quiet, low power, often has QuickSync. Storage generally lives in an external enclosure.

Easiest start
Used desktop
Tower or small form factor
$150–400
up front
plus electricity

More drive bays and more room to grow. Bigger, warmer and a little louder.

Best value
NAS
Multi-bay enclosure
$300–1,000+
up front, before drives
plus electricity

Built for storage and redundancy. Drives are a serious separate cost worth planning for.

Storage first
Custom build
Self-assembled server
$500–2,000+
up front
plus electricity

Exactly the machine you want. Most expensive and most work, but the most headroom.

Advanced
VPS
Rented virtual server
$0
up front
$5–50+ every month

Running in minutes with a real public address. Storage is limited and gets pricey quickly.

Small services
VPS + cloud storage
Server plus object storage
$0
up front
$20–100+ every month

Scales without buying drives. Watch retrieval and bandwidth charges, which are easy to miss.

Archives
The comparison people forget: a $150 mini PC that lasts three years works out around $4 a month before electricity. A $15/month VPS is $540 over the same period, with less storage. Renting buys convenience and uptime, not savings.

These are rough estimates for orientation only, and they move around constantly. Drive costs, electricity rates and provider pricing all vary — check current prices yourself before buying anything.

07 · Buying it

Hardware picks

As an Amazon Associate I earn from qualifying purchases.

The links below are affiliate links. If you buy through one, this project earns a small commission at no extra cost to you — it pays for the domain and the hardware used to test these guides.

It changes nothing about the advice. Every recommendation here is a description of what to look for, not a specific product we were paid to name. If a cheaper option is better, that is what the page says — see the cost comparison, which recommends a used office PC over anything new. Full detail on the disclosures page.

These are searches rather than single products, because specific models go out of stock and get superseded constantly. Each one is filtered to the specifications that actually matter for a media server, and each explains what you are looking at.

Links update to your region.
No prices here, deliberately. Amazon prices change constantly and any number written into a page is wrong within days. Every link opens the current listing, where the price is whatever it actually is today. The cost comparison gives you honest ballpark ranges to plan with.
Buy the cheapest thing that meets the specification. This is the section of a website most likely to talk you into overspending, so to be plain about it: a used office mini PC at around $150 runs everything in this project comfortably. The more expensive options solve problems you probably do not have yet. Start small and upgrade the specific thing that runs out.
07 · Services

VPN & VPS providers

Gluetun works with a wide range of VPN providers, so this is mostly a question of price, privacy policy and which countries you want to appear in. VPS choice comes down to what you're running and where.

About links on this page

Some links here may eventually be affiliate links, and where that's the case it will say so plainly right next to the link. No service is listed because it pays a commission, and none of the technical guidance changes based on who does. Right now none of the links below are affiliate links. Prices and terms change often, so check with the provider directly.

VPN providers

Mullvad

Flat pricing, no accounts tied to your identity, and a long-standing privacy record. Well supported by Gluetun including WireGuard.

Proton VPN

From the Proton Mail team, with a clear privacy stance and solid WireGuard support. Works well as a Gluetun provider.

Private Internet Access

Long-established provider with broad Gluetun support and a large server network. Runs an affiliate programme we haven't joined.

Surfshark

Competitively priced with unlimited device connections and Gluetun compatibility. Also runs an affiliate programme we haven't joined.

What matters when choosing: that Gluetun supports it, that the provider allows the traffic you intend to send, that WireGuard is available, and that the privacy policy actually says what you think it says. Speed differences between reputable providers matter far less than people assume.

VPS providers

Hetzner

Consistently good value with reliable hardware and generous transfer allowances. A community favourite for small always-on services.

DigitalOcean

Straightforward interface and unusually good documentation, which makes it friendly if this is your first server. Runs an affiliate programme we haven't joined.

Vultr

Wide choice of locations and instance sizes, useful if you want the server geographically close to you.

Contabo

Notably more storage per pound than most competitors, which suits archive workloads. Performance is less consistent, so match it to the job.

08 · Worth knowing about

Other tools you might want

None of these are part of the core modules, and you don't need any of them to start. They're the things people tend to add once the server has been running a while and they've found the rough edges.

09 · In short

Putting it together

If you want a shortcut through all of the above: get a used mini PC or office desktop with 16 GB of RAM and an Intel chip with QuickSync, put a decent-sized drive in it, and use Tailscale so you never have to open a port. That covers most of this stack comfortably and costs less than a couple of months of streaming subscriptions.

Add a small VPS later if you want monitoring that survives your server going down. Add drives when you run out. Upgrade the machine when you actually hit a wall, not before.

Buy modestRun it a whileFind the real limitUpgrade that one thing

The best server is the one you'll actually keep running.

Whatever you build it on, the rules don't change. Only obtain, store and share content you're legally permitted to use, treat downloaded files as untrusted regardless of what your VPN is doing, keep your host and images updated, and back up anything you'd be upset to lose. Better hardware doesn't make any of that optional.