connected
Go live. Stay live.
IRL streaming that survives dead zones. Your phone streams to your own server, and your server keeps the broadcast alive. Lose signal and viewers see your Be-right-back screen, not an ended stream. It’s over only when you end it.
Free, open source, one command. The iPhone app is still in testing and not open yet. Your crew needs no app at all: chat, alerts, program view, and TTS run in any browser on your own domain.
You’re still live. Viewers are seeing your Be-right-back screen.
Only End Stream ends it. The card holds through restarts and hour-long outages.
What it does
The whole chain, self-hosted, from your phone to Twitch.
Never cuts out
Your server owns the broadcast; your phone just feeds it. Dead zone, phone restart, hour-long outage: viewers see your Be-right-back screen until you’re back. Only End Stream ends it.
Every connection at once
WiFi, cellular, and your crew’s phones bond into one uplink. One path chokes, the others carry the stream. Built for weak rural signal, not studio fiber.
Your own studio
Alerts burned into the video, chat and channel-point TTS with real controls, bits thresholds, donations through your own Stripe. Self-hosted, nobody in the middle.
Get it
A server you own, and a phone that feeds it.
Point a domain at a small VPS (about $5 a month) and run the one setup command from GitHub. It installs the relay, the never-cut-out engine, your studio, and HTTPS.
Install the app on your phone, point it at your relay, and log in.
Go live. Your crew opens chat, alerts, program view, and TTS in a browser on your domain, with the permissions you choose.
Questions
The ones people actually ask.
What actually happens when I lose signal?
Do I need my own server?
What do I stream from?
How do I install the Android APK?
1c62a723a824e4687937a63f6437339b3d1d60093aee5568adc4ba06f28b8063.