BeStream Edge
Reliable Contribution Transport Protocol

Secure contribution transportfor unstable IP environments

BeStream Edge is a contribution transport protocol built for moving live video between field encoders, control rooms, studios and monitoring points over public or private IP networks. It combines authenticated encryption, adaptive packet recovery and operational monitoring in a sender/receiver workflow designed for real broadcast use.

ChaCha20-Poly1305Authenticated encryption with low software overhead
Adaptive FEC + ARQRecovery tuned per link, bitrate and latency target
On-Prem ControlNo cloud dependency, no forced third-party transport layer
Why engineering teams choose it
A protocol-first approach for reliable live video transport
BeStream Edge focuses on contribution-grade delivery over IP with encrypted packet transport, configurable recovery behaviour and clean sender/receiver operation on Windows or Linux. It is designed for broadcast and operational workflows where packet loss, jitter and route instability must be managed without losing the signal.
๐Ÿ”
Authenticated packet transportChaCha20-Poly1305 protects the transport path packet by packet while keeping software overhead practical on general-purpose systems.
๐Ÿ“ก
Adaptive FEC + ARQ recoveryForward error correction and retransmission work together to improve contribution continuity on unstable or lossy links.
๐Ÿงฉ
Broadcast workflow fitUDP input, UDP or RTMP output, browser-based control and contribution-friendly deployment with no forced transcoding path.
Field Encoder
Control Room
Studio Ingest
Monitoring Point
Protocol overview

One protocol layer. Encrypted transport, resilient delivery, operational control.

BeStream Edge runs as a lightweight sender/receiver service on Windows or Linux. Fully controlled by your team and deployable on private infrastructure.

Secure Transport

Move live contribution feeds across public, private or restricted IP paths with authenticated protection on each transport packet.

  • Authenticated encryption on every packet
  • Replay and tamper resistance at the transport layer
  • Suitable for public internet, VPN and private routing

Resilient Delivery

Adaptive FEC and ARQ recovery help sustain contribution feeds on lossy, jittery or operationally difficult links.

  • FEC for immediate recovery without always waiting for retransmission
  • ARQ support for burst-loss conditions
  • Configurable bitrate, latency and recovery profile

Operational Fit

Designed for real broadcast contribution workflows with deployable sender/receiver nodes and browser-based control.

  • Browser UI for channel and key management
  • Windows service or Linux daemon operation
  • Live bitrate, RTT, FEC and recovery visibility
Signal flow

Contribution transport in four stages

Any encoder or media source sends UDP into BeStream Edge. The TX applies transport protection and recovery settings, sends across the network, and the RX reconstructs and outputs the signal for local use.

Input: UDP from encoder or media gateway. Codec-agnostic contribution workflow.
Transport: BeStream Edge protocol with authenticated encryption, FEC, ARQ and adaptive transport behaviour over UDP.
Output: Clean UDP or RTMP for local media systems, monitoring or onward distribution.
Management: Browser-based channel setup, transport keys and live protocol telemetry.
Deployment path
1

Deploy sender and receiver

Run the same protocol stack on both ends as a lightweight Windows or Linux service.

2

Connect the source

Feed UDP from your encoder or upstream media device into the sender node.

3

Set transport profile

Choose encryption, recovery, bitrate and latency values based on the target network path.

4

Deliver at the far end

The receiver reconstructs the stream and outputs it to local broadcast or monitoring infrastructure.

Use cases

Built for contribution workflows that cannot rely on a perfect network

From broadcaster field contribution to difficult fixed-location paths, BeStream Edge is intended for situations where operational continuity matters more than ideal network conditions.

๐ŸŽฅ

Field Contribution

Reporter kits, mobile encoders, temporary uplinks
  • Transport contribution feeds from the field to master control or ingest
  • Handle lossy or unstable IP paths more gracefully than plain UDP delivery
  • Keep deployment simple on standard hardware
๐Ÿ›ฐ๏ธ

Satellite & Difficult Links

Operational paths with latency, loss or route instability
  • Support contribution delivery where retransmission alone is not enough
  • Use configurable recovery profiles per path
  • Keep transport fully under operator control
๐Ÿข

Studio-to-Studio Transport

Private network, VPN or internet-based contribution
  • Move live feeds between facilities over managed or unmanaged IP paths
  • Preserve workflow flexibility with UDP and RTMP outputs
  • Avoid dependence on external cloud relay layers
๐Ÿ–ฅ๏ธ

Monitoring & Return Paths

Control rooms, remote monitoring and operational visibility
  • Deliver contribution feeds to monitoring and decision points
  • Observe bitrate, RTT and packet recovery behaviour in real time
  • Adjust transport settings to suit changing network conditions
Transport behaviour

