PROVID
Dashboard

Secure keys for your streams.

Secure ingest keys for the relay. One key for SRT, SRTLA or RTMP. Bonding across multiple connections, auto-reconnect, and automatic rerouting to another location during maintenance or outages.

Go to dashboard
Encoders
OBS Studio
RTMP / SRT
BELABOX
SRTLA
LiveU Solo
SRT
Haivision
SRT
FFmpeg
RTMP / SRT

PROVID Relay

Location
Region
Frankfurt
Protocol
RTMP / SRT
Vault
Locked
Playback
HLS

From first click to live stream.

Keys share the same clean lifecycle, from generating to rotating.

  • Generate. From the dashboard with your chosen protocol and region.
  • Connect encoder. Drop the ingest URL and key into your encoder.
  • Live & monitor. Stream runs, stats and events stream right along.
  • Rotate or revoke. A new key is a new ingest. The current session drops; reconnect the encoder with the replacement.

Key Vault

3 active

Main relay · OBS

SRT

sk_live_••••4f2a · FRA · 6,500 kbps

Road kit · BELABOX

SRTLA

sk_live_••••91c8 · LAX · 4,500 kbps

Guest host · Mira

RTMP

sk_live_••••7b13 · NYC · 8,000 kbps

Embed the streamwithout exposing the streamkey.

A player key is a separate, scoped key for embedding the live player on third-party sites. The encoder keeps the real streamkey; the embed gets its own. Available on relays with authentication enabled.

Safe to embed.

Player keys are separate from the ingest key. Put them on sites and overlays without giving away the real key.

Revocable per embed.

Each key is independent. If one embed leaks, revoke just that key, the stream and the other embeds keep running.

Stats without personal data.

A player key shows stats without viewer IPs and without a path back to the streamkey.

Relay infrastructurewithout the rack.

Multiple protocols, secure keys, bonding, auto-reconnect, path protection and automatic rerouting, all behind one URL.

Multiple protocols

SRT, SRTLA and RTMP on a single endpoint. Whatever your encoder speaks, we receive.

SRTLA bonding

Multiple connections in parallel, e.g. several modems or Starlink.

Auto-reconnect

Connection comes back automatically once the line is up again, depending on your streaming software.

Auto-rerouting

During maintenance or outages, your stream automatically switches to another location.

SMPTE ST 2022-7

Send the same stream to several relay servers at once. Blue/Red is the two-path example; more paths are possible. If one path drops, the others keep the stream up.

Stream check

Black frames, freezes and silence on the relay, in seconds. No extra load on the encoder.

Many signals in, one stream out.

Several connections in parallel come together at the relay. Combine 5G, LTE, Wi-Fi and Starlink on a bonding encoder; PROVID aggregates them.

  • Encoder needs to support it. Bonding is SRTLA on the contribution. The encoder has to open several connections, such as BELABOX, LiveU and similar kits. A single RTMP send is one path.
  • Survives handoffs. Dead zones, cell handovers and a dropped SIM can't kill the stream, the other links cover it.
  • Lives in the encoder. The encoder does the bonding. The relay takes the bonded stream.

Frame-locked multicam, no timecode hardware.

The relay stamps a shared clock on the streams you already push. In Cloud OBS, add them as PROVID Sync Sources in one group and cut them together.

  • Timecode baked in. The relay stamps it on the segments. Nothing extra on the encoder.
  • No sync boxes. No LTC, no genlock. The relay clock is enough for everyone.
  • PROVID Sync Sources. Several streams in one group in Cloud OBS. Then you cut.
  • Streams you already push. One more camera is one more streamkey.

One relay. Multiple audio tracks.

Send multiple audio tracks (languages, clean mix, commentary) over one relay. The relay labels each track and gates access by play-key, so different viewers get different audio from the same stream.

  • Multi-track over one key. Languages, commentary and a clean mix ride a single relay, no parallel streams.
  • Per-key access. Play-keys decide which tracks a viewer can hear; scope or revoke access per embed.
  • Standards-based delivery. HLS alternate-audio for browsers and players, native SRT track passthrough for pulls.

Stream check on the relay.

Black frames, freezes and silence on the relay, in seconds. Notify by mail, webhook and more from the dashboard.

Live feed
1 alert sent
detecting: black frames
Guard watch
Alerts mail · webhook

black frames

now
  • On the relay. Black frames, freezes and silence, not your local preview.
  • Notify your way. Mail, webhook and more. Set it in the dashboard.
  • Start and end. You hear when it starts and when it clears.
  • Nothing extra on the encoder. The check runs on the relay.

Standard HLS, any player.

Adaptive (ABR)
…/hls/{key}/master.m3u8

Stream and play keys resolve to a standard HLS playlist. It's adaptive (ABR) and drops straight into any HLS player. VLC, ffplay, Safari, hls.js or the OBS Media Source.

Pin a quality
…/hls/{key}/1080p.m3u8 · 480p.m3u8 · …

Per-rendition variant playlists let you lock a specific quality, handy in OBS, instead of letting the player switch adaptively.

From encoder to the relay in three steps.

Generate a key, connect your encoder, go live. No DNS hassle, no platform keys on the device.

01

Generate an ingest key

In the dashboard: pick a protocol (SRT/SRTLA/RTMP), set region and bitrate limit.

02

Connect your encoder to PROVID

OBS, BELABOX, LiveU, Haivision, FFmpeg, drop in the ingest URL and key, your encoder never sees the platform.

03

Forward securely

PROVID keeps the stream at the location. Use it internally, route it to the studio, or send it onward from Cloud OBS or your encoder.

Ready to send?Generate a key.

Encoders on set point to PROVID. Isolated ingest keys, bonding and stream check keep the contribution stable.

Generate ingest key