What Jadarit is

Jadarit takes video in over RTMP or WebRTC, and gives it back out over HLS and WebRTC. It runs as one binary on hardware you control. There is no cloud component, no per-viewer billing, and nothing phones home.

Passing video through

Most media servers decode every incoming stream and encode it again on the way out. Jadarit does not. Frames are parsed for their boundaries and repackaged into whichever container the viewer needs, so the picture that leaves the server is bit for bit the picture that arrived.

That is why it runs comfortably on small machines. A 1080p stream costs a few percent of a core rather than most of one.

Audio is the exception. WebRTC needs Opus and HLS needs AAC, so audio is converted per output. It is a fraction of the cost of touching video.

The words used here

Term	Meaning
Application	A namespace. Streams, VOD assets, ads, recordings, and keys all belong to one. The default application is called default.
Stream	One live video source inside an application, identified by a name.
Publish key	A secret an encoder presents in order to publish. See Apps and keys.
VOD asset	A stored file that has been conditioned so it can be played out cleanly.
Playlist	An ordered list of VOD assets that can be run as a continuous channel.
Ad break	A commercial spliced into the media timeline, signalled with a discontinuity.

What goes in and what comes out

Direction	Protocol	Notes
In	RTMP	OBS, vMix, FFmpeg. Enhanced RTMP is supported, so HEVC arrives intact.
In	WHIP	WebRTC ingest from a browser, no plugin needed.
Out	HLS	Standard segmented HLS, for reach and for devices that need it.
Out	WHEP	WebRTC playback, typically under a second of latency.

Both outputs come from the same ingest. You do not choose one at publish time.

What it needs

A 64-bit Linux machine. Because video is not re-encoded, the bar is low: a modest two-core VPS handles several concurrent 1080p streams. Ad insertion and playout add a little CPU for audio, not for video.