Card offloads in the hundreds of gigabytes
Multi-camera ISO recordings and high-frame-rate capture fill drives quickly, and the venue uplink is shared with everyone else.
Broadcast & live sports
Get camera cards, highlights and masters from the venue to the network before the next event.
When the whistle goes, the content is on cards in a truck at a venue with a shared, congested uplink. Highlights, ISO feeds and archive material still have to reach editorial, post and the network tonight. RIPTON CLOUD moves those files as packages over that uplink.
Plan limits are those published on the pricing page. Benchmark figures come from RIPTON CLOUD's published EC2 test at roughly 150 ms latency and 3% packet loss. Results on your route depend on your network, endpoints and storage. RIPTON CLOUD does not claim any industry certification on this page.
Evaluated transfer path
01
Venue or OB storage
02
RIPTON Desktop in the truck
03
RIPTON node at the network
04
Editorial or MAM ingest folder
Post-event pressure
The event is over. The deadline is not.
Sports and live-event content is captured at venues with congested, high-latency connectivity and needed at facilities that may be a continent away, on a clock set by the next broadcast.
Every minute of latency is lost bandwidth
Venue-to-network routes are long. TCP transfers lose most of the link at that latency, so a 1 Gbps uplink delivers far less.
Freelancers, OB companies and rights holders
Content moves between organisations that do not share networks or accounts.
Workflows
Where the transfer path matters most.
ISO feeds · card offloads · logs
Venue to editorial
Package the card offload in the truck and send it to the network's node. Editorial sees progress and gets the folder structure intact.
Highlights · promos · graphics packages
Highlights and graphics to partners
Send finished highlight packages and graphics to rights holders and affiliates as packages with scoped links and download records.
Masters · archive · compliance copies
Masters to post and archive
Schedule finished masters to a post house or archive node so the deliverable exists where it is needed before the morning.
RIPTON CLOUD in the workflow
What a broadcast team gets
The product earns its place by moving prepared data between endpoints—not by claiming ownership of every system around it.
Designed for the venue uplink
The RIPT protocol is UDP-based with rate control and block retransmission, built for the long, lossy links between a venue and a facility.
Multi-camera folders as one package
An offload of many clips travels and is stored as a single package with its structure kept for ingest.
Delivery you can see from the gallery
Progress while it sends and a record when the facility has it, so nobody phones the truck to ask.
Encrypted on every packet
AES-256-GCM or ChaCha20-Poly1305 with a forward-secret key per session and replay protection. There is no plaintext mode to misconfigure.
No generic speed promise
Throughput depends on your route, endpoints, and storage. The published benchmark (a 1 GB file 7.5x faster than the TCP baseline at 150 ms and 3% loss) tells you where the difference appears; your own route tells you how much.
Product boundary
File delivery, not contribution.
RIPTON CLOUD moves recorded files between endpoints. It is not a live video contribution or distribution system and does not replace SRT, satellite or fibre contribution.
What it covers
- Card offloads and ISO recordings sent as packages
- Highlight and graphics delivery to partners
- Scheduled masters to post and archive
- Delivery records for every recipient
What stays with your stack
- Live video contribution or streaming
- Playout or distribution
- Media asset management
- Transcoding
Evaluation path
Test it from a real venue
Bring one event's offload and the truck's actual uplink. Measure both tools to the same facility.
- 01
Choose the event
One venue, one facility, the real uplink on the day.
- 02
Send the offload
The same card offload with both tools, elapsed time and restarts recorded.
- 03
Deliver a highlight package
To a rights holder or affiliate, confirming download without help from your team.
- 04
Decide on numbers
Minutes from final whistle to files at the facility, written down.
FAQ
Questions technical buyers ask.
Is this live contribution?
No. RIPTON CLOUD moves recorded files. Live video contribution stays on SRT, satellite or fibre. Use this for everything that is a file after the event.
Can OB companies and freelancers send without accounts?
Yes. A Shared Inbox or public upload link lets them send from a browser with no named seat and no charge on your side.
What about very large single files?
No file-size limit from Professional up; 10 GB per file on Free and 100 GB on Starter.
Will it be faster than our current tool from the venue?
That depends on the uplink and the route. The published benchmark shows the difference appears with latency and loss, which venue links have. Measure it on one event.
Technical evaluation
Files at the facility before the pundits finish.
Start a free workspace, or bring one event's route and we will help you measure it.