StreamWizardStreamWizard

Cloud OBS

Your OBS, in the cloud.
Your phone runs it.

Built for IRL streamers. A dedicated OBS for your channel, an ingest that speaks SRT and SRTLA, and an auto switcher that covers for your connection before chat notices.

Your stream setup, already running

  • A dedicated OBS for your channel, booted in the cloud when you need it.
  • Your phone or encoder streams in over SRT or SRTLA.
  • Signal drops mid stream? The auto switcher swaps to your connection-lost scene, tells chat, and swaps back when the bitrate recovers.
  • Need eyes on OBS itself? Open the live OBS window in a browser on your PC, with CPU, memory, FPS, and frame time next to it.
streamwizard.org/obs-viewer?instanceId=facade1d-7e57-c0de-face-c0ffeedecade
Cloud OBS
FileEditViewDocks
Scenes▣

--------------

▲▼
Sources▣
▲▼
IRL CAM
SRT · 6200 kbps
−62%+Scale to Window
No source selectedPropertiesFilters
Audio Mixer▣
0 hiddenOptions
Scene Transitions▣
Stinger
Controls▣
00:00:00CPU: 0.3%30.00 / 30.00 FPS

Real footage from xpudu's IRL streams

Stream Deck

OBS Connected

Current scene

IRL

Auto switching is on. Tap a scene to hold it.

Stream

Offline

The mobile deck runs the show

The deck lives on your phone and installs like an app. No PC, no tech BS, just stream. Switch a scene here and watch it land in the OBS window above.

  • Go live and end the stream from your pocket.
  • Switch scenes, or hold one while the auto switcher waits.
  • Edit your stream title and category between locations.
  • Read and send Twitch chat without leaving the deck.

Your own OBS stays yours. Cloud OBS is there for the streams your PC cannot follow.

Your phone streams in.
The cloud stays on air.

StreamWizard runs an SRT and SRTLA ingest server that receives the video from your phone or encoder and hands it to your cloud OBS. One thing to decide: how many connections you are streaming over.

Your phone or encoder

Whatever you already stream with. It sends out over SRT or SRTLA.

StreamWizard ingest

Catches your feed and keeps an eye on how it is doing, once a second.

Your cloud OBS

Pulls that feed into the IRL scene it set up for you on first boot.

Twitch

OBS streams out from the cloud, so your phone is not the thing on air.

Pick one

SRT

port 8888

One connection. Start here.

A phone with one SIM, a phone on wifi, or a single encoder. Point it at the SRT URL, paste your key in as the stream ID, and you are live. This is what most IRL streamers use and it needs nothing you do not already own.

  • Any app or encoder that speaks SRT.
  • Made for connections that come and go, so a rough patch stays a rough patch instead of a dead stream.

SRTLA

port 5000

Several connections at once.

Two connections or ten, arriving as one stream. Two SIMs, a SIM and wifi, or everything you can get your hands on. When one of them walks into a dead spot the others carry you, so pick this if one connection does not cover where you stream.

  • Belabox, Moblin, IRLToolkit and anything else that speaks SRTLA.
  • A connection can drop and come back without your stream noticing.

One key, two URLs

SRT
srt://your-ingest:8888
SRTLA
srtla://your-ingest:5000
Stream ID
4f2a…c91b

Copy them from the dashboard, or have the key sent to you as a Discord DM so you are not typing 64 characters on a phone.

  • Rotate the key whenever you want. The old one stops working the second the new one appears.
  • Your OBS boots with a scene called IRL and a source called StreamWizard Ingest, already pointed at your feed. Nothing to wire up.
  • Plain RTMP works too, but the auto switcher only sees your bitrate on it, not your ping or your dropped packets.

Setting yours up for the first time? Read the IRL docs.

The auto switcher

You walk under a bridge.
Chat never sees the frozen frame.

The auto switcher checks the stats at your ingest once a second, moves your cloud OBS to a fallback scene when the connection goes bad, and switches back once it is properly stable. Here it is doing exactly that on a walk that goes wrong. Or grab a slider and break the signal yourself.

Walking the open street. Signal is good.

Your phone or encoder

The signal you send

Bitrate

no data

Ping (RTT)

no data

Dropped packets

no data

Ingest

Stats once a second

Auto switcher

Checking signal

Bitrate

0/6s good

Ping

0/6s good

Loss

0/6s good

Live in 6s

IRL

clean feed

Connection Lost

hold screen

Twitch

What chat sees

Sensitivity

Checking the feed before it is allowed on the live scene. 0s into the walk.

Sensitivity

OBS Connected

Warming up

Sensitivity

How quickly the auto switcher reacts when your IRL signal gets rough. Changes land while you stream.

Advanced mode

Tune every threshold yourself instead of using a preset.

Retune from your pocket

