--- title: Comparing Broadcaster and ZEC slug: zixi-broadcaster-zec-current-version/comparing-broadcaster-and-zec docTags: createdAt: 2025-11-18T15:56:42.739Z --- ## Introduction Zixi Broadcaster and Zixi Edge Compute (ZEC) provide some similar funtionality, but there are also some significant differences which mean that they serve different purposes and should occupy different places in your workflow. The tables below explains the key differences and appropriate uses for each. ### Basic Feature Differences | **Feature** | **Broadcaster** | **ZEC** | | ---------------------------- | --------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Primary Role** | Core media gateway for large-scale routing and processing | Lightweight edge contribution and routing | | **Stream Processing** | Transcoding, remuxing, multiplexing, PID mapping | No transcoding, remuxing or multiplexing. PID mapping is supported on Zixi pull inputs and on streams sent to a Broadcaster by Zixi push. | | **Ad Signaling** | SCTE-35 insertion, ESAM/POIS integration | SCTE-35 insertion (you supply the payload). No ESAM/POIS integration. | | **Protocol Support** | Any-to-any conversion (Zixi, RTP, RIST, SRT, HLS, etc.) | Zixi protocol, basic RTP/SRT | | **OTT Packaging** | HLS, LL-DASH, CMAF adaptive bitrate packaging | HLS and DASH (including CMAF) packaging of streams received over Zixi pull. A ZEC cannot transcode, so it cannot create extra bitrates; build adaptive bitrate ladders on a Broadcaster. | | **Scale and Redundancy** | High-density routing, active/active failover | Single-node edge deployment | | **Analytics and Monitoring** | TR-101-290 analyzer, SCTE-35 reporting, AgentZ telemetry | Basic health monitoring | | **Workflow Automation** | Event switching, scheduling, time-shifted delivery | Limited automation | ### Details of ZEC Limitations **(that Broadcaster does not have)** | Feature Area | Limitations | | ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Hardware / Location** | - Can’t scale to data center or cloud-level workloads - Not suitable for multi-tenant routing or global distribution. | | **Networking and Transport** | * Can’t perform complex stream routing between multiple endpoints or regions * Doesn’t support advanced SMPTE 2022-7 hitless redundancy across data centers. | | **Stream Processing / Conditioning** | Can’t perform heavy stream conditioning such as:
* Transcoding * Remuxing * Multiplexing
PID mapping and SCTE-35 insertion are available, within the ZEC rule that every output is either a Zixi push to a Broadcaster or is fed directly by a Zixi pull. | | **Scale and Throughput** | - Can’t handle hundreds or **thousands** of concurrent streams - Therefore limited throughput | | **Failover and Redundancy** | Can’t participate in complex global hardware redundancy & orchestration | | **Protocol Handling** | Can’t perform any-to-any protocol translation beyond Zixi-to/from a small set (e.g., RTMP, SRT, UDP) | | **Deployment and Management** | Not designed to operate as a standalone routing node. It requires a Broadcaster or ZEN Master to manage topology. | | **Analytics and Control** | Reports basic link and health metrics but doesn’t provide deep insight, analytics, or multi-hop visibility | | **Interoperability** | Can’t integrate with multiple partner networks, CDN targets, or conditional access workflows | | **Licensing / Operations** | Doesn’t include Broadcaster-level control features or automation (event switching, scheduling, ESAM/ESNI) | | | | | | | ### Where and When to Use ZEC and Broadcaster | **Aspect** | **ZEC** | **Broadcaster** | | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | Primary deployment location | At the network edge / on-premises near the source or local network | Central node (on-premises, cloud, or hybrid) for large scale processing and distribution | | Primary role | Ingest/contribute or receive/distribute video streams; interface local protocols; optimize transport to/from central | Ingest streams (from edge or elsewhere), perform transcoding/packaging/recording/transmuxing, output to many formats and destinations | | Protocol focus | Convert local protocols (HLS/RTMP/RTSP etc) and then use optimized Zixi protocol to connect upward; or use Zixi protocol to receive and then output local protocol | Broad protocol support (14+ protocols) for ingest & egress, format conversion, multiple bitrates, etc. | | Processing / transformation | Some local manipulation (e.g. bonding/link fail-over, encryption/decryption, PID mapping, SCTE-35 insertion) but more focused on transport/edge | Full processing: transcoding, transmuxing, packaging, recording, time shifting, large scale distribution | | Cost/egress optimization | When using ZEC you can reduce transport/egress costs (e.g., 50% reduction claim) because of efficient Zixi protocol at edge | Less about “edge cost” and more about handling many outputs, large scale, reliability, resiliency | | Scalability and central features | Edge-scale: multiple ZEC nodes in various locations, each handling local contributions / distributions | Central scale: clusters, load-balancing, many destinations, global distribution | | Typical use-case | Local site or remote contribution: e.g., remote camera, OB van, remote facility using ZEC to send feeds to central.
Also local distribution point receiving feeds and distributing locally | Broadcaster workflows: receiving many input feeds, normalizing, transcoding and sending to CDNs, OTT, global endpoints; managing large event distribution |