Multisite

One service, every venue.

Distribute a service to every campus on multisite-cloud — with software where you have a computer, or an Outpost where you want a box. And choose the trade that suits the room: rock-solid and a few seconds behind, or live and talking back.

Join early access See how it works

Runs on multisite-cloud Endpoint: obs-multisite or Outpost Same account as Cloud

In practice

The same service in every room — reliably behind, or live and talking back.

Choose the trade

Reliability, or low latency. Not the same thing.

A campus following the service and an overflow room that needs to talk back want different things. Multisite gives you both, and you pick per venue.

Reliability mode

Cloud-storage relay, from obs-multisite

Your service is written into ultra-reliable cloud storage as it happens, and each venue pulls it back down. There is no fragile direct connection between venues — if a link stutters, the venue simply follows a little further behind. Nothing is lost.

The trade The campus may run a few seconds behind the main room.

Survives an ordinary or unreliable line
No dropped frames, no dead screens
Proven engine, already soaked

Available

Low-latency mode

SRT today, WebRTC for talkback

Carry the venue live, in step with the main room. With WebRTC it is sub-second and bidirectional — an overflow room or a remote panellist can speak back.

The trade Needs a better link, and is less forgiving when it drops.

Watch in step with the main room
Bidirectional talkback Coming
For overflow rooms, panels and Q&A

SRT available WebRTC coming

Comparison of multisite reliability and low-latency modes
At a glance	Reliability mode	Low-latency mode
Built on	Cloud-storage relay (`obs-multisite`)	SRT, or WebRTC
Latency	A few seconds behind	Live / sub-second*
If the link drops	Nothing lost; venue falls behind	Needs a good link
Talkback	No	Yes (WebRTC)
Best for	Campuses following the service	Overflow rooms, panellists, Q&A
Endpoint	Software or Outpost	Software or Outpost

* WebRTC is on the roadmap, not shipped. SRT low-latency is available today.

How it fits together

One control plane. Every venue. One of two paths.

Source

Your main service

An encoder, or an Outpost. Either way it feeds one place.

Control plane

multisite-cloud, on Cloudflare

One account, one dashboard, one invoice.

Reliability path

Cloud-storage relay

The service is written to cloud storage; each venue pulls it back and follows a few seconds behind.

Low-latency path

SRT or WebRTC to the venue

Live and in step — and, with WebRTC, able to talk back.

Destination

Every campus lights up

Satellites, overflow rooms, remote panellists.

A rule of thumb

Which mode for which room?

A campus following the sermonReliability — being a few seconds behind costs nothing.

An overflow room watching liveLow latency — nobody wants to hear the room next door.

A remote panellist who speaksLow latency with talkback — WebRTC, when it lands.

A venue on an unreliable lineReliability — retransmission beats a perfect connection you don't have.

What makes it different

Built for the way venues actually are.

Most multisite products assume a perfect network and a helpful IT department. This one assumes neither.

Reliability mode

Cloud storage as the go-between; venues follow a few seconds behind and nothing is lost.

Low-latency mode Coming

SRT today, WebRTC for sub-second bidirectional talkback.

No network configuration

No static IP, port forwarding or VPN. Works over fibre, 4G/5G, bonded or Starlink.

Restream relay

A service taken in at one place can be relayed onward to YouTube, Facebook, or any other RTMP or SRT destination — another campus, another platform, another vendor.

Installed-audio friendly

Coexists with AES67 / Dante audio-over-IP.

Capabilities marked as available are in the existing obs-multisite engine; anything on the roadmap is labelled where it appears.

Two endpoints

Software where you have a computer. Hardware where you want a box.

Both run from multisite-cloud, and both work in either mode.

Software

`obs-multisite`

The proven store-and-forward relay, running on a machine you already have. The fastest way to light up a campus with no new hardware.

Runs on a computer you already own
Store-and-forward reliability built in
Configured from the same dashboard as Cloud

Available

Hardware

StreamWorks Outpost

A fixed-install appliance for venues that shouldn't need a laptop in the room. It joins with a code and disappears into the rack.

Claim by code — no passphrases copied by hand
Health reported into your dashboard
Keeps running if our control plane doesn't

In development Register interest →

At the far end, a Raspberry Pi is often enough — silent, inexpensive, and easy to hide behind a screen.

In the same account

Multisite is not a second product to manage.

It lives beside Cloud, so a church that streams publicly and to its campuses keeps one login, one dashboard and one invoice.

One account

Cloud channels and Multisite venues in the same organisation.

One health view

Every venue's link quality beside every public stream.

Pull link per channel

Admin-controlled, because handing the feed to a venue is account structure, not something a producer should do mid-service.

The limit, said out loud

There is one playback passphrase per feed, and every venue shares it. A single campus cannot be revoked without rotating the passphrase for all of them. For a church with a handful of campuses that is fine. If you are an events company reselling a feed to clients, tell us — we would rather recommend the right thing up front than have you discover this later.

Early access

Tell us about your campuses.

Plans and commercials for Multisite aren't finalised. If you run more than one venue, we'd like to hear how it works today — it will shape what we build.

No card, no commitment.

Talk to us about your campuses Join early access