· · · ·
For Productions For Engineers Modules Downloads Live demo Request a demo
All modules Module 24 · Federation & redundancy

Add a server when you need more.
Mirror it when you can’t go down.

Increase your encode, decode, replay and mixing capacity by adding another SYGNAL server. Federate them to share resources over the network, or duplicate control data to two mixers for fully redundant pipelines.

Federation & redundancy

Scale out, or mirror for hot redundancy

Increase encode, decode, replay and mixing capability by adding another SYGNAL server. Federate them to virtually link over the network and access resources between them. Duplicate control data to two mixers for fully redundant vision mixing — or any other AV pipeline.

  • Pool resources across federated servers
  • Mirror control data for hot redundancy
  • Geographically distribute your production
  • Pair in three steps, with a code you compare on both servers
  • Remote sources pulled on demand
  • Mirror groups with one leader, automatic failover and rejoin
Capacity & resilience

More than one server, one system

Capacity and resilience come from the same thing: a second server that behaves as part of the same system.

Scale

Add a server to grow encode, decode, replay and mixing capacity — then reach its resources from anywhere on the network.

Redundancy

Duplicate control data to a second mixer for fully redundant vision mixing, or any other AV pipeline that can’t go down.

Distribute

Federate servers across sites and time zones, and run one production spread over many locations.

Running a federation

Pair it, share it, keep it up

Federation is set up and watched from the same interface as everything else.

Pairing

A three-step wizard: find the server, verify the code, set the sharing defaults. Both servers show the same code, and an operator confirms they match.

Source directory

Every paired server sees one shared directory of sources, with thumbnails. A remote source is pulled on demand, so the origin only encodes what is being watched.

Mirror groups

Mirror a prompter or a vision mixer across servers. One server leads. If it drops, another takes over, and it rejoins on its own when it returns.

Conflicts

If two servers diverge during a split, the losing copy is quarantined, not discarded. Compare the two and choose: keep ours, or use theirs.

Sharing policy

Set what each peer may reach, module by module, with a default policy for new peers. Access tags scope which sources and instances a peer can see.

Devices, map & events

Enrol nodes by token from the Devices page as contributor, receiver or full. A live map and an events strip show the federation. An uplink bandwidth governor steps video down before it touches audio.


Find out more

Keep exploring the toolkit

Scale without changing systems

Book a walkthrough with the engineers who built it, or see a federated setup in the live demo.