Sensitivity lives on the deck too. This one is wired to the switcher above, so what you tap here retunes the demo live.

  • Changes land mid-stream. The switcher picks them up within a second, and your stream and ingest never restart.
  • Retune for where you are: Relaxed for the woods where dead spots are normal, Fast for the city where a single frozen frame stands out.
  • Pick a preset or flip advanced mode here and the switcher above follows.
  • Tap a scene on the deck and it goes on air. The switcher stands down until you let go.

Scenes are tracked by their id inside OBS, not their name, so renaming a scene months later does not quietly break your switcher.

Three presets.
Or every number, yours.

Three presets set the bitrate floor, the ping ceiling, the dropped-packet limit and how many bad seconds trigger a switch, and a custom mode lets you set every number yourself. Pick how twitchy it is and get on with your stream. The exact thresholds are below, because you are going to ask anyway.

Auto switcher sensitivity presets and the thresholds each one sets. Choose a preset to retune the demo.
Threshold
Bitrate floor300 kbps500 kbps800 kbps
Ping ceiling2000 ms1500 ms1000 ms
Dropped packets2%1%0.5%
Switch after6s bad4s bad2s bad
Back after15s good8s good5s good
Startup check8s6s4s
Offline after10s quiet7s quiet5s quiet

Switches after ~4s bad, back after ~8s stable. The right pick for most IRL setups.

Chat hears what happened.
You do not type a word.

Each time the auto switcher changes scene it posts a message in your Twitch chat, as you, with the bitrate, ping, packet loss and scene filled in. Three messages you write once. The switcher fills in the numbers behind the switch and posts them in your channel while your hands are busy holding a camera.

The three you write

These are the defaults. Change them to your voice.

Quality dropped

Connection unstable — switching to backup scene ({bitrate} kbps, {rtt} ms RTT)

Signal lost

Stream signal lost — hang tight!

Back live

Signal restored — back live!

Four things it fills in

{bitrate}
The bitrate arriving when it switched, in kbps.
{rtt}
The round trip time to your phone, in milliseconds.
{loss}
Dropped packets as a percentage, the number it judged.
{scene}
The scene it moved you to.

Your Twitch chat

Nothing yet. The walk above has not gone wrong, so chat has not been told anything.

Sent as the broadcaster. No bot account in your mod list, no command for chat to spam.

It posts as you

Not as a bot in your mod list. Chat reads it as the streamer saying something, because that is what it is.

Once per switch, not once per second

The switcher can watch a metric flap for a minute. Chat hears about the switch, and nothing else.

No all clear out of nowhere

Back live only goes out if chat was told about a problem first, and only within ten minutes of it. Start a stream cold and it says nothing at all.

The whole control room.
One thumb.

The deck is a phone-sized web app that controls your cloud OBS: scenes, chat, stream info and switcher sensitivity. It opens in your browser and installs to your home screen like an app. Four tabs, tiles you can hit without looking, and zoom locked so fast tapping never fights you.

Deck

Go live, end the stream, and a grid of scene tiles big enough to hit while walking. Start and stop the cloud OBS itself from here too, with a boot stepper while it comes up.

Chat

Read your Twitch chat and reply to it, with 7TV, BetterTTV and FrankerFaceZ emotes rendered next to Twitch's own.

Stream info

Change your title and your category between locations, without opening a browser or asking a mod to do it.

Sensitivity

The three auto switcher presets and the full custom matrix. Scenes stay on the dashboard on purpose: this tab is for what you change while moving.

Tap a scene and the switcher stands down

Cutting to your BRB screen only to be dragged back two seconds later is the worst thing an auto switcher can do to you. So tapping a tile is a hold: the scene goes up and the switcher waits. A card tells you what you are holding and gives you the button to let go.

  • Hold for 15 minutes, an hour, or until you release it yourself.
  • Let go and the switcher starts counting from zero, so it has to earn the live scene back the same way it always does.
  • Scene changes made anywhere show up everywhere: the deck, the OBS window in your browser, and OBS itself.

Setting it up takes a minute. Read the deck docs.

Overlays that know where you are.

IRL widgets put your live speed, distance, city and weather on stream, read from the GPS of the phone you stream with. Build it in the editor, paste one URL into cloud OBS.

Just don't dox yourself while your home.

Browser source · 1920×1080

Your phone

Open the overlay on the phone you stream from. It reads the GPS. No extra hardware.

StreamWizard

Every fix becomes speed, distance, the city you are in, and the weather there.

OBS

One browser source shows it all. Cloud OBS, or the OBS on your PC.

The walking stats bar

SpeedDistanceLocationWeather

One bar along the bottom. Toggle each module on or off.

Single-value widgets

SpeedHeadingAltitudeLatitudeLongitudeAccuracy

Straight from the GPS. Place them anywhere on the canvas.

When the feed drops, the auto switcher cuts to your connection lost scene. Build that one in the same editor: clips from your last stream and a hang tight message beat a frozen frame.

