How Vasl works - Vasl

A stream enters Vasl, gets adapted if the next hop needs it, and leaves toward a player or another server. You run that path on one install.

Ingest

Publish from the encoder, the room, the file, or a URL already on the network.

In	Typical source
WebRTC / WHIP	Browsers, and encoders that already speak WHIP
SIP	Room systems and phones, with audio and video
RTMP	OBS, vMix, Wirecast, and desk encoders
RTSP	Cameras and recorders, pulled or pushed
SRT	Contribution across a long or lossy link
NDI	Switchers, graphics, and cameras on the studio network
File or URL	A file you already have, or a stream at an address you can reach

Process

Vasl transmuxes when the next protocol can take the codec. It transcodes audio and video when it cannot. Recording, poster frames, level and mix, and cue points sit on the same path. See Process and Recording.

Deliver

Out	Use it when
WebRTC / WHEP	Someone in the session needs to answer
HLS	People are only watching, and a CDN may cache the playlist
RTSP	The next player or recorder expects RTSP
RTMP or SRT restream	The program has to move to another destination

What stays on the install

Metrics, logs, and a per-stream trace are part of the same machine. See Operations. Keys, signed links, SSO, and TLS are how you keep the URLs closed. See Security. A second machine is a load balancer and a warm standby that you operate. Vasl leaves that design with you. See Install.