Livelink features
Everything between the source and the viewer.
Follow one live feed through Livelink: in from the source, checked, protected, shaped, packaged and delivered to every taker. Each step is one click, and every step is watched.
11 atoms · jump to one
Illustration: the Livelink diamond assembles from its two bands, then breaks apart into one block for each feature on this page.
01·Contribution
Bring it in from anywhere.
A stadium encoder, a bonded 4G pack, a teleport, a partner's playout: if it speaks IP, Livelink can take it.
Any protocol in
SRT, Zixi, RIST and RTMP, and more, as caller or listener, push or pull.
Connected in minutes
Create a source, hand the details to the venue and watch it connect.
Every input watched
A live picture, a status and the numbers that matter, the moment it connects.
MSTVLivelinkZixi in over bonded 4G from Antalya, SRT out to the broadcaster.Read the case study →
Illustration: small venue blocks connect to a source block over SRT, Zixi, RIST and RTMP. The source block opens and a picture tile rises, its status changing from Connecting to Connected.
02·Live health
Know it's healthy before anyone asks.
Bitrate, packet rate, jitter, round-trip time, latency and loss, live and historical, for every source and every destination.
Live and historical
Watch it now or go back to the minute something changed.
Stream analysis
Continuous transport-stream checks catch sync loss, continuity and table errors before viewers do.
Alerts that reach you
Choose what matters and hear about it by email or Slack. Mute what doesn't.
Illustration: live stat tiles for bitrate, jitter, round-trip time, latency and loss stand on a block like a tiny dashboard, beside a live bitrate line, a stream-analysis checklist turning green and an alert sent by email and Slack.
03·Resilience
When one path drops, the other carries on.
Run main and backup on separate paths, and group them for automatic failover.
Main and backup
Separate routes, separate paths, one output.
Automatic failover
Set the thresholds once; Livelink switches when the main falls below them.
Disaster recovery
Add a third path for the channels that must never go dark.
Illustration: main and backup source blocks feed one output. The main block cracks and drops below its threshold; the backup lifts into the main position while the output picture keeps running.
04·Live production
Produce the show in the cloud.
Livelink Studio is a complete production and master control room that you launch when the show needs it, then shut down when it ends.
Switching, audio and graphics
Frame-accurate cuts, mixes and wipes, a full audio desk and downstream keying, all in the browser.
Build once, launch any time
Configure a production from templates, launch it for the event and relaunch it for the next one.
A backup that mirrors everything
A second engine in another cloud region follows every press, ready for one-press failover.
Illustration: camera and source blocks feed a studio block that opens into a small vision mixer, with a red-tallied programme monitor, a green-tallied preview and source buttons. Every few seconds preview is taken to air, and a mirrored backup block in another region follows each take.
05·Processing
Shape it for every screen.
Transcode in the cloud, only while you need it. One feed becomes the exact versions each taker asked for.
Transcoding and ABR ladders
From a single contribution feed to a full adaptive ladder.
Audio, captions and branding
Map audio tracks, carry captions and timecode, and add a logo overlay.
Multiviewers
Put every feed on one wall for your operators, with layouts you design.
Illustration: a transcode block extrudes a staircase of renditions for an adaptive ladder, while captions, audio tracks and a logo overlay switch on across a small multiviewer wall.
06·OTT
Package it for streaming.
HLS and DASH packaging for your CDN, your origin or your partners, with protection built in when the content needs it.
Push or pull
Push to the platforms you use, or let partners pull from you.
Protection built in
Encryption for the content that needs it, configured with presets.
Social and third parties
Deliver straight to social and partner platforms, with no round trip through HQ.
Illustration: a packager block pushes out segment cubes that stack into HLS and DASH columns, marked with a lock for protection, then travel on to a CDN, social platforms and a partner.
07·Distribution
One feed. Every taker.
Deliver to broadcasters, betting partners, OTT platforms and fixed infrastructure. Each taker gets the protocol and format they asked for.
One to many
Add a taker without touching the others.
Rights and permissions
Decide exactly which partner organisations can take which feed, and change it in seconds.
Any protocol out
SRT, Zixi, RIST, RTMP, HLS and DASH, mixed and matched per taker.
QTVLivelink142 matches, from zero to six simultaneous deliveries.Read the case study →
Illustration: destination blocks snap in one by one around a single source, each with its own protocol, while a partner access toggle switches one taker off and on again.
08·Scheduling
Right on time, every time.
Book deliveries on a timeline and let Livelink start and stop them. Run a one-off event, a season, or around the clock.
A timeline you can read
Zoom from the next hour out to the whole week.
Starts and stops itself
No one waiting up to press go, and nothing left running afterwards.
Overruns handled
Extend or move a booking as the day changes.
QTVLivelinkLast-minute changes to requirements and rights, handled on the fly.Read the case study →
Illustration: bookings on a timeline track assemble into blocks as the red now line reaches them and dissolve when they end, then the view zooms out from the day to the whole week.
09·Monitoring
See the whole picture.
Build live monitoring boards from your own sources, destinations and environments, and share them with the people who need them.
InSight boards
Drag your workflow onto a canvas and watch it run, live.
Share a live view
Send a link to a partner or a gallery screen. No login needed.
On your phone
Check status, stats and schedules from anywhere.
Illustration: the workflow is seen from above as a monitoring board of source, environment and destination nodes with clocks and gauges, shared by link and shown on a phone.
10·Infrastructure
Run it on any cloud, near any venue.
Put each environment in the cloud and region that suits the job. Run them side by side, and start and stop them when you need to.
Multi-cloud
AWS, Google Cloud, DigitalOcean and Akamai, and your own cloud account if you prefer.
Close to the action
Choose regions near your venues and your takers.
Edge devices
Reach and control venue hardware remotely, securely, from the same place.
Illustration: separate islands for AWS, Google Cloud, DigitalOcean and Akamai, each holding environments with CPU and memory gauges, and an edge device block linking in from a venue.
11·Usage and billing
Know what it costs while it's running.
Usage is tracked for every environment and every service, whether it runs for an hour or a year. No surprises at month end.
Pay for what runs
Start it, use it, stop it. When nothing's running, nothing's billing.
Daily and monthly views
See today's spend as it happens, and the month at a glance.
Every stream accounted for
Break usage down by environment, service and cloud.
Illustration: a small workflow lights up and an amber usage meter rises only while it runs; when the workflow is torn down the meter drops to zero and the day’s bars stop growing.
Two ways to use it
Drive it yourself, or let us run it.
Self service
The same control plane our engineers use, with a clean UI and an API for everything in it.
Managed service
Our team runs your workflows around the clock, with SLAs and experts who do this every day.
- hello@cerberus.tech
- Phone
- +44 2393 032017
- Office
- Steel House, Solent Business Park, Fareham, Hampshire, PO15 7FP
Illustration: the Livelink diamond splits into its blue and teal bands, one for each way to use it.