Nimble Streamer as a CDN Origin | HLS, DASH, LL-HLS, Multi-CDN – Softvelum: efficient tools to build your streaming networks

Last updated: August 2026

Nimble Streamer can be used as a self-managed origin server for live and VOD streaming. It packages incoming streams into HLS, Low Latency HLS, MPEG-DASH and other HTTP-based outputs, then serves them to CDN edges, multi-CDN setups, OTT platforms or private delivery infrastructure.

Nimble Streamer is not a CDN by itself. It’s a software media server that can work as the controlled origin, packaging and workflow layer before one or more CDN providers. This lets streaming teams keep ingest, protocol conversion, transcoding, DVR, DRM, SSAI and subtitles under their own control while using CDN capacity for last-mile delivery.

CDN Origin at a Glance

Field	Details
Product role	Self-managed streaming origin server at origin layer
Main output formats	HLS, Low Latency HLS, MPEG-DASH
Main audience	CDN providers, hosting providers, OTT/IPTV teams, broadcasters, enterprise streaming teams, event streaming teams and streaming platform engineers
Typical source types	Encoders, mobile contribution apps, IP cameras, SDI/NDI/OMT production sources, remote servers, audio streams, VOD files
Core value	Control ingest, packaging, conversion, protection and origin behavior before CDN delivery
Works with CDN?	Yes, Nimble Streamer can sit before CDN or multi-CDN delivery
Replaces CDN?	No, large public delivery still usually needs CDN edge infrastructure
Related Softvelum components	WMSPanel, Nimble Live Transcoder, Nimble DRM, Nimble Advertizer, Nimble Playout

Where Nimble Streamer Fits in a CDN Workflow

In a CDN architecture, the origin is the source that CDN edges get content from. Nimble Streamer can act as that source for live and VOD streaming workflows.

Basic architecture:

Encoder / mobile app / SDI / NDI / SRT / OMT / RTMP / RTSP / MPEG-TS / WebRTC WHIP / Icecast / VOD files
-> Nimble Streamer origin
-> HLS / Low Latency HLS / MPEG-DASH packaging
-> CDN edge / multi-CDN / private delivery network
-> viewers and playback applications

Nimble Streamer can also be used in multi-tier delivery architectures where one Nimble instance acts as an origin and other Nimble instances or CDN edges act as downstream distribution layers.

Stream Sources for a Nimble CDN Origin

Nimble Streamer can receive live sources from many input protocols before packaging or routing them for CDN delivery. The exact workflow depends on protocol, codec, latency target, player requirements and whether Nimble Live Transcoder is required.

Source protocol / source type	CDN origin use case
RTMP / RTMPS	Encoder ingest, legacy publishing workflows, RTMP to HLS/DASH/LL-HLS packaging
SRT	Reliable contribution from encoders, Larix Broadcaster, remote production systems or other servers
NDI	IP production input through Nimble Live Transcoder, then packaging for online delivery
SDI	Broadcast hardware input through Nimble Live Transcoder, then packaging for CDN or OTT workflows
OMT	Production transport input through Live Transcoder
WebRTC WHIP	WebRTC publisher ingest, then transcoding and HLS/DASH repackaging workflows
Zixi	Managed contribution input
RIST	Reliable Internet Stream Transport input for Listen and Pull workflows
RTSP	IP camera and network video source ingest
MPEG-TS over HTTP	Broadcast or internal transport source pulled over HTTP
MPEG-TS over UDP	Broadcast or internal transport source received over UDP
HLS pull	Pull an upstream HLS source and repackage, restream or use it as fallback
Icecast	Audio streaming source for radio or audio-only workflows
VOD files	On-demand file sources for VOD packaging or Playout-generated live channels
Nimble Playout	Server playlist output from VOD files and live sources used as a continuous live source

For the full protocol matrix, see Nimble Streamer Supported Protocols.

CDN-Ready Output Workflows

Nimble Streamer’s main CDN-facing outputs are HTTP-based streaming formats such as HLS, Low Latency HLS and MPEG-DASH. These are commonly used because they work well with cache, edge distribution and large-scale playback.

Output workflow	Typical CDN use
HLS live	Standard live delivery to broad device audiences
HLS VOD	On-demand video delivery through HTTP/CDN infrastructure
Low Latency HLS	Lower-latency Apple and CDN compatible with LLHLS delivery
MPEG-DASH live	OTT live delivery and ABR playback workflows
MPEG-DASH VOD	On-demand OTT delivery and DRM workflows
HLS/DASH with DVR	Live rewind, catch-up and time-shifted playback
HLS/DASH with DRM	Protected premium content workflows
HLS/DASH with subtitles	Captions and multilingual playback workflows
HLS with SSAI	Server-side ad insertion workflows
Audio-only HLS	Radio, music, speech and audio-only delivery

