Cloud Craft SRLCloud · DevOps · SRE · Infrastructure

Broadcast and IPTV · MPEG-TS control plane

Keep channels flowing, correctly mapped and fully observable.

NoSignal is a production Linux application for ingesting, switching, conditioning and delivering MPEG-TS streams. It brings failover, packet-level correctness, HLS, EPG and operator visibility into one deterministic service.

RustMPEG-TSUDP multicastSRTHLSPrometheus
Production deployedUsed by broadcast and IPTV operators in the EU
Four input familiesUDP, SRT, HTTP TS and HLS
Standards firstDVB and MPEG-TS correctness in the packet path
One Linux serviceEngine, API, UI, telemetry and HLS origin

The operator problem

Live transport fails in more ways than “up” and “down.”

Inputs freeze, continuity breaks, backups drift, service identifiers collide, multicast paths disappear and receivers reject streams that are almost—but not actually—compliant.

  • Failover must be fast without flapping between unstable inputs
  • Packet conditioning cannot become a CPU tax on passthrough channels
  • Operators need live state, history and safe changes without daemon restarts

The engineering response

Packet correctness inside an operator-first control plane.

NoSignal isolates channels, branches above unused processing, keeps packet work synchronous and bounded, and moves configuration changes through the web UI and API without restarting unrelated channels.

  • Per-channel runtime and output isolation
  • Conditioning runs only when the channel enables it
  • Metrics, alerts, SSE updates and runbook-friendly state are built in

Capabilities

From wire ingest to viewer delivery.

NoSignal covers the complete transport workflow while keeping protocol correctness, steady-state CPU use and operational clarity visible in the design.

01 · INGEST

Multiple transport inputs

UDP multicast, SRT, HTTP transport stream and HLS inputs, with interface-aware binding and health signals.

02 · FAILOVER

Controlled source switching

Priority inputs, warm standby, watchdogs, anti-flap behavior and auto-revert keep output stable through source failure.

03 · CONDITIONING

DVB-correct packet work

PID filtering and remap, PSI rewrite, continuity correction, service identity and optional CBR pacing.

04 · OUTPUT

Parallel delivery

UDP multicast, SRT, HTTP TS and built-in HLS outputs consume independently so one slow path cannot block another.

05 · EPG

XMLTV and EIT workflows

EPG import, mapping, service-aware injection and tools for resolving identifier collisions across channel lineups.

06 · OPERATIONS

Telemetry everywhere

Web console, REST API, SSE state, Prometheus metrics, alerts, live preview and companion iOS visibility.

System shape

Async at the edges. Deterministic in the packet path.

Inputs and connection-oriented outputs use asynchronous I/O. The transform pipeline stays synchronous and allocation-light, while each channel remains an isolated runtime unit.

Transport inputsUDP · SRT · HTTP TS · HLS
Channel runtimeHealth, failover, packet pipeline
Output fan-outUDP · SRT · HTTP TS · HLS
OperationsWeb, API, SSE, Prometheus, iOS

What this proves

We build software where protocol details become operational outcomes.

NoSignal combines broadcast engineering, performance-sensitive Rust, Linux operations, a polished control surface and production deployment across real channel loads.

Broadcast engineeringMPEG-TS, DVB, multicast, SRT, HLS, EPG and receiver interoperability.
Performance architectureMinimal per-channel work, isolated tasks and predictable packet processing.
Product operationsInstaller, API, UI, licensing, telemetry, support tooling and release discipline.

More projects

Other critical systems we operate.

Explore our route-server control plane, public Looking Glass and safe DDoS automation platform.

Broadcast systems that stay understandable

Working on IPTV, streaming or media infrastructure?

We can help with transport architecture, failover, MPEG-TS conditioning, observability, Linux deployment and custom operator software.