Recovery and continuity at the protocol layer

BeStream Edge is designed to improve contribution continuity by combining encrypted transport with adaptive recovery techniques. The aim is operational stability, controlled latency and better tolerance to packet loss on imperfect IP paths.

Adaptive
Recovery
FEC and ARQ combined per path
Configurable
Latency
Set to match the operational link
On-Prem
Control
No cloud relay dependency
Example โ€” protected transport path
1
2
3
4
5
6
R
8
9
10
Normal transport packet Loss event Recovered packet

Protocol behaviour that matches contribution requirements

Instead of relying on a single recovery method, BeStream Edge combines authenticated encryption, parity-based forward recovery and retransmission logic in one transport path. This gives operators more control over how bitrate, latency and resilience are balanced per link.

What operators can tune

Latency
High
Recovery
Strong
Control
Full
Packet recovery

Contribution transport that keeps the signal moving

BeStream Edge monitors packet loss and uses recovery mechanisms before damaged transport conditions turn into visible operational disruption downstream.

Example โ€” packet loss handled at the transport layer
Video
Video
Video
โœ• Lost
Video
Video
Video
Video
Video
Video
Recovery data travels alongside contribution traffic
โœ“ Receiver reconstructs the missing packet and the feed continues
Recovery data travels alongside contribution traffic. When loss conditions allow it, the receiver reconstructs missing packets without waiting for a full retransmission cycle. When needed, ARQ adds another recovery path for burst-loss events.
Profile
Recovery
Latency
Use Case
Low Loss
Adaptive FEC
Lower
Stable contribution paths with occasional packet loss
Mixed Loss
FEC + ARQ
Balanced
General internet or mixed operational routing
Burst Loss
Higher parity + ARQ
Higher
Difficult contribution paths where continuity matters most
Works quietly on difficult links
Recovery capacity can be tuned to match expected network conditions, from stable managed paths to more volatile public internet contribution routes.
Two recovery paths
If a packet is recoverable through parity, the receiver restores it immediately. If loss conditions exceed that layer, retransmission provides another recovery chance.
Operator control
Latency and recovery are not fixed assumptions. Operators can tune them to the path, bitrate and operational priority of the feed.
Protocol stack

A transport stack designed for live contribution

The protocol combines encryption, recovery and packet delivery behaviour in one transport layer so operators can control resilience without adding unnecessary workflow complexity.

BeStream Edge layers
Source
UDP contribution input from encoder or media gateway
Recovery
Adaptive FEC parity for immediate recovery when conditions allow
ARQ
Retransmission path for burst-loss and non-recoverable parity events
Crypto
ChaCha20-Poly1305 authenticated encryption on transport packets
Control
Operational transport logic with bitrate, RTT and recovery visibility
Network
UDP-based contribution transport across private or public IP paths
Role
Contribution transport protocol for sender/receiver workflows
Encryption
ChaCha20-Poly1305 authenticated packet protection
Recovery
Adaptive FEC and ARQ working together on lossy paths
Input
UDP contribution input from encoders and media gateways
Output
UDP or RTMP output for downstream systems
Deployment
Windows service or Linux daemon on customer-controlled infrastructure

Operational compatibility

Built to fit into contribution workflows without forcing a complete workflow redesign.

Workflow Role
Contribution transport between source and destination nodes
Input Side
UDP from encoder, gateway or media processing system
Output Side
UDP or RTMP for monitoring, ingest or onward delivery
Control
Browser-based operational interface
Deployment Model
On-premises sender/receiver nodes

Protocol tags

Common positioning terms for engineers, operators and integrators.

Contribution Transport Protocol Layer Recovery On-Prem Deployment UDP Input UDP / RTMP Output Adaptive FEC + ARQ
Private evaluation

Assess the protocol in your own contribution workflow

BeStream Edge is intended for teams that need more control over encrypted contribution transport, packet recovery behaviour and deployment model. Share your workflow and we will map an appropriate sender/receiver profile for your environment.

Contribution workflow briefing

Tell us about your transport requirement

Share the path, bitrate, operational environment and output requirement. We will review the workflow and suggest a sender/receiver transport profile.

We respond within one business day.

How to brief us

A short technical outline is enough for an initial review.

1
Source and codecTell us what produces the feed and what kind of contribution output you have.
2
Network pathShare whether it is internet, VPN, private routing or a more difficult field path.
3
Bitrate and latencyTell us the expected feed bitrate and the operational latency target.
๐Ÿ“จ
Technical Briefing Share your contribution workflow and transport target. sales@bestream.io
๐Ÿ”
Private Evaluation Protocol review for customer-controlled deployments and difficult links. sales@bestream.io
Workflow details can be reviewed privately for customer or operational environments.