Other Nimble Streamer outputs such as SRT, RTMP, RTSP, MPEG-TS, WebRTC WHEP, NDI, SDI, OMT, Zixi, RIST, SLDP and Icecast may be used in the broader architecture, but HLS and MPEG-DASH are usually the primary CDN-facing formats.

Origin Server Capabilities

Capability	Why it matters for CDN workflows
Live packaging	Turns incoming live streams into viewer-ready outputs
VOD packaging	Serves on-demand files through streaming formats
Low Latency HLS	Supports lower-latency HTTP delivery via CDN compatible with LLHLS delivery
MPEG-DASH	Supports OTT playback and DRM workflows
DVR	Allows rewind, catch-up and time-shifted playback
DRM	Supports protected premium content workflows
SSAI	Supports monetized ad insertion workflows
Subtitles and captions	Preserves or generates caption workflows before delivery
Multi-bitrate ladders	Helps deliver adaptive playback to different network/device conditions
Transcoding	Aligns codec, bitrate, resolution, frame rate and audio format before CDN delivery
Playout	Generates continuous live channels from VOD files and live sources
Failover / hot swap	Helps build resilient live delivery workflows
HTTP delivery	Works with HLS, DASH and CDN caching strategies

Common CDN Origin Workflows

SRT Contribution to HLS Or DASH CDN Delivery

SRT is often used as the reliable contribution layer. Nimble Streamer receives the SRT source via Listen, Push or Rendezvous mode, then repackages or transcodes it when needed, and outputs HLS, Low Latency HLS or MPEG-DASH for CDN delivery.

Encoder / Larix Broadcaster
-> SRT
-> Nimble Streamer origin
-> HLS / LL-HLS / DASH
-> CDN
-> viewers

Use this when:

contribution reliability is important;
the source is remote;
CDN delivery must use HLS or DASH;
the workflow needs DVR, DRM, subtitles, SSAI or ABR before delivery.

SRT in Nimble Streamer

RTMP or RTSP to HLS CDN Delivery

Nimble Streamer can receive RTMP from encoders or RTSP from IP cameras and package those sources into HLS or MPEG-DASH for CDN delivery. Nimble supports Enhanced RTMP spec with multiple additional codecs to deliver.

RTMP encoder / RTSP camera
-> Nimble Streamer origin
-> HLS / DASH
-> CDN
-> players

Use this when:

existing encoders still publish RTMP;
camera sources use RTSP;
you need to modernize playback without replacing all sources;
the output must be CDN-friendly.

WebRTC WHIP to CDN or Recording Workflows

WebRTC WHIP is an ingest protocol. Nimble Streamer can receive WHIP publishers and then use the incoming source for transcoding, HLS/DASH packaging or other workflows.

WebRTC publisher
-> WHIP
-> Nimble Streamer
-> HLS / DASH
-> CDN
-> players

Use this when:

browser or mobile WebRTC publishing is required;
the same source must be used for low-latency playback and HTTP delivery.

WebRTC in Nimble Streamer

SDI, NDI or OMT Production Source to CDN Delivery

Nimble Streamer can connect broadcast and production sources to CDN-ready outputs through Live Transcoder.

SDI / NDI / OMT production source
-> Nimble Streamer + Live Transcoder
-> HLS / LL-HLS / DASH
-> CDN or playback system

Use this when:

the source comes from broadcast hardware or production infrastructure;
SDI, NDI or OMT must be converted into IP streaming outputs;
captions, audio layout, frame rate or resolution must be aligned before delivery.

VOD Origin for HLS and DASH

Nimble Streamer can package stored media files for VOD delivery through HLS and MPEG-DASH workflows. The workflow may include DRM, subtitles and adaptive playback.

VOD files
-> Nimble Streamer origin
-> HLS / DASH
-> CDN
-> VOD players

Use this when:

you need self-managed VOD packaging;
files must be delivered through CDN;
VOD files are part of a larger live/VOD platform.

Playout Channel to CDN Delivery

Nimble Streamer Playout can generate a continuous live stream from VOD files and live sources. You can mix various sources, define fallback sources, you can even automate your TV channel programming via your own systems. That output can then be packaged and delivered through CDN-facing protocols.

VOD files / live blocks
-> Nimble Streamer Playout
-> HLS / DASH
-> CDN
-> continuous channel playback

Use this when:

you need a 24/7 channel;
a playlist-based live-like stream is required;
event programming must be scheduled;
fallback content must be available;
an online radio or linear channel workflow is needed.