Want a widget that is not here? Ask in the Discord. That is where the widget list grows.

Same editor, same widgets, in the OBS on your PC too. Read the overlay docs

FAQ

Before you launch a container.

What the words mean, what you need, what persists, and what it costs.

What is cloud OBS?
Cloud OBS is a real copy of OBS Studio running in a container on StreamWizard's servers instead of on a PC at home, and it is the thing streaming to Twitch. Your phone or encoder sends video to a StreamWizard ingest server, cloud OBS picks that feed up as a source, and OBS does the rest: scenes, overlays, browser sources and the encode to Twitch. You control it from the deck, a web app on your phone, or open the full OBS window in your browser. Because the encode happens on a machine with a wired connection, your side only has to get video to the ingest. If that link drops, the auto switcher moves OBS to a fallback scene and your channel stays live. Cloud OBS is the paid part of StreamWizard and is in invite-only beta right now.
What is IRL streaming?
IRL streaming is broadcasting live from outside on a mobile connection, with a phone or a bonding encoder as the camera instead of a PC and a webcam. Walks, drives, markets, festivals: the stream goes wherever you go, which is the appeal and the problem. Mobile signal comes and goes. A tower handover, a tunnel or a crowd on the same cell can drop your bitrate for a few seconds, and on a normal setup that means a frozen frame or a dead stream. IRL setups deal with this in two places: an encoder that speaks SRT or SRTLA so a rough patch arrives as normal video, and something at the other end that covers for you when the connection fails. In StreamWizard that other end is cloud OBS with the auto switcher, so chat sees a fallback scene instead of a frozen face.
Do I need a PC running at home?
No. OBS runs in a container in the cloud, on our machines, and it is the thing streaming to Twitch. Your phone only sends video to the ingest. It can drop to one bar, switch networks or run out of battery, and your Twitch stream stays up on the fallback scene.
What do I stream from the street with?
Any app or encoder that speaks SRT or SRTLA. A streaming app on your phone, or a bonding encoder like Belabox, Moblin or IRLToolkit. One connection goes to the SRT URL, several at once go to the SRTLA one, and both use the same key.
What is SRT?
SRT (Secure Reliable Transport) is a video transport protocol built for unreliable networks, which makes it the standard way to get an IRL stream from a phone to a server. It runs over UDP and keeps a latency buffer on both ends: your encoder holds the last few seconds of video, and when a packet goes missing the receiver asks for it again and gets it before it is due to play. On the usual defaults that buffer is 2.5 seconds on the encoder, and the StreamWizard ingest holds 4 more, which is why a tower handover arrives as normal video instead of a stutter. Almost every IRL app and encoder speaks SRT. With StreamWizard you point it at the SRT URL on port 8888, paste your key in as the stream ID, and cloud OBS picks the feed up.
What is SRTLA?
SRTLA (SRT Live Ack) is an extension of SRT that bonds several internet connections into one stream, so two SIMs, a SIM and wifi, or everything you can get your hands on arrive at the ingest as a single SRT feed. Each connection carries a share of the packets and the receiver puts them back in order. When one connection walks into a dead spot the others carry the stream, and when it comes back it rejoins without your stream noticing. That is the difference from plain SRT: SRT survives a rough patch on one connection, SRTLA survives losing a connection. Bonding encoders like Belabox and Moblin speak it, and so does IRLToolkit. On StreamWizard the SRTLA URL uses port 5000, the SRT URL uses 8888, and both take the same key, so pick whichever matches how many connections you stream over.
How long is the delay?
Around 10 seconds from your camera to a viewer's screen. Your encoder holds an SRT latency buffer, 2.5 seconds on the usual defaults, the ingest holds 4 more, and Twitch adds its own on top. That buffer is the point: it swallows the packets a tower handover loses, so a rough minute of walking arrives as normal video instead of a stutter, and the switcher still has good frames to play with while it decides.
Is it real OBS, or your version of it?
Real OBS. You open a window in your browser and you are looking at the actual OBS running in your container, scene list and all. Browser sources from any alert provider work the same as they do at home, so bring the overlays you already use.
Do I lose my scenes when I stop the container?
No. Scenes, sources and uploaded files live on your container and come back the next time you start it. Stop it between streams so it is not sitting there running while you sleep.
What does it cost?
Cloud OBS, the ingest server and the deck are the paid part of StreamWizard, in invite-only beta right now, so access goes out by hand in Discord. Full split on the pricing page.

Beta

Cloud OBS, the ingest server and the deck are a paid plan, and they are in beta. Access goes out by hand while we find the rough edges, so the way in is to ask in Discord. Prices land with the plan story. Clips, overlays and analytics stay free and open source either way, and the full split is on the pricing page.

Last updated

Sign in and poke around.

Log in with Twitch, no card needed. Clips, overlays, and analytics are free and open source.

Star on GitHubJoin the Discord