Managed tunnel, edge POPs, fair use.
Relay sends viewers through a regional edge node. Pro enforces 10 concurrent streams; Pro Unlimited and Founder's Pass are unlimited within fair-use bandwidth guidance.
How relay works
Your Jellyfin server runs a sidecar that maintains an outbound connection to a Finderwave edge node. When a viewer starts a relay session, they receive a stream URL and short-lived session token. The edge forwards authenticated requests over that tunnel — your home IP is never exposed to viewers.
Direct-access tiers never use this path. If you downgrade from relay to a direct tier, existing relay sessions stop when their tokens expire.
Regions and stream URLs
Each relay server is assigned a primary POP (point of presence). Stream URLs use the regional hostname — for example eu-west1.stream.finderwave.app — so traffic stays close to your viewers when possible.
You pick the primary region in server settings. If a POP is unavailable, routing may fall back per our ops runbook; Business customers can contract for dedicated capacity.
Concurrent streams
Pro enforces 10 concurrent relay streams per account at the API when session tokens are issued. If an eleventh viewer tries to start a relay session, they receive a clear error — upgrade to Pro Unlimited if you routinely hit the cap.
Pro Unlimited and Founder's Pass have no hard concurrent stream cap; bandwidth still follows the Fair Use Policy.
Fair use pointer
Relay costs real bandwidth. Monthly guidance figures (not silent hard cut-offs) are documented in the Fair Use Policy— roughly ~2.5 TB/month on Pro and ~6 TB/month on Pro Unlimited and Founder's Pass.
We email before any enforcement action. Direct tiers are unaffected. Questions: [email protected].