Use case

Plex / Jellyfin on a VPS.
Your library, your bandwidth.

Run Plex, Jellyfin, or Emby on a Pulsar67 VPS so your library is reachable from anywhere with generous bandwidth included, without exposing your home IP, fighting CGNAT, or asking your ISP for an open port.

Why a VPS

Home Plex works until you leave the house.

Hosting Plex at home is great until your ISP decides residential uplink isn't for "video servers", you're behind CGNAT, or you want to share with family and don't want to give them your home IP.

A VPS gives Plex a clean public IP, business-class uplink, and a static address so the apps "just connect." Pair with rclone mounts (Google Drive / OneDrive / S3) or your own storage and it's effectively unlimited.

Business uplink

10 Gbps backbone. Plex Direct Play streams hit line rate; no residential cap.

Clean public IP

Static address, not behind CGNAT. The Plex clients connect first try.

rclone mounts

Mount cloud storage as a filesystem. Effectively unlimited library size for ~zero extra cost.

SAS SSD metadata

Library scans and metadata writes hit SAS SSD. Cover-art browsing actually feels snappy.

Recommended plan

Sized for streams and transcodes.

Direct Play barely needs CPU. Transcoding hits the cores hard.

Pulsar Starter
Direct Play, 1-2 viewers, rclone mount
$5/mo
  • 1 vCPU
  • 2 GB RAM
  • 40 GB SAS SSD (+ rclone for library)
Order Starter

CPU-only transcoding is slower than GPU. If your viewers' clients can Direct Play, Starter is fine for most H.264 / H.265 libraries.

What you'll need

A streaming-ready box in under an hour.

Why Pulsar67

A media box you can actually point your family at.

Dedicated public IP

Not CGNAT. Plex remote access works the first time.

10 Gbps uplink

Even 4K streams per viewer barely register on this network.

DDoS protection

Plex shares often get hit by abuse. Always-on at our edge.

Flat price

$5/$15/month flat. No per-stream or per-viewer billing.

Stream from anywhere.

A Plex or Jellyfin box your family can reach without your home IP, your home ISP, or your home power outages.

Field notes

Plex and Jellyfin deployment notes

Concrete setup details for the first deploy, the firewall, and the first thing to check when something acts strange.

Ports

Plex uses TCP 32400. Jellyfin uses TCP 8096. Put web access behind HTTPS where possible and limit admin exposure.

RAM

Starter is enough for Direct Play. Pro gives more room for metadata scans and multiple users, but GPU-heavy transcoding is not the goal on these VPS plans.

Config

Use Direct Play-friendly media formats, mount storage carefully, and keep metadata/cache on local SAS SSD.

First check

If streams buffer, check whether the client is transcoding, then inspect bitrate, upload cap, and remote storage latency.