Skip to content

Functional characteristics

Use this capability map to find the relevant configuration guide. The linked manual pages describe settings, prerequisites and operational limits.

Catena has two layers, and they are licensed separately: you can take the delivery engine alone and add the subscriber service when you need it.

  • The delivery engine takes streams in, processes them, records the archive and serves viewers. If you already run a portal or middleware, this is the layer you connect to it.
  • The subscriber service turns those streams into a product: portals, packages, the guide, subscribers, and the apps they watch on.

Using this reference

Choose a section below, then follow the corresponding page of the manual for configuration.


The delivery engine

Ingest

Capability What it is
Sources over RTMP, RTSP, MPEG-TS (UDP and HTTP), HLS, M4F The usual ways a stream arrives from a headend or a partner
MPEG-DASH source capture Pull a stream by a DASH manifest: one representation or the whole ladder, a protected source via ClearKey keys — more
Input video codecs: H.264, HEVC, AV1, MPEG-2 Video Accepted and decoded, MPEG-2 from broadcast and satellite trunks included
Multicast ingest Take SPTS straight off the operator network
SRT ingest Take a feed over a lossy link, with a passphrase
Publishing point The far side pushes into Catena instead of being pulled
Synthetic source Built-in generator to prove the path before a real feed exists
Backup sources with priority An ordered list; the stream moves to the next one when a source dies
Backup file A clip goes to air when every source is down
Source quality thresholds Timeouts, bitrate floor and ceiling, MPEG-TS continuity errors
Source state with a reason Working, degraded or dead — and why, per source
MPTS ingest with program selection Take one multiplex and pick the programs out of it; a single capture of the trunk feeds every stream taken from it

Processing

Capability What it is
Transcoding to H.264, HEVC and AV1 Bring any source to what viewers' devices actually decode
ABR ladder Several renditions per stream: resolution, bitrate, GOP, resize strategy per rung
Track selection by id or by language How each input is turned into an output
Per-track audio encoding Different codec and bitrate per audio track
Thumbnails Frames for seek previews and stream tiles, from keyframes or over HTTP
Closed captions CEA-608/708 to WebVTT A broadcast channel's captions reach browsers and apps as a separate track
Teletext subtitles to WebVTT Decode subtitle pages into separate tracks for browser and OTT players — configuration.
Hardware transcoding on NVIDIA (NVENC) Decode, scale and encode on the card; the card is picked explicitly or automatically
Deinterlace Interlaced broadcast feeds to progressive for OTT devices
Logo overlay A station bug over the picture: the image is burned into the video track of a rung — more

Archive, catch-up and timeshift

Capability What it is
Archive recording Record a stream with a depth and size limit
Archive across several disks Several mount points per streamer, with mount checking and disk state
Archive playback by time range Play any past interval by its UTC boundaries
Startover and pause live Jump to the beginning of what is on now, and pause a live stream
Relative and absolute timeshift Play a fixed number of seconds behind live, or from a wall-clock moment
SSD cache for hot archive Prime-time catch-up served off SSD without paying for an all-SSD archive

Delivery

Capability What it is
HLS and LL-HLS The default way viewers watch, and its low-latency variant
DASH The second manifest format, for devices that prefer it
MPEG-TS and fMP4 output Plain transport for STBs and for other servers
Built-in player Watch a stream from the console without setting up anything
CDN zones Viewers are routed by their IP to the streamers of their zone
Device profiles A class of devices gets only the tracks it can play: by User-Agent, header or URL parameter — more
Load balancer The player asks one address and is sent to the streamer that carries the stream
Multicast output Serve your own subscribers on a managed network by pushing streams into multicast groups

Access and protection

Capability What it is
Operator login and API keys Credentials for the console and bearer keys for the management API
Join tokens and streamer keys How a machine is admitted to the cluster and how it authenticates afterwards
Playback authorization backends Catena asks your service whether playback is allowed — configuration.
Signed playback links A hashed link with an expiry and an optional IP binding, checked without calling anyone
Concurrent session limit Cap the streams one subscriber may run, and catch shared passwords
DRM: Widevine, PlayReady, FairPlay Studio-grade protection with keys from your DRM vendor over CPIX — delivery encryption
DRM over archive and rewind The same key on catch-up: the archive is encrypted on the way out, like the live edge — more

Cluster and resilience