Related page: Nimble Streamer Playout

Single Origin, Multi-Tier and Multi-CDN Architectures

With Nimble Streamer, you can build delivery systems with any architecture best fit for your streaming scenarios.

Single Origin

In a single-origin architecture, one Nimble Streamer instance packages and serves streams to CDN or downstream viewers.

Use this when:

audience scale is moderate;
delivery geography is limited;
the CDN pulls from a single controlled origin;
the workflow is simple enough to operate from one origin layer.

Origin Plus Edge

In an origin-plus-edge architecture, Nimble Streamer acts as the controlled origin and downstream edge layers handle delivery closer to viewers.

Use this when:

the audience is distributed;
delivery needs better resilience;
you need to reduce load on the origin;
edge caching or regional distribution is required.

Multi-Tier Nimble Architecture

Nimble Streamer can also be used in multi-tier streaming architectures where upstream Nimble instances feed downstream Nimble instances and other CDNs.

Use this when:

you want to build part of your own delivery network;
live streams must be re-transmitted within your infrastructure;
different regions or customers need separated edge layers;
you need more control before handing traffic to a CDN.

Multi-CDN

Nimble Streamer can act as a controlled origin layer before one or more CDN providers. This allows streaming teams to keep ingest, packaging, DVR, DRM, SSAI and protocol conversion logic under their own control while using external CDN capacity for last-mile delivery.

Use this when:

you need redundancy between CDN providers;
you want more control over origin behavior;
large events require fallback delivery paths;
different regions perform better with different CDNs;
you need to switch distribution paths without changing ingest.

When Nimble Streamer is a Good CDN Origin

Nimble Streamer is a good origin choice when your team needs:

self-managed streaming infrastructure;
control over ingest and packaging;
multiple protocols at ingest;
HLS, Low Latency HLS or MPEG-DASH output;
live and VOD workflows on the same platform;
DVR before CDN delivery;
DRM before CDN delivery;
server-side ad insertion before CDN delivery;
captions, subtitles or ASR-generated WebVTT before delivery;
multi-bitrate ladder generation;
failover or hot swap workflows;
playout-generated channels;
protocol bridging between broadcast, contribution and playback systems;
API-driven automation;
cost control at the origin layer.

When You Still Need a CDN

Nimble Streamer is not a replacement for every CDN function. For large public delivery, a CDN or private edge infrastructure is usually still needed.

Use CDN or additional edge infrastructure when you need:

global last-mile scale;
delivery close to viewers in many regions;
very large public events;
edge caching at high traffic volume;
DDoS protection;
regional routing;
ISP peering benefits;
high availability at the network edge.

The practical model is often:

Nimble Streamer controls origin logic.
CDN handles large-scale last-mile delivery.

Nimble Origin vs CDN

Requirement	Nimble Streamer origin	CDN / edge network
Receive SRT, RTMP, RTSP, SDI, NDI, WHIP and other sources	Yes	Usually no or limited
Package HLS, LL-HLS and DASH	Yes	Usually pulls prepared output from origin
Transcode, filter or create ABR ladders	Yes, with Live Transcoder	Usually not the main CDN role
Apply DRM, SSAI, captions or workflow logic	Yes	May cache or deliver resulting streams
Deliver to global public audiences	Possible at small/moderate scale	Yes
Edge caching near viewers	Limited unless building multi-tier architecture	Yes
DDoS protection and large-scale network edge	Not the main role	Yes
Multi-CDN strategy	Can act as controlled origin	CDNs provide delivery paths

CDN Origin Features to Configure

HLS and DASH Packaging

Configure HLS, Low Latency HLS or MPEG-DASH output based on player requirements, CDN behavior and latency target. The CDN must be compatible with LLHLS.

Set up CDN-friendly streaming

Read these articles to fine tune your Nimble setup specifically for further CDNs delivery:

ABR Ladders

Adaptive bitrate ladders help deliver playback to viewers with different devices and network conditions. Use Nimble Live Transcoder when output variants require codec, bitrate, resolution, frame rate or audio changes.

Related page: Nimble Live Transcoder

DVR

DVR allows live streams to be recorded and played back through HLS or MPEG-DASH workflows. This supports rewind, catch-up and time-shifted viewing.

Related page: Nimble Streamer DVR

DRM

Nimble DRM can protect HLS and MPEG-DASH workflows. This is useful for premium OTT, IPTV and protected enterprise content.

Related page: Nimble Streamer DRM

Server-side Ads Insertion (SSAI)

Nimble Advertizer can provide server-side ad insertion for live and VOD workflows. This includes static rules as well as automation via custom handlers.

Related page:Nimble Streamer Advertizer

