TV channels for cruise ships and offshore sites
Bandwidth-shaped channel packages for ships and offshore sites: lower ladders, aggressive buffering and a cache on board, so a congested link degrades gracefully instead of dropping.
What a cruise or offshore operator gets
- Bitrate-capped variants tuned per vessel link
- On-board cache with scheduled catch-up refresh
- SRT with configurable latency for high-RTT links
- Per-vessel monitoring visible to your bridge IT
HOW THE SIGNAL REACHES THE SHIP
The vessel pulls encrypted SRT from the core site nearest its region, and the region changes as the ship moves: Luxembourg or Frankfurt in northern Europe, Dallas in the Caribbean, Singapore across South East Asia, Johannesburg down the African coast. The feed follows the itinerary rather than staying pinned to one site.
On board, our player appliance or the same job in software terminates SRT and puts out UDP multicast for the cabin TVs, exactly as a local headend would. Adaptive HLS / DASH runs alongside it for the guest app, phones and tablets, from the same channels and the same EPG.
SRT latency is configured per vessel from the measured round trip, not from a default, and ARQ repairs the losses a satellite link produces without dropping the service. Where the link is shared with guest internet, each channel runs at a capped constant bitrate so television cannot starve the rest of the ship.
SATELLITE BACKHAUL AT SEA
A ship is the hardest delivery case we have: round trips of several hundred milliseconds on geostationary capacity, bandwidth that changes with beam, weather and passenger count, and hours in port or at a canal where the link is worse than the brochure suggests. The bouquet has to degrade in a way the guest tolerates.
So we shape it. Channel variants are capped, under 2 Mbps per channel where the link is tight, with the ladder trimmed to the rungs the cabin screens actually use. The bouquet itself is trimmed too: the channels the passenger mix on that itinerary watches, rather than every feed in the catalogue.
An on-board cache holds catch-up and restart material and refreshes on a schedule you set, so replay viewing does not touch the satellite at all during peak hours. Per-vessel monitoring of bitrate, loss, retransmission and uptime per channel is visible to your shore IT and to your bridge team, not only to our NOC.
Rights matter here as much as bandwidth. Cabin viewing is a separate grant from redistribution, territorial windows move with the ship, and we state per channel what the rights holder allows before the vessel sails rather than after a complaint.
GET IT INSTANT
Send us the vessel list, the itinerary regions and the passenger mix. We propose a bouquet and a per-channel bitrate cap against the link you actually have, confirm the per-channel monthly rate, and issue endpoints within 12 hours. No setup fee, and volume discounts apply from ten channels.
Test it in port first with the free three-day trial. It ships both encrypted SRT and adaptive HLS / DASH for the channels you pick, so the cabin multicast path and the guest app path can be measured over the real satellite link before a contract exists.
HOW IT IS PRICED
| SRT DELIVERYEncrypted MPEG-TS over the public internet | EUR 150 |
| HLS / DASH ADAPTIVEABR ladder + LL-HLS/DASH, packaged and CDN-delivered | EUR 200 |
| MultiDRMWidevine + PlayReady + FairPlay | + EUR 19 |
| Cloud DVR & replay7-day catch-up window | + EUR 29 |
| Restart & start-overJump to the start of the running show | + EUR 15 |
| EPG & metadata feedXMLTV + JSON, 14 days ahead | + EUR 9 |
Per channel, per month, excluding VAT. Volume discounts apply automatically from ten channels (up to 20%), a 12-month term saves a further 10% and a 24-month term 15%. Both are applied in the order total. 6 core sites, dual origin per channel.
LOOKING GLASS
Which of our points serves you fastest?
| Point of presence | Role | Distance | RTT | Jitter | Loss |
|---|---|---|---|---|---|
| LondonUK | edge | 0 km | 4 ms | 0.4 ms | 0.00 % |
| LilleFR | edge | 243 km | 7 ms | 0.7 ms | 0.00 % |
| ManchesterUK | edge | 261 km | 7 ms | 0.4 ms | 0.00 % |
| AmsterdamNL | edge | 358 km | 8 ms | 0.3 ms | 0.00 % |
Estimated from great-circle distance and our routing table. Ask the NOC for a live probe from your own prefix before you sign.
PLAYER APPLIANCE
PLAYOUT SOFTWARE