Capability What it is
Streamer registry Every machine, its state and its telemetry in one screen
Joining a streamer A time-boxed window and a token instead of editing files
Automatic stream placement Central decides which streamer runs which stream
Placement history and reasons Why a stream is where it is, and what moved it
Placement requirements Labels and namespaces decide which machines a stream may run on
Edge streamers Machines dedicated to delivery: viewer load moves off the capture machines
Archive cache on an edge Archive parts that were read settle locally, repeat requests do not reach the source
Archive backup copies The archive is recorded not only on the capture machine but on a set number of neighbours
Serving archive leftovers After a stream moves, what was recorded keeps being served from the former machine
Archive cleanup Archive a streamer cannot serve is erased by the retention depth instead of piling up
Archive orphans A streamer finds the archive of a deleted stream itself, central assigns cleanup to it, the space is free within a day
Stream slice on the streamer page What exactly was delivered to the machine: roles, configs, delivery
Recovery from a streamer loss Streams of a dead machine are re-planned onto the survivors
Configuration delivery Central holds the settings and tracks desired, synced and applied per streamer
Stream limit per streamer Cap how much one machine takes; zero keeps it in the cluster but empty
Database backup and restore A supported procedure instead of a hand-written pg_dump

Observability and operation

Capability What it is
Dashboard The whole installation on one screen: machines, streams, traffic, errors
Streamer telemetry CPU, network, running streams, archive capacity, uptime, last contact
Merged stream status One value across every streamer that takes part in handling the stream, and a banner with the reason for intervention on its page
Live viewer sessions Who is watching what, from which streamer, with filters and a force-close
Session history Closed sessions with duration, bytes and the reason they ended
Built-in metrics server Prometheus-compatible queries and a Grafana data source, without extra parts
Structured logs and traces Machine-readable logs and OpenTelemetry traces for tracking a request
Retroview Vendor cloud monitoring with long history and curated alerts

The subscriber service

This layer is what turns a stream into a television product. Take it if you have no operator TV system; skip it and connect your own portal over the API if you already have one.

Streams, packages and the guide

Capability What it is
Stream templates Settings written once and applied to hundreds of streams
Stream catalogue Title, logo and guide binding on top of the technical stream
Packages Named bundles of streams — the thing a subscriber actually buys
Free packages Streams every subscriber gets without a subscription
Guide from XMLTV Import the schedule from your provider, refreshed automatically
Guide import diagnostics What was fetched, what changed, what failed and when
Programme API Query the schedule for apps and integrations

Subscribers and subscriptions

Capability What it is
Subscriber accounts The person who watches, and what they are entitled to
Playback token per subscriber What the streamer checks before letting a session play
Subscriptions to packages Access granted and revoked immediately
Blocking a subscriber Cut access without losing the account and its history

Viewer applications

Capability What it is
Web player for viewers Watching without installing anything
Stream list with now and next What is on, and what is on after it

Analytics and audit

Capability What it is
Viewing sessions The live and historical record of who watched what
Operations audit log Who changed what, and when — including subscription changes

Operator staff and permissions

Capability What it is
Operator credentials One login pair and API keys for the whole installation

Integration

Capability What it is
Management API Everything the console does, available to your systems
Connecting a third-party portal Keep the portal you have and drive Catena over the API
OpenAPI schema The management API has a machine-readable OpenAPI schema.

What Catena does not do

These are deliberately outside the product. Naming them saves a discovery call:

  • Cameras, surveillance, exporting recordings and proxied viewing — connecting cameras (including reaching ones with no public address through an agent), cutting a piece of the archive out into an MP4 file, and proxying playback through the control server are Watcher.
  • WebRTC and NDI — publishing over WHIP, playback over WHEP, NDI ingest and the products built around them are Agora.
  • Baseband, sending streams onward and the DVB transport multiplex — SDI, ASI and ST-2110 ingest, pushing streams out to third parties over RTMP, SRT or MPEG-TS, and building an MPTS with SI/NIT/SDT tables and logical stream numbers are Mcaster. Catena keeps the two directions it needs for its own service: taking a feed in over SRT, and pushing out to multicast for its own subscribers.
  • Conditional access for broadcast — CAS and scrambling for cable and satellite estates. On a managed network, isolation and DRM cover the same ground differently.
  • Billing and tariffs — Catena knows who is entitled to what, never what it costs. Prices, invoices and payments live in your billing system, which drives Catena over the API.