Hardware for streaming workloads, on your terms. Buy a machine outright, have us source and configure one and stand it up in the location you name, or bring your own rack and let us host it.
Reply within 3 business hours. No sales sequence.
Most vendors give you one option and call it a product. Streaming teams arrive with very different constraints, so there are three.
We specify and supply the machine, you own it. It goes on your balance sheet and into your rack, wherever that rack happens to be.
Suits teams with their own facility, or a capex budget that prefers hardware to a subscription.
We build the configuration around your workload and stand it up in the location you name, with transit chosen for that market. If the build needs hardware we do not already hold, we buy it in: the capital is ours, you pay a monthly figure. You are not limited to a stock list.
Suits teams who want capacity in a specific city without opening a relationship with a data centre, or without putting hardware on their own balance sheet.
You already own the hardware and it needs somewhere to live. We take the rack into a data centre, give it power, cooling and transit, and keep hands available for the physical work.
Suits teams who have made the hardware decision already and need the facility, not the machine.
The arrangement changes what you pay for and who owns what. Everything else about the build, sizing, locations and transit, is decided the same way in all three.
Served fromhttps://cdn84906683.blazingcdn.net/boxing/hls/master.m3u8 · Segments: 4 s · Footage: Pixabay, free licence A streaming server is only as useful as the software on it, and that software is yours. Here is the honest division of labour.
The specification, the build, the network it sits on and, where we host it, the power and the physical work. What we operate is monitored by us around the clock, and the availability commitment for your build is written into your order.
Ingest, the media server, packaging and manifests, your ladder and your DRM decisions. We do not transcode, re-package or generate manifests on any of our infrastructure, and we say the same on Streaming CDN.
If the encoding itself is the bottleneck rather than the server it runs on, start from Video Content Processing Servers.
Four platform classes cover almost every streaming build, whether you buy the machine outright, have us place it, or bring your own rack. The stack that runs on them stays yours.
Where the mezzanine and the packaged renditions live. Flash in front of disk, so the catalogue is read fast and stored cheaply.
The node that answers players. Sized so a live window and a hot VOD tail both stay in flash.
For teams that run their own encoder. The same card handles ladders, packaging and the graphics work sitting next to them.
A back catalogue kept whole on one chassis rather than pulled from object storage every time somebody requests it.
Every configuration is specified per build. Cores, memory, flash, raw capacity and port speed follow the ladder, the concurrency and the size of the catalogue, and they are written into the quote before anything is ordered.
The three arrangements differ mostly in this table, which is the part worth agreeing before anyone quotes a number.
Buy: yours from delivery.
Placed: ours, sourced for the build, on a monthly figure.
Colocated: yours already.
Buy: yours to arrange.
Placed: ours, including power, cooling and transit.
Colocated: ours, including remote hands.
Yours in all three. Your media server, your packager, your ingest and your licences. We do not run the stack and we do not charge you for it.
Two different purchases that both get described as «streaming infrastructure».
You are buying machines and a place to put them. Ordered per build, in whichever of the three arrangements fits how your company buys.
You are buying delivery. You bring the stream and it reaches viewers on the shared network, billed per terabyte. See Streaming CDN.
The two sit together often: your own servers produce and originate the stream, delivery runs on the network. The rest of the build-to-order line is on Custom Enterprise CDN Infrastructure.
Tell us what the server has to run and which arrangement suits you. You get a reply within 3 business hours with a specification and a price, or an honest answer that a shared setup covers you already.
He reads every request sent from this page and replies within 3 business hours, including the reply that says a shared setup covers you already. No sales sequence in between.