Captions and Subtitles

Caption and subtitle workflows can be prepared before CDN delivery. Nimble Streamer supports live and VOD subtitle workflows including CEA-608, CEA-708, DVB subtitles, DVB teletext, WebVTT and ASR-generated captions.

Failover and Hot Swap

Failover and hot swap workflows allow teams to switch between source origin and substitute streams with minimal disruption. This is useful for live events, backup sources and resilience planning.

There are two cases covered by this feature set:

Streams failover hot swap – when primary stream is active all the time and a substitute stream to replace it on some occasions;
Emergency streams hot swap – the substitute stream is inactive but when it goes live, it must replace the original stream.

Operational Checklist

Use this checklist before deploying Nimble Streamer as a CDN origin.

Choose source protocols: SRT, RTMP, RTSP, MPEG-TS, WHIP, SDI, NDI, OMT, HLS pull, Icecast or another supported input like playout.
Confirm source codecs and audio formats.
Choose output format: HLS, Low Latency HLS or MPEG-DASH.
Decide whether Live Transcoder is required.
Configure ABR ladder if adaptive playback is needed.
Configure DVR, DRM, SSAI or subtitles if required.
Configure CDN: set up pull or downstream delivery.
Validate cache behavior and segment duration.
Test playback on target devices.
Test failover or backup source behavior.
Monitor origin load and bandwidth.

Related Nimble Streamer Resources

FAQ

Can Nimble Streamer be used as a CDN origin?

Yes. Nimble Streamer can be used as a self-managed origin server or origin layer for live and VOD streaming. It can package incoming streams into HLS and MPEG-DASH, then serve them to CDN edges, multi-CDN setups, OTT platforms or private delivery infrastructure.

Does Nimble Streamer replace a CDN?

No. Nimble Streamer is not a CDN by itself. It can act as the controlled origin. Large-scale public delivery usually still needs CDN or edge infrastructure for last-mile distribution, caching, regional delivery and DDoS protection.

Can Nimble Streamer package HLS and DASH for CDN delivery?

Yes. Nimble Streamer supports HLS, Low Latency HLS and MPEG-DASH workflows for live and VOD delivery. These HTTP-based formats are commonly used with CDN infrastructure.

Does Nimble Streamer support Low Latency HLS as an origin?

Yes. Nimble Streamer supports Apple Low Latency HLS workflows. LL-HLS is useful when a team needs lower latency while keeping HTTP/CDN-compatible delivery.

Can Nimble Streamer be used in multi-CDN architectures?

Yes. Nimble Streamer can act as a controlled origin before one or more CDN providers. This lets teams keep ingest, packaging, DVR, DRM, SSAI and protocol conversion logic under their own control while using multiple CDNs for delivery.

Which source protocols can Nimble Streamer receive before CDN delivery?

Nimble Streamer can receive sources via RTMP, SRT, NDI, SDI, OMT, WebRTC WHIP, Zixi, RIST, RTSP, MPEG-TS over HTTP or UDP, HLS pull, Icecast and SHOUTcast workflows. VOD files and Nimble Playout can also be used as sources for CDN-facing outputs.

Can Nimble Streamer use SRT as a source for HLS CDN delivery?

Yes. Nimble Streamer can receive SRT contribution streams and output HLS, Low Latency HLS, MPEG-DASH or other formats for CDN delivery.

Can Nimble Streamer use SDI, NDI or OMT sources for CDN delivery?

Yes. Nimble Streamer can use SDI, NDI and OMT sources through Nimble Live Transcoder, then output HLS, Low Latency HLS and MPEG-DASH.

Can Nimble Streamer be used for VOD origin workflows?

Yes. Nimble Streamer can package and deliver VOD content through HLS and MPEG-DASH workflows. It can be used as a self-managed VOD origin before CDN delivery.

Can Nimble Streamer handle DRM before CDN delivery?

Yes. Nimble DRM can protect HLS and MPEG-DASH workflows. The protected outputs can then be delivered through CDN infrastructure.

Can Nimble Streamer handle server-side ad insertion before CDN delivery?

Yes. Nimble Advertizer can provide server-side ad insertion for live and VOD workflows. This lets teams prepare monetized outputs before CDN delivery.

When do I need CDN edges in addition to Nimble Streamer?

Use CDN edges when you need large public scale, delivery close to viewers, global distribution, edge caching, DDoS protection, regional routing or high availability at the network edge.

Start Building A CDN Origin Workflow

Start by choosing your ingest protocol, output protocol and delivery architecture. Then confirm codec compatibility, whether Live Transcoder is required, and which CDN or edge layer will pull from Nimble Streamer.

Primary next steps: