Optimized for streaming platforms
Media Servers
Dedicated media server configurations for Plex, Jellyfin, Emby, VOD libraries, content archives, and platforms where storage layout and compute are as important as outbound bandwidth.
Port range
10-100 Gbps
Traffic terms
Unmetered port
Transcode
CPU/GPU scoped
Storage
NVMe + HDD
Software
Plex / Jellyfin / Emby
From
€79/mo
Configurations
Storage
2x2 TB NVMe + 2x16 TB HDD
Compute
Intel Xeon E-2388G · 32 GB DDR4
Network
10 Gbps · Unmetered port
Storage
2x4 TB NVMe + 4x16 TB HDD
Compute
AMD Ryzen 9 7950X · 64 GB DDR5
Network
20 Gbps · Unmetered port
Storage
4x4 TB NVMe + 8x16 TB HDD
Compute
AMD EPYC 7443P · 128 GB DDR4
Network
40 Gbps · Unmetered port
Storage
12x8 TB NVMe + 24x20 TB HDD
Compute
Dual AMD EPYC 9654 · 1 TB DDR5
Network
100 Gbps · Unmetered port
A media server is three resources in tension: storage (how much library you hold), transcoding (how many simultaneous re-encodes you run), and network (how fast you deliver). Our tiers balance those three — from a personal library to a commercial VOD platform.
Use cases
Workload: Remote viewers stream files already compatible with their players.
Sizing: Disk throughput and outbound bandwidth are usually more important than CPU.
Fit: Media tiers combine storage-heavy layouts with 10-100 Gbps ports.
Limit: Rights to all hosted media remain the customer's responsibility.
Workload: Users request streams in formats or bitrates different from source files.
Sizing: CPU/GPU capacity controls concurrency; storage and port speed only help after encoding is handled.
Fit: Higher tiers can be scoped around compute and GPU needs.
Limit: A bandwidth upgrade will not fix a CPU-bound transcode queue.
Workload: Large content library with hot and cold media tiers.
Sizing: NVMe for hot titles, HDD for archive, and a backup policy are the main design decisions.
Fit: Media configurations make storage topology part of the buy.
Limit: Backup retention must be ordered separately if required.
You can run Plex, Jellyfin, Emby, and custom VOD stacks on standard Linux or Windows server builds. Customers are responsible for licenses, media rights, and application security.
Direct play mostly uses bandwidth and storage. Transcoding re-encodes video and can quickly become CPU/GPU-bound. Choose a higher compute tier or GPU option when many users need format or bitrate conversion.
Backup options can be quoted with the server. Do not treat a dedicated server as a backup system by default; production media libraries should have a separate backup or replication plan.
Related paths
Compare adjacent bandwidth, media, and pooled-capacity routes before choosing a configuration.
