# IRLServer — full site content

> IRLServer runs RTMP, SRT and SRTLA relay endpoints for IRL streamers: your encoder sends to a relay near you, the relay forwards to the streaming software you already run, and your stream survives the moment a mobile uplink does not.

This file is the complete text of 41 pages, converted from https://irlserver.com. The index with one-line summaries is at https://irlserver.com/llms.txt.

Source: https://irlserver.com

# Your signal drops. Your stream doesn't.

Professional stream relay with automatic scene switching, drop protection, and global coverage.

[Explore Features](#features) [View Pricing$9.99](#pricing)

No Data Caps

Global Servers

RTMP, SRT & SRTLA

Works with the gear you already own

-   BELABOX
-   MOBLIN
-   IRL PRO
-   LIVEU
-   IRLBOX
-   LARIX
-   OBS
-   SRTLA
-   SRT
-   RTMP
-   RTMPS

What you actually get

## One screen. Every endpoint.

Each endpoint you own, the protocols it speaks, and the stream details to paste into your encoder — behind a copy button, not a support ticket. Add one, move it to another region, or share it with a co-streamer from the same place.

![The IRLServer dashboard: a live stream at 8.2 Mbps with its bandwidth graph, endpoint slots in use, and a relay endpoint with the protocols it accepts.](/_next/image?url=%2Fimg%2Fdashboard.png&w=3840&q=75&dpl=dpl_Gk9qPULqTp72ajXnUbe9fy8fHN3k)

[See how the stream reaches OBS →](https://irlserver.com/guides/obs-setup)

## TRUSTED BY STREAMERS WORLDWIDE

[

![Mystixx](https://static-cdn.jtvnw.net/jtv_user_pictures/b64ab5ec-75d9-4382-bb58-f9fef5968853-profile_image-600x600.png)

Mystixx PARTNER

36.3K

LIVE

](https://www.twitch.tv/mystixx)[

![Detoo](https://static-cdn.jtvnw.net/jtv_user_pictures/48c42865-4686-41fc-bc49-d2526b6d9140-profile_image-600x600.png)

Detoo PARTNER

87.6K

](https://www.twitch.tv/detoo)[

![Melkepakken](https://static-cdn.jtvnw.net/jtv_user_pictures/38080fe4-cf2c-47f1-9917-5090dcd75f27-profile_image-600x600.png)

Melkepakken AFFILIATE

1.7K

](https://www.twitch.tv/melkepakken)[

![Skiben](https://static-cdn.jtvnw.net/jtv_user_pictures/ec542cdf-1fee-4be9-8ed1-7e27b742e704-profile_image-600x600.png)

Skiben PARTNER

8.6K

LIVE

](https://www.twitch.tv/skiben)[

![Jenserkongen](https://static-cdn.jtvnw.net/jtv_user_pictures/f2614bf3-1614-4f94-b5bb-8ef37d54bc0a-profile_image-600x600.png)

Jenserkongen AFFILIATE

7.1K

](https://www.twitch.tv/jenserkongen)[

![Danniz](https://static-cdn.jtvnw.net/jtv_user_pictures/0f3b5303-c694-4b6e-ad85-eed283e36514-profile_image-600x600.png)

Danniz PARTNER

44.4K

LIVE

](https://www.twitch.tv/danniz)[

![Mystixx](https://static-cdn.jtvnw.net/jtv_user_pictures/b64ab5ec-75d9-4382-bb58-f9fef5968853-profile_image-600x600.png)

Mystixx PARTNER

36.3K

LIVE

](https://www.twitch.tv/mystixx)[

![Detoo](https://static-cdn.jtvnw.net/jtv_user_pictures/48c42865-4686-41fc-bc49-d2526b6d9140-profile_image-600x600.png)

Detoo PARTNER

87.6K

](https://www.twitch.tv/detoo)[

![Melkepakken](https://static-cdn.jtvnw.net/jtv_user_pictures/38080fe4-cf2c-47f1-9917-5090dcd75f27-profile_image-600x600.png)

Melkepakken AFFILIATE

1.7K

](https://www.twitch.tv/melkepakken)[

![Skiben](https://static-cdn.jtvnw.net/jtv_user_pictures/ec542cdf-1fee-4be9-8ed1-7e27b742e704-profile_image-600x600.png)

Skiben PARTNER

8.6K

LIVE

](https://www.twitch.tv/skiben)[

![Jenserkongen](https://static-cdn.jtvnw.net/jtv_user_pictures/f2614bf3-1614-4f94-b5bb-8ef37d54bc0a-profile_image-600x600.png)

Jenserkongen AFFILIATE

7.1K

](https://www.twitch.tv/jenserkongen)[

![Danniz](https://static-cdn.jtvnw.net/jtv_user_pictures/0f3b5303-c694-4b6e-ad85-eed283e36514-profile_image-600x600.png)

Danniz PARTNER

44.4K

LIVE

](https://www.twitch.tv/danniz)[

![Mystixx](https://static-cdn.jtvnw.net/jtv_user_pictures/b64ab5ec-75d9-4382-bb58-f9fef5968853-profile_image-600x600.png)

Mystixx PARTNER

36.3K

LIVE

](https://www.twitch.tv/mystixx)[

![Detoo](https://static-cdn.jtvnw.net/jtv_user_pictures/48c42865-4686-41fc-bc49-d2526b6d9140-profile_image-600x600.png)

Detoo PARTNER

87.6K

](https://www.twitch.tv/detoo)[

![Melkepakken](https://static-cdn.jtvnw.net/jtv_user_pictures/38080fe4-cf2c-47f1-9917-5090dcd75f27-profile_image-600x600.png)

Melkepakken AFFILIATE

1.7K

](https://www.twitch.tv/melkepakken)[

![Skiben](https://static-cdn.jtvnw.net/jtv_user_pictures/ec542cdf-1fee-4be9-8ed1-7e27b742e704-profile_image-600x600.png)

Skiben PARTNER

8.6K

LIVE

](https://www.twitch.tv/skiben)[

![Jenserkongen](https://static-cdn.jtvnw.net/jtv_user_pictures/f2614bf3-1614-4f94-b5bb-8ef37d54bc0a-profile_image-600x600.png)

Jenserkongen AFFILIATE

7.1K

](https://www.twitch.tv/jenserkongen)[

![Danniz](https://static-cdn.jtvnw.net/jtv_user_pictures/0f3b5303-c694-4b6e-ad85-eed283e36514-profile_image-600x600.png)

Danniz PARTNER

44.4K

LIVE

](https://www.twitch.tv/danniz)

### What our users say

"IRLServer is a great choice for streaming. The setup process is straightforward, the pricing is reasonable, and customer service is highly responsive. You can stream with good quality using either your phone or a backpack."

![Mystixx](https://static-cdn.jtvnw.net/jtv_user_pictures/b64ab5ec-75d9-4382-bb58-f9fef5968853-profile_image-600x600.png)

Mystixx PARTNER

36.3K followers

740K

Followers reached

100+

Streamers

99.9%

Uptime

24/7

Support

## BUILT FOR IRL

RTMP, SRT and SRTLA relay endpoints with custom optimizations for professional IRL streaming.

### Enhanced SRTLA Bonding

Custom optimizations for maximum stream stability. Our SRTLA relays deliver superior reliability and performance.

### Drop Protection

Never lose your audience. Automatic BRB scene switching when your connection drops, keeping viewers engaged until you reconnect.

### Wide Compatibility

Works with Moblin, Belabox, IRLBox, LiveU Solo and Solo Pro, IRL Pro, Larix and more.

### Automatic Scene Switching

With NOALBS, detect low bitrate and disconnects to automatically switch to a BRB scene.

### No Data Caps

Stream as long as you like. We never meter your transfer or bill for overage. The only ceiling is the 20 Mb/s input bitrate.

### Easy Setup

One-click setup for most streaming apps. Guides available for manual configuration.

### Manage From Anywhere

Control, customize and monitor your streaming endpoints from our dashboard.

### Protocol Support

We support RTMP, SRTLA, SRT and RTMPS protocols.

## Ready to Go Live?

Stream from anywhere with our global infrastructure. Ultra-low latency, maximum reliability.

![FI](https://cdn.jsdelivr.net/gh/umidbekk/react-flag-kit@1/assets/FI.svg)

### Helsinki, Finland

Helsinki

Northern European location providing excellent connectivity to Scandinavia and the Baltic region.

Supported Protocols

RTMP SRTLA SRT

![NO](https://cdn.jsdelivr.net/gh/umidbekk/react-flag-kit@1/assets/NO.svg)

### Sandefjord, Norway

Sandefjord

Strategic Norwegian location offering optimal performance for Northern European streaming.

Supported Protocols

RTMP SRTLA SRT

![US](https://cdn.jsdelivr.net/gh/umidbekk/react-flag-kit@1/assets/US.svg)

### Chicago, USA

Illinois

Central US location ensuring low latency and high reliability for North American streams.

Supported Protocols

RTMP SRTLA SRT

![US](https://cdn.jsdelivr.net/gh/umidbekk/react-flag-kit@1/assets/US.svg)

### Hillsboro, USA

Oregon

West Coast US location providing excellent connectivity for Pacific region streaming.

Supported Protocols

RTMP SRTLA SRT

![SG](https://cdn.jsdelivr.net/gh/umidbekk/react-flag-kit@1/assets/SG.svg)

### Singapore, Singapore

Southeast Asia

Southeast Asian location providing low latency connectivity for the Asia-Pacific region.

Supported Protocols

RTMP SRTLA SRT

[Start Streaming](https://irlserver.com/dashboard) [View Pricing](#pricing)

## CHOOSE YOUR PLAN

Simple pricing for professional streaming

POPULAR

### STANDARD

$9.99 /mo

RTMP, SRT & SRTLA relay endpoint

Custom SRTLA optimizations

Max input bitrate: 20Mb/s

Max resolution: Uncapped

Drop protection with NOALBS

No data caps or overage fees

Bring your own OBS, Streamlabs or vMix

IRLServer is a relay. You bring your own OBS (or Streamlabs, vMix) to receive your stream and go live to Twitch, YouTube or Kick.

[GET STARTED](https://irl.ac/)

### CUSTOM SOLUTIONS

Contact us

Need something special? We build custom IRL solutions for all kinds of streamers.

Custom IRL backpack setup

Multiple relay endpoints

Belabox®-compatible remote

Scene switching automation

Custom software development

White-label dashboard

[GET IN TOUCH](https://irlserver.com/discord)

ALL PLANS INCLUDE 24/7 SUPPORT • CANCEL ANYTIME

IRLControl

## REMOTE CONTROL

Control OBS and Moblin from any device. Switch scenes, manage audio, toggle sources, and hand your mods a panel of their own. All from your browser, free with your IRLServer account.

[Open IRLControl](https://irlcontrol.com/)

### OBS, fully remote

Switch scenes, ride the audio mixer, toggle sources, and start or stop recording. Every OBS control, from your phone.

### Moblin in your pocket

Drive your Moblin rig live. Zoom, scenes, mics, filters, reactions, SRT priorities, and gimbal presets.

### Hand your mods the board

Generate a password-protected share link per rig. Your team gets a stripped-down panel with only the controls they need.

### Real-time, nothing to install

WebSocket relay with auto-reconnect. No extra software on your rig, works on any device with a browser.

## FREQUENTLY ASKED QUESTIONS

What is a stream relay endpoint?

Do I need OBS or other software?

How do I set this up?

Which encoders and apps do you support?

What protocols do you support?

I want to stream from multiple cameras/drones

What happens when my connection drops?

Can I control my Belabox remotely?

How quickly can I get started?

---

Source: https://irlserver.com/llms-full.txt

\# IRLServer — full site content > IRLServer runs RTMP, SRT and SRTLA relay endpoints for IRL streamers: your encoder sends to a relay near you, the relay forwards to the streaming software you already run, and your stream survives the moment a mobile uplink does not. This file is the complete text of 15 pages, converted from https://irlserver.com. The index with one-line summaries is at https://irlserver.com/llms.txt. Source: https://irlserver.com # Your signal drops. Your stream doesn't. Professional stream relay with automatic scene switching, drop protection, and global coverage. \[Explore Features\](#features) \[View Pricing$9.99\](#pricing) No Data Caps Global Servers RTMP, SRT & SRTLA Works with the gear you already own - BELABOX - MOBLIN - IRL PRO - LIVEU - IRLBOX - LARIX - OBS - SRTLA - SRT - RTMP - RTMPS What you actually get ## One screen. Every endpoint. Each endpoint you own, the protocols it speaks, and the stream details to paste into your encoder — behind a copy button, not a support ticket. Add one, move it to another region, or share it with a co-streamer from the same place. !\[The IRLServer dashboard: a live stream at 8.2 Mbps with its bandwidth graph, endpoint slots in use, and a relay endpoint with the protocols it accepts.\](/\_next/image?url=%2Fimg%2Fdashboard.png&w=3840&q=75&dpl=dpl\_Gk9qPULqTp72ajXnUbe9fy8fHN3k) \[See how the stream reaches OBS →\](https://irlserver.com/guides/obs-setup) ## TRUSTED BY STREAMERS WORLDWIDE \[ !\[Mystixx\](https://static-cdn.jtvnw.net/jtv\_user\_pictures/b64ab5ec-75d9-4382-bb58-f9fef5968853-profile\_image-600x600.png) Mystixx PARTNER 36.3K LIVE \](https://www.twitch.tv/mystixx)\[ !\[Detoo\](https://static-cdn.jtvnw.net/jtv\_user\_pictures/48c42865-4686-41fc-bc49-d2526b6d9140-profile\_image-600x600.png) Detoo PARTNER 87.6K \](https://www.twitch.tv/detoo)\[ !\[Melkepakken\](https://static-cdn.jtvnw.net/jtv\_user\_pictures/38080fe4-cf2c-47f1-9917-5090dcd75f27-profile\_image-600x600.png) Melkepakken AFFILIATE 1.7K \](https://www.twitch.tv/melkepakken)\[ !\[Skiben\](https://static-cdn.jtvnw.net/jtv\_user\_pictures/ec542cdf-1fee-4be9-8ed1-7e27b742e704-profile\_image-600x600.png) Skiben PARTNER 8.6K LIVE \](https://www.twitch.tv/skiben)\[ !\[Jenserkongen\](https://static-cdn.jtvnw.net/jtv\_user\_pictures/f2614bf3-1614-4f94-b5bb-8ef37d54bc0a-profile\_image-600x600.png) Jenserkongen AFFILIATE 7.1K \](https://www.twitch.tv/jenserkongen)\[ !\[Danniz\](https://static-cdn.jtvnw.net/jtv\_user\_pictures/0f3b5303-c694-4b6e-ad85-eed283e36514-profile\_image-600x600.png) Danniz PARTNER 44.4K LIVE \](https://www.twitch.tv/danniz)\[ !\[Mystixx\](https://static-cdn.jtvnw.net/jtv\_user\_pictures/b64ab5ec-75d9-4382-bb58-f9fef5968853-profile\_image-600x600.png) Mystixx PARTNER 36.3K LIVE \](https://www.twitch.tv/mystixx)\[ !\[Detoo\](https://static-cdn.jtvnw.net/jtv\_user\_pictures/48c42865-4686-41fc-bc49-d2526b6d9140-profile\_image-600x600.png) Detoo PARTNER 87.6K \](https://www.twitch.tv/detoo)\[ !\[Melkepakken\](https://static-cdn.jtvnw.net/jtv\_user\_pictures/38080fe4-cf2c-47f1-9917-5090dcd75f27-profile\_image-600x600.png) Melkepakken AFFILIATE 1.7K \](https://www.twitch.tv/melkepakken)\[ !\[Skiben\](https://static-cdn.jtvnw.net/jtv\_user\_pictures/ec542cdf-1fee-4be9-8ed1-7e27b742e704-profile\_image-600x600.png) Skiben PARTNER 8.6K LIVE \](https://www.twitch.tv/skiben)\[ !\[Jenserkongen\](https://static-cdn.jtvnw.net/jtv\_user\_pictures/f2614bf3-1614-4f94-b5bb-8ef37d54bc0a-profile\_image-600x600.png) Jenserkongen AFFILIATE 7.1K \](https://www.twitch.tv/jenserkongen)\[ !\[Danniz\](https://static-cdn.jtvnw.net/jtv\_user\_pictures/0f3b5303-c694-4b6e-ad85-eed283e36514-profile\_image-600x600.png) Danniz PARTNER 44.4K LIVE \](https://www.twitch.tv/danniz)\[ !\[Mystixx\](https://static-cdn.jtvnw.net/jtv\_user\_pictures/b64ab5ec-75d9-4382-bb58-f9fef5968853-profile\_image-600x600.png) Mystixx PARTNER 36.3K LIVE \](https://www.twitch.tv/mystixx)\[ !\[Detoo\](https://static-cdn.jtvnw.net/jtv\_user\_pictures/48c42865-4686-41fc-bc49-d2526b6d9140-profile\_image-600x600.png) Detoo PARTNER 87.6K \](https://www.twitch.tv/detoo)\[ !\[Melkepakken\](https://static-cdn.jtvnw.net/jtv\_user\_pictures/38080fe4-cf2c-47f1-9917-5090dcd75f27-profile\_image-600x600.png) Melkepakken AFFILIATE 1.7K \](https://www.twitch.tv/melkepakken)\[ !\[Skiben\](https://static-cdn.jtvnw.net/jtv\_user\_pictures/ec542cdf-1fee-4be9-8ed1-7e27b742e704-profile\_image-600x600.png) Skiben PARTNER 8.6K LIVE \](https://www.twitch.tv/skiben)\[ !\[Jenserkongen\](https://static-cdn.jtvnw.net/jtv\_user\_pictures/f2614bf3-1614-4f94-b5bb-8ef37d54bc0a-profile\_image-600x600.png) Jenserkongen AFFILIATE 7.1K \](https://www.twitch.tv/jenserkongen)\[ !\[Danniz\](https://static-cdn.jtvnw.net/jtv\_user\_pictures/0f3b5303-c694-4b6e-ad85-eed283e36514-profile\_image-600x600.png) Danniz PARTNER 44.4K LIVE \](https://www.twitch.tv/danniz) ### What our users say "IRLServer is a great choice for streaming. The setup process is straightforward, the pricing is reasonable, and customer service is highly responsive. You can stream with good quality using either your phone or a backpack." !\[Mystixx\](https://static-cdn.jtvnw.net/jtv\_user\_pictures/b64ab5ec-75d9-4382-bb58-f9fef5968853-profile\_image-600x600.png) Mystixx PARTNER 36.3K followers 740K Followers reached 100+ Streamers 99.9% Uptime 24/7 Support ## BUILT FOR IRL RTMP, SRT and SRTLA relay endpoints with custom optimizations for professional IRL streaming. ### Enhanced SRTLA Bonding Custom optimizations for maximum stream stability. Our SRTLA relays deliver superior reliability and performance. ### Drop Protection Never lose your audience. Automatic BRB scene switching when your connection drops, keeping viewers engaged until you reconnect. ### Wide Compatibility Works with Moblin, Belabox, IRLBox, LiveU Solo and Solo Pro, IRL Pro, Larix and more. ### Automatic Scene Switching With NOALBS, detect low bitrate and disconnects to automatically switch to a BRB scene. ### No Data Caps Stream as long as you like. We never meter your transfer or bill for overage. The only ceiling is the 20 Mb/s input bitrate. ### Easy Setup One-click setup for most streaming apps. Guides available for manual configuration. ### Manage From Anywhere Control, customize and monitor your streaming endpoints from our dashboard. ### Protocol Support We support RTMP, SRTLA, SRT and RTMPS protocols. ## Ready to Go Live? Stream from anywhere with our global infrastructure. Ultra-low latency, maximum reliability. !\[FI\](https://cdn.jsdelivr.net/gh/umidbekk/react-flag-kit@1/assets/FI.svg) ### Helsinki, Finland Helsinki Northern European location providing excellent connectivity to Scandinavia and the Baltic region. Supported Protocols RTMP SRTLA SRT !\[NO\](https://cdn.jsdelivr.net/gh/umidbekk/react-flag-kit@1/assets/NO.svg) ### Sandefjord, Norway Sandefjord Strategic Norwegian location offering optimal performance for Northern European streaming. Supported Protocols RTMP SRTLA SRT !\[US\](https://cdn.jsdelivr.net/gh/umidbekk/react-flag-kit@1/assets/US.svg) ### Chicago, USA Illinois Central US location ensuring low latency and high reliability for North American streams. Supported Protocols RTMP SRTLA SRT !\[US\](https://cdn.jsdelivr.net/gh/umidbekk/react-flag-kit@1/assets/US.svg) ### Hillsboro, USA Oregon West Coast US location providing excellent connectivity for Pacific region streaming. Supported Protocols RTMP SRTLA SRT !\[SG\](https://cdn.jsdelivr.net/gh/umidbekk/react-flag-kit@1/assets/SG.svg) ### Singapore, Singapore Southeast Asia Southeast Asian location providing low latency connectivity for the Asia-Pacific region. Supported Protocols RTMP SRTLA SRT \[Start Streaming\](https://irlserver.com/dashboard) \[View Pricing\](#pricing) ## CHOOSE YOUR PLAN Simple pricing for professional streaming POPULAR ### STANDARD $9.99 /mo RTMP, SRT & SRTLA relay endpoint Custom SRTLA optimizations Max input bitrate: 20Mb/s Max resolution: Uncapped Drop protection with NOALBS No data caps or overage fees Bring your own OBS, Streamlabs or vMix IRLServer is a relay. You bring your own OBS (or Streamlabs, vMix) to receive your stream and go live to Twitch, YouTube or Kick. \[GET STARTED\](https://irl.ac/) ### CUSTOM SOLUTIONS Contact us Need something special? We build custom IRL solutions for all kinds of streamers. Custom IRL backpack setup Multiple relay endpoints Belabox®-compatible remote Scene switching automation Custom software development White-label dashboard \[GET IN TOUCH\](https://irlserver.com/discord) ALL PLANS INCLUDE 24/7 SUPPORT • CANCEL ANYTIME IRLControl ## REMOTE CONTROL Control OBS and Moblin from any device. Switch scenes, manage audio, toggle sources, and hand your mods a panel of their own. All from your browser, free with your IRLServer account. \[Open IRLControl\](https://irlcontrol.com/) ### OBS, fully remote Switch scenes, ride the audio mixer, toggle sources, and start or stop recording. Every OBS control, from your phone. ### Moblin in your pocket Drive your Moblin rig live. Zoom, scenes, mics, filters, reactions, SRT priorities, and gimbal presets. ### Hand your mods the board Generate a password-protected share link per rig. Your team gets a stripped-down panel with only the controls they need. ### Real-time, nothing to install WebSocket relay with auto-reconnect. No extra software on your rig, works on any device with a browser. ## FREQUENTLY ASKED QUESTIONS What is a stream relay endpoint? Do I need OBS or other software? How do I set this up? Which encoders and apps do you support? What protocols do you support? I want to stream from multiple cameras/drones What happens when my connection drops? Can I control my Belabox remotely? How quickly can I get started? --- Source: https://irlserver.com/compare # RELAY PROVIDER COMPARISON See how IRLServer compares to other cloud streaming solutions. We focus on reliability, features, and value for IRL streamers. ## Why Choose IRLServer? ### Custom SRTLA Optimizations Our SRTLA implementation includes in-house optimizations for better reliability and performance compared to standard implementations. ### Many Protocols Available RTMP, RTMPS, SRT, and SRTLA - all protocols available. Choose what fits your needs. ### Global Server Network Strategically positioned servers in EU and US for low-latency streaming from anywhere in the world. ### No Data Caps We do not meter your transfer or charge for overage. One flat price, however long you stream, with a 20 Mb/s input bitrate. ## Feature Comparison | Feature | IRLServer | Typical Competitor | | --- | --- | --- | | Protocols | | | | SRTLA Support | Yes | Varies | | SRT Support | Yes | Most | | RTMP Support | Yes | All | | RTMPS (Secure) | Yes | Some | | Features | | | | Drop Protection (NOALBS compatible) | Yes | Most | | No Data Caps | Yes | Some | | Max Input Bitrate | 20 Mb/s | Tiered | | Custom SRTLA Optimizations | Yes | Rare | | Belabox-compatible Remote | Yes | Rare | | Stats API for NOALBS | Yes | Most | | Server Coverage | | | | EU Servers | Yes | Most | | US Servers | Yes | Most | | Support | | | | Discord Community | Yes | Most | | Setup Guides | Yes | Some | | Free Tools (Calculator, Config Gen) | Yes | Few | ## Simple, Transparent Pricing ### What's Included - All protocols (RTMP, RTMPS, SRT, SRTLA) - No data caps - Multiple endpoints - Stats API for NOALBS - Discord support ### No Hidden Fees - No bandwidth overage charges - No setup fees - No long-term contracts - Cancel anytime \[View Pricing\](https://irlserver.com/pricing) ## Ready to Get Started? Join thousands of IRL streamers who trust IRLServer for their cloud streaming needs. \[Start Streaming\](https://irl.ac/) \[View Setup Guides\](https://irlserver.com/guides) --- Source: https://irlserver.com/features # IRL Streaming Features - SRTLA, Drop Protection, Global Servers | IRLServer ## BUILT FOR IRL RTMP, SRT and SRTLA relay endpoints with custom optimizations for professional IRL streaming. ### Enhanced SRTLA Bonding Custom optimizations for maximum stream stability. Our SRTLA relays deliver superior reliability and performance. ### Drop Protection Never lose your audience. Automatic BRB scene switching when your connection drops, keeping viewers engaged until you reconnect. ### Wide Compatibility Works with Moblin, Belabox, IRLBox, LiveU Solo and Solo Pro, IRL Pro, Larix and more. ### Automatic Scene Switching With NOALBS, detect low bitrate and disconnects to automatically switch to a BRB scene. ### No Data Caps Stream as long as you like. We never meter your transfer or bill for overage. The only ceiling is the 20 Mb/s input bitrate. ### Easy Setup One-click setup for most streaming apps. Guides available for manual configuration. ### Manage From Anywhere Control, customize and monitor your streaming endpoints from our dashboard. ### Protocol Support We support RTMP, SRTLA, SRT and RTMPS protocols. --- Source: https://irlserver.com/guides # SETUP GUIDES Step-by-step tutorials to get your IRL stream up and running. From basic OBS setup to advanced encoder configuration. Get started \[ Get started ### SRTLA Bonding Explained: Stream IRL Without Dropping What SRTLA bonding is, how it holds your IRL stream together across multiple modems, and why a custom optimized relay beats the basic open source version. SRTLA Bonding Relay 7 min read \](https://irlserver.com/guides/srtla-bonding)\[ Get started ### The Best IRL Streaming Setup for Twitch and Kick in 2026 A complete, reliable IRL streaming setup for Twitch and Kick: phone or encoder, SRTLA bonding, a relay, your own OBS, and NOALBS scene switching, explained end to end. Twitch Kick SRTLA 8 min read \](https://irlserver.com/guides/best-irl-streaming-setup-twitch-kick) Stage \[ Stage ### How to IRL Stream Without a PC at Home Every other setup assumes a PC running OBS while you are out. If you do not have one, here is the path that does the compositing in the cloud instead. Stage No PC Phone only 6 min read \](https://irlserver.com/guides/irl-stream-without-a-pc)\[ Stage ### How to Multistream to Twitch, Kick and YouTube at Once Multistreaming an IRL feed comes down to which machine makes the copies: your own OBS at home, or a compositor in the cloud. What each one costs you. Stage Multistreaming Twitch 6 min read \](https://irlserver.com/guides/multistream-twitch-kick-youtube) Protocols \[ Protocols ### SRT Latency Settings for IRL Streaming: What to Set and Why What the SRT latency number actually does, why 2000 to 3000 ms is the right starting point for cellular and bonded rigs, how to read freezes vs bitrate drops, and why a lower number rarely makes your stream feel faster. SRT SRTLA Latency 7 min read \](https://irlserver.com/guides/srt-latency-settings-irl-streaming)\[ Protocols ### SRTLA vs RTMP for IRL Streaming: Which Protocol to Use How SRTLA, SRT, and RTMP differ for IRL streaming: recovery, bonding, latency, and when each one is actually the right call. SRTLA RTMP SRT 6 min read \](https://irlserver.com/guides/srtla-vs-rtmp) Reliability \[ Reliability ### NOALBS Scene Switching Automatic scene switching based on bitrate. Switch between LIVE, LOW, and BRB scenes when connection quality changes. NOALBS Automation 15 min \](https://irlserver.com/guides/noalbs)\[ Reliability ### How to Keep Your IRL Stream Live When the Signal Drops A field tested setup that stops your Twitch or Kick stream from ending when phone signal dies: SRTLA bonding, the relay as a source in your own OBS, and NOALBS auto scene switching. Drop protection SRTLA NOALBS 9 min read \](https://irlserver.com/guides/keep-stream-live-when-signal-drops)\[ Reliability ### How to Stop Your Stream From Ending on Twitch and Kick Why Twitch and Kick end an IRL broadcast when your connection drops, and the setup that keeps the session alive: your own OBS broadcasting through a relay with NOALBS. Twitch Kick Drop protection 6 min read \](https://irlserver.com/guides/stop-streams-ending-twitch-kick)\[ Reliability ### Why Mobile Signal Gets Bad While You Stream (and How to Fix It) The real reasons cellular signal drops during an IRL stream: congestion, tower handoffs, crowds, and weak uploads, plus the setup that keeps you live anyway. Connectivity SRTLA Bonding 6 min read \](https://irlserver.com/guides/why-mobile-signal-drops-irl) Encoders \[ Encoders ### Hardware Encoders Configure Belabox, LiveU Solo, and IRLBox. Set up SRT and SRTLA streaming with your relay endpoint. Belabox LiveU 12 min \](https://irlserver.com/guides/encoders)\[ Encoders ### How to Connect a LiveU Solo Pro to Your Relay over SRT Set up an SRT custom destination for a LiveU Solo Pro, pick the right latency, and use HEVC to get more picture out of the same bonded uplink. LiveU SRT HEVC 6 min read \](https://irlserver.com/guides/connect-liveu-solo-pro)\[ Encoders ### How to Connect an IRLBox to Your Relay Send an IRLBox feed to an SRT or RTMP relay endpoint, get it into your own OBS, and understand where IRLBox's own RIST bonding fits. IRLBox SRT RTMP 6 min read \](https://irlserver.com/guides/connect-irlbox)\[ Encoders ### How to Connect Belabox to Your Relay (with Remote Control) Connect a Belabox to an SRTLA relay step by step, and remote control the box while you are live. The custom remote control most providers cannot offer. Belabox SRTLA Remote control 6 min read \](https://irlserver.com/guides/connect-belabox)\[ Encoders ### How to Connect LiveU Solo and Solo Pro to Your Relay Connect a LiveU Solo (RTMP) or Solo Pro (SRT) to an IRLServer relay. LiveU bonds with its own LRT layer, then sends a single stream to your relay and OBS. LiveU SRT RTMP 6 min read \](https://irlserver.com/guides/connect-liveu)\[ Encoders ### How to Stream from a DJI Osmo Pocket to Your Relay over RTMP Send a DJI Osmo Pocket 3 or Pocket 4 straight to an RTMP relay endpoint using the DJI Mimo app, then pull the feed into your own OBS. DJI RTMP Phone 6 min read \](https://irlserver.com/guides/connect-dji-osmo-pocket) Phone streaming \[ Phone streaming ### Mobile Streaming Apps Setup guides for Moblin, IRL Pro, and Larix Broadcaster with SRTLA bonding for reliable mobile streaming on iOS and Android. SRTLA Mobile 8 min \](https://irlserver.com/guides/mobile-streaming)\[ Phone streaming ### How to Connect IRL Pro to Your Relay (Android SRTLA Setup) Point IRL Pro on Android at an SRTLA relay step by step: protocol, server, port, and stream id, plus bonding multiple connections for a stable IRL stream. IRL Pro Android SRTLA 5 min read \](https://irlserver.com/guides/connect-irl-pro)\[ Phone streaming ### How to Connect Moblin to Your Relay (iPhone SRTLA Setup) Point Moblin on iPhone at an SRTLA relay step by step: protocol, server, port, and stream id, plus bonding multiple connections for a stable IRL stream. Moblin iPhone SRTLA 5 min read \](https://irlserver.com/guides/connect-moblin)\[ Phone streaming ### How to Go Live IRL From Your Android Phone in 2026 Everything you need to IRL stream from Android: the right app (IRL Pro), bonded connections, a relay, and your own OBS, so your stream holds when you move. Android IRL Pro SRTLA 6 min read \](https://irlserver.com/guides/go-live-from-android)\[ Phone streaming ### How to Go Live IRL From Your iPhone in 2026 Everything you need to IRL stream from an iPhone: the right app (Moblin), bonded connections, a relay, and your own OBS, so your stream holds when you move. iPhone Moblin SRTLA 6 min read \](https://irlserver.com/guides/go-live-from-iphone)\[ Phone streaming ### How to Use a DJI Camera with Moblin for Bonded IRL Streaming Pair a DJI Osmo Pocket or Osmo Action to Moblin over Bluetooth, let Moblin receive it on its own RTMP server, and send the result to an SRTLA relay so the feed bonds across cellular and WiFi. DJI Moblin SRTLA 7 min read \](https://irlserver.com/guides/dji-through-moblin) OBS \[ OBS ### OBS Studio Setup Configure OBS Studio for IRL streaming with relay endpoints: media source setup, scene creation, and network buffering. OBS Beginner 10 min \](https://irlserver.com/guides/obs-setup) Collab \[ Collab ### How to Share Your IRL Feed With Other Streamers (Play Keys) Co-stream your IRL feed with other creators using play keys. Generate a named, shareable player key per streamer, all pulling from your single publisher feed. Collab Play keys OBS 5 min read \](https://irlserver.com/guides/share-your-feed-with-other-streamers) Need more help? \[Join Discord\](https://irlserver.com/discord) \[Free Tools\](https://irlserver.com/tools) \[Use Cases\](https://irlserver.com/use-cases) --- Source: https://irlserver.com/guides/encoders Hardware 12 min read # Hardware Encoder Setup Guide Configure hardware encoders for professional IRL streaming. Learn how to set up Belabox, LiveU Solo, IRLBox, and other portable encoders with your relay endpoint. ## Why Use a Hardware Encoder? ### Better Battery Life Dedicated encoders don't drain your phone battery ### Multi-SIM Bonding Bond 4+ cellular connections for maximum reliability ### HDMI Input Use any camera with HDMI output for better quality ## Belabox ### Belabox SRTLA Open-source software for Orange Pi 5 Plus, Radxa Rock 5A/5B, and Jetson Nano. Supports multi-modem SRTLA bonding for reliable mobile streaming. SRTLA Bonding Multi-modem Open Source 4G/5G Support #### Configuration SRTLA receiver address \`srt.region.irl.ac\` SRTLA receiver port \`5000\` SRT Stream ID \`live/stream/YOUR\_KEY\` #### Setup Steps 1. Access Belabox web interface (usually at 192.168.x.x) 2. Navigate to "SRTLA Settings" 3. If given the choice for SRTLA relay server, choose "CUSTOM" 4. Enter your SRTLA receiver address, port and SRT streamid from your dashboard 5. Configure your modems in the Network section 6. Start streaming Use the IRLServer \[Belabox-compatible remote control\](https://remote.irl.ac/) to manage your Belabox from anywhere. ## LiveU Solo Pro ### LiveU Solo Pro SRT Professional portable encoder with reliable low-latency delivery. Supports SRT protocol. SRT Professional Grade Built-in Battery Easy Setup #### SRT Configuration SRT URL \`srt://srt.region.irl.ac:4001\` Stream ID \`live/stream/YOUR\_KEY\` Latency \`2500ms (recommended)\` #### Setup Steps 1. Log in to your LiveU Solo Portal 2. Navigate to Destinations → Custom SRT 3. Enter the SRT URL with your stream ID 4. Set latency to 2500ms for optimal stability 5. Save and assign to your unit LiveU Solo Pro connects via SRT to your relay endpoint. LiveU handles bonding with its own LRT layer, and you still get the benefits of our relay. ## LiveU (RTMP) ### LiveU RTMP Standard LiveU encoders using RTMP protocol for streaming to relay endpoints. RTMP Professional Reliable Easy Config #### RTMP Configuration Server URL \`rtmp://rtmp.region.irl.ac:1935/publish\` Stream Key \`YOUR\_KEY\` #### Setup Steps 1. Access LiveU Central portal 2. Create a Custom RTMP destination 3. Enter the server URL and stream key 4. Assign to your encoder unit ## IRLBox ### IRLBox SRT / RTMP / RIST Portable IRL streaming encoder supporting both SRT and RTMP protocols. SRT RTMP RIST Portable Multi-modem Budget-friendly #### SRT Configuration Server URL \`srt.region.irl.ac\` Port \`4001\` Stream ID \`live/stream/YOUR\_KEY\` Latency \`2500ms (recommended)\` #### RTMP Configuration (Alternative) Server URL \`rtmp://rtmp.region.irl.ac:1935/publish\` Stream Key \`YOUR\_KEY\` SRTLA is recommended over RTMP for mobile streaming as it provides better reliability with connection bonding. ## General Tips for Hardware Encoders \*\*Latency Setting:\*\* Start with 2500ms latency for SRTLA/SRT. You can lower it to 2000ms for less delay if your connection is stable. \*\*Bitrate:\*\* Most hardware encoders work well at 4000-6000 kbps for 1080p. Don't go too high - it wastes data and doesn't improve quality much. \*\*Heat Management:\*\* Hardware encoders can get hot during extended streams. Ensure good ventilation in your backpack. \*\*Power:\*\* Use a quality power bank with USB-PD or 12V output. Cheap power banks can cause encoder instability. ## Encoder Comparison | Encoder | Protocol | Bonding | Price Range | | --- | --- | --- | --- | | Belabox | SRTLA | Yes (up to 8 modems) | $200-400 (DIY) | | LiveU Solo | RTMP | With expensive LRT Subscription | $1,500+ | | LiveU Solo Pro | SRT | With expensive LRT Subscription | $1,500+ | ## Next Steps \[ ### OBS Setup Guide Configure OBS to receive your stream \](https://irlserver.com/guides/obs-setup)\[ ### NOALBS Setup Automatic scene switching \](https://irlserver.com/guides/noalbs)\[ ### Mobile Streaming Guide Stream from your phone with SRTLA \](https://irlserver.com/guides/mobile-streaming)\[ ### Bitrate Calculator Calculate optimal stream settings \](https://irlserver.com/tools/bitrate-calculator) --- Source: https://irlserver.com/guides/mobile-streaming Mobile 8 min read # Mobile Streaming Apps Guide Setup guides for the best mobile streaming apps. Configure SRTLA bonding for reliable streaming over cellular networks with automatic failover. ## Why SRTLA for Mobile Streaming? SRTLA (SRT with Link Aggregation) bonds multiple cellular connections together for maximum reliability. This means: - \*\*Connection Redundancy:\*\* If one network connection loses signal, others keep the stream alive - \*\*Higher Bitrate:\*\* Combine bandwidth from multiple connections - \*\*Better in Crowds:\*\* Different carriers handle congestion differently ## Moblin (iOS) ### Moblin iOS (iPhone, iPad) SRTLA SRT RTMP 4K 60fps H.265/HEVC Chat Integration Twitch Kick Moblin is the most popular iOS streaming app for IRL streamers. It supports SRTLA bonding, allowing you to use multiple cellular connections simultaneously. #### Quick Setup 1. Download Moblin from the \[App Store\](https://apps.apple.com/us/app/moblin/id6466745933) 2. Open Settings → Stream → Add new stream 3. Select "SRTLA" as the protocol 4. Enter your server details from the IRLServer dashboard #### Connection Settings Server: \`srt.region.irl.ac\` Port: \`5000\` Stream ID: \`live/stream/YOUR\_KEY\` Use "SRTLA" to bond multiple connections. Enable WiFi and cellular simultaneously for best results. You can use the network connection of other iPhones and Android phones. Use the Moblink feature (Moblin iOS) or download the \[Moblink app (Android)\](https://play.google.com/store/apps/details?id=com.eerimoq.moblink). ## IRL Pro (Android) ### IRL Pro Android SRTLA SRT RTMP Multi-connection H.264/H.265 IRL Pro is a professional streaming app for Android with SRTLA bonding support. It allows multi-connection redundancy for reliable mobile streaming. #### Quick Setup 1. Download IRL Pro from the \[Play Store\](https://play.google.com/store/apps/details?id=app.irlpro.android) 2. Go to Settings → Stream Settings 3. Add a new SRTLA destination 4. Enter your IRLServer endpoint details #### Connection Settings Server URL: \`srt.region.irl.ac\` Port: \`5000\` Stream ID: \`live/stream/YOUR\_KEY\` IRL Pro supports multiple network interfaces. Enable WiFi and mobile data simultaneously for bonded connections. ## Larix Broadcaster (iOS & Android) ### Larix Broadcaster iOS & Android SRT RTMP RIST NDI H.264/HEVC Multi-camera Larix Broadcaster is a professional streaming camera app available on both iOS and Android. It supports SRT and RTMP protocols with advanced encoding options. #### Quick Setup 1. Download Larix from \[softvelum.com\](https://softvelum.com/larix/) 2. Open Settings → Connections → New connection 3. Select SRT as the protocol 4. Configure with your IRLServer SRT URL #### SRT URL Format \`srt://srt.region.irl.ac:4001?streamid=live/stream/YOUR\_KEY&latency=2000000\` Larix supports SRT but not SRTLA bonding. For multi-SIM bonding, use Moblin (iOS) or IRL Pro (Android) instead. ## Recommended Encoding Settings | Setting | 4G/LTE | 5G | | --- | --- | --- | | Resolution | 1080p | 1080p / 1440p | | Frame Rate | 30 fps | 30-60 fps | | Bitrate | 3000-5000 kbps | 5000-8000 kbps | | Codec | H.264 / H.265 | H.265 (HEVC) | | Keyframe | 2 seconds | 2 seconds | ## Pro Tips for Mobile Streaming \*\*Battery Management:\*\* Enable battery saver mode for background apps. Use a power bank - streaming at 1080p can drain your battery in 2-3 hours. \*\*Data Usage:\*\* At 5000 kbps, you'll use about 2.2 GB per hour. Use our \[bitrate calculator\](https://irlserver.com/tools/bitrate-calculator) to plan your data needs. \*\*Heat Management:\*\* Phones can throttle when hot. Remove your case and avoid direct sunlight during long streams. \*\*Network Priority:\*\* Disable WiFi if you're only using cellular, or your phone may try to switch networks and cause drops. ## Next Steps \[ ### OBS Setup Guide Configure OBS to receive your stream \](https://irlserver.com/guides/obs-setup)\[ ### NOALBS Setup Automatic scene switching \](https://irlserver.com/guides/noalbs)\[ ### Bitrate Calculator Calculate optimal stream settings \](https://irlserver.com/tools/bitrate-calculator) --- Source: https://irlserver.com/guides/obs-setup Beginner 10 min read # OBS Studio Setup Guide Learn how to configure OBS Studio to receive your IRL stream from a relay endpoint. This guide covers both basic setup for beginners and advanced NOALBS configuration for automatic scene switching. ## Prerequisites - \[OBS Studio\](https://obsproject.com/download) installed (version 28.0 or later recommended) - An IRLServer account with an active endpoint (get one at \[irl.ac\](https://irl.ac/)) - Your stream URL from the dashboard (RTMP or SRT/SRTLA) ## Choose Your Setup ### Simplified Setup Just one LIVE scene. Best for beginners who want to get started quickly without automatic scene switching. Recommended for beginners ### Advanced Setup (NOALBS) Multiple scenes (LIVE, LOW, BRB, REFRESH) with automatic switching when your connection drops or has low bitrate. Recommended for regular streamers ## Step-by-Step Setup 1 ### Launch OBS Studio Open OBS Studio on your computer. If this is your first time, complete the auto-configuration wizard or click Cancel to set up manually. 2 ### Create Your Scenes For simplified setup, create one scene: - \`LIVE\` \\- Your main streaming scene For NOALBS setup, create these scenes: - \`LIVE\` \\- Main stream view - \`LOW\` \\- Low bitrate warning scene - \`BRB\` \\- Disconnected/be right back scene - \`REFRESH\` \\- Connection refresh scene Right-click in the Scenes panel → Add Scene. Use EXACT names (case sensitive) for NOALBS compatibility. 3 ### Add Media Source In your LIVE scene, add a Media Source: 1. Right-click in Sources panel → Add → Media Source 2. Name it something like "IRL Feed" or "Stream Input" 3. Uncheck "Local File" 4. Check "Show nothing when playback ends" 5. Check "Restart playback when source becomes active" 6. Check "Close file when inactive" 4 ### Configure Your Stream URL In the Media Source properties, paste your stream URL from the IRLServer dashboard. For RTMP endpoints: \`rtmp://rtmp.region.irl.ac/publish/YOUR\_KEY\` For SRT/SRTLA endpoints: \`srt://srt.region.irl.ac:4000?streamid=play/stream/YOUR\_KEY&latency=2000000\` Your actual stream URLs are available in your dashboard at \[irl.ac/dashboard/endpoints\](https://irl.ac/dashboard/endpoints) 5 ### Set Network Buffering Configure network buffering for stable playback. In the Media Source properties: - \*\*Network Buffering:\*\* 1 MB (recommended) or higher for unstable connections - \*\*Reconnect Delay:\*\* 3 seconds Higher buffer = more stable but more delay. Start with 1 MB and increase if you see stuttering. 6 ### Stretch to Screen Make the media source fill your canvas: 1. Right-click on the media source in the preview 2. Transform → Stretch to Screen Or press Ctrl+F with the source selected to fit to screen. 7 ### Copy to Other Scenes (NOALBS) If using NOALBS, copy your media source to other scenes: 1. Right-click your media source → Copy 2. Go to LOW scene → Right-click → Paste (Reference) 3. Repeat for REFRESH scene Using "Paste (Reference)" ensures all scenes use the same source. Changes to one will apply to all. 8 ### Test Your Setup Start streaming from your encoder (Belabox, Moblin, etc.) to your IRLServer endpoint. You should see your stream appear in OBS within a few seconds. If the stream doesn't appear, check that your encoder is connected and streaming to the correct URL. You can verify connection status in your IRLServer dashboard. ## Next Steps \[ ### Setup NOALBS Automatic scene switching \](https://irlserver.com/guides/noalbs)\[ ### NOALBS Config Generator Generate config.json \](https://irlserver.com/tools/noalbs-config)\[ ### Bitrate Calculator Calculate optimal stream settings \](https://irlserver.com/tools/bitrate-calculator)\[ ### Mobile Streaming Guide Stream from your phone with SRTLA \](https://irlserver.com/guides/mobile-streaming) ## Resources \[OBS Wiki\](https://obsproject.com/wiki/) \[IRLServer Discord\](https://irlserver.com/discord) --- Source: https://irlserver.com/imprint # Impressum Imprint / Legal Disclosure ## Angaben gemäß § 5 DDG LEKANGER SOLUTIONS Dalehaugen 2A 0657 Oslo Norwegen ## Inhaber Thomas Lekanger ## Kontakt E-Mail: \[mail@irlserver.com\](mailto:mail@irlserver.com) ## Registereintrag Eingetragen im norwegischen Unternehmensregister (Enhetsregisteret), geführt von den Brønnøysundregistrene. Organisationsnummer (Org.nr.): 934 927 230 ## Verantwortlich für den Inhalt nach § 18 Abs. 2 MStV Thomas Lekanger Anschrift wie oben ## Verbraucherstreitbeilegung Wir sind nicht bereit und nicht verpflichtet, an Streitbeilegungsverfahren vor einer Verbraucherschlichtungsstelle teilzunehmen. --- ## Information pursuant to § 5 DDG LEKANGER SOLUTIONS Dalehaugen 2A 0657 Oslo Norway ## Owner Thomas Lekanger ## Contact Email: \[mail@irlserver.com\](mailto:mail@irlserver.com) ## Company registration Registered in the Norwegian Register of Legal Entities (Enhetsregisteret), maintained by the Brønnøysund Register Centre. Organisation number (Org.nr.): 934 927 230 ## Responsible for content per § 18 (2) MStV Thomas Lekanger Address as above ## Consumer dispute resolution We are neither willing nor obliged to participate in dispute resolution proceedings before a consumer arbitration board. --- Source: https://irlserver.com/terms # Terms of Service Last updated: June 6, 2026 These Terms of Service (the "Terms") govern your access to and use of IRLServer, including our website at irlserver.com, the streaming relay service, and any related tools (together, the "Service"). The Service is operated by LEKANGER SOLUTIONS (organisation number 934 927 230), a sole proprietorship registered in Norway ("IRLServer", "we", "us", or "our"). Full provider details are available in our \[Imprint\](https://irlserver.com/imprint). By creating an account, subscribing, or otherwise using the Service, you agree to these Terms and to our \[Privacy Policy\](https://irlserver.com/privacy). If you do not agree, do not use the Service. ## 1\\. The Service IRLServer provides a streaming relay for live broadcasters. A paid subscription gives you a relay endpoint (RTMP, RTMPS, SRT, or SRTLA), access to our server regions, support for automatic scene switching via NOALBS, and a stats API for monitoring your stream. We may add, change, or remove features over time to improve or maintain the Service. ## 2\\. Eligibility and accounts You must be at least 16 years old to use the Service. If you are under 18, you may only use the Service with the consent of a parent or legal guardian, who must also authorise any payment method used. You are responsible for keeping your account credentials secure and for all activity that occurs under your account. You must provide accurate information and keep it up to date. Notify us promptly of any unauthorised use of your account. ## 3\\. Subscriptions and billing The relay service is offered on a recurring subscription basis. Payments are processed by Stripe; we do not store your full card details. By subscribing, you authorise us (through Stripe) to charge the applicable fee for each billing period until you cancel. Subscriptions renew automatically at the end of each billing period at the then-current price unless you cancel before the renewal date. You can upgrade or downgrade your plan at any time; changes take effect immediately and billing is prorated. Prices are shown inclusive of any applicable taxes where required. We may change our prices, but a price change will only apply to you from your next billing period, and we will give you reasonable notice before it takes effect. ## 4\\. Right of withdrawal and refunds If you are a consumer, you may request a full refund of your initial subscription payment within 14 days of your first purchase, for any reason. To exercise this right, contact us at \[mail@irlserver.com\](mailto:mail@irlserver.com) within the 14-day period. This 14-day money-back guarantee applies to your initial purchase only. Renewal payments for subsequent billing periods are non-refundable; to avoid a renewal charge, cancel before the renewal date. Nothing in this section limits any non-waivable rights you have under Norwegian or EU consumer law. ## 5\\. Cancellation and termination You may cancel your subscription at any time. Cancellation takes effect at the end of the current billing period, and you retain access to the paid Service until then. We may suspend or terminate your access to the Service, with or without notice, if you breach these Terms, if your use poses a risk to the Service or other users, or if we are required to do so by law. ## 6\\. Acceptable use You agree that you will not: - use the Service to transmit content that is illegal, or that infringes the intellectual property, privacy, or other rights of any third party; - relay content you do not have the rights to broadcast, or content that violates the terms of the platform you stream to (for example Twitch, YouTube, or Kick); - resell, sublicense, or share your relay endpoint with third parties, or use a single subscription for more concurrent streams than your plan permits; - attempt to disrupt, overload, reverse-engineer, or gain unauthorised access to the Service or its infrastructure; or - use the Service to send spam, malware, or otherwise harm others. ## 7\\. Your content and our role as host You retain all rights to the streams and other content you transmit through the Service ("Your Content"). IRLServer acts only as a technical relay and hosting provider for Your Content; we do not monitor, control, or claim ownership of what you stream, and you are solely responsible for it. As a hosting provider we are not liable for Your Content unless we have actual knowledge that specific content is illegal and fail to act. If you believe content transmitted through the Service is unlawful or infringing, contact us at \[mail@irlserver.com\](mailto:mail@irlserver.com) and we will review and, where appropriate, remove or disable access to it. ## 8\\. Intellectual property The Service, including the IRLServer name, logo, website content, and software, is owned by LEKANGER SOLUTIONS and protected by applicable intellectual property laws. We grant you a limited, non-exclusive, non-transferable, revocable licence to use the Service in accordance with these Terms. You may not copy, modify, or distribute any part of the Service without our written permission. ## 9\\. Third-party services The Service integrates with or relies on third parties, including Stripe for payments and the streaming platforms you broadcast to. We are not responsible for third-party services, and your use of them is governed by their own terms and privacy policies. ## 10\\. Availability and disclaimers We work to keep the Service reliable, but it is provided "as is" and "as available" without warranties of any kind, whether express or implied, including warranties of merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that the Service will be uninterrupted, error-free, or that it will meet your specific requirements. Maintenance, network conditions, and factors outside our control may affect availability. This section does not exclude any liability that cannot be excluded under applicable law. ## 11\\. Limitation of liability To the extent permitted by law, IRLServer will not be liable for any indirect, incidental, or consequential damages, or for lost profits, revenue, data, or goodwill, arising from your use of or inability to use the Service. Nothing in these Terms limits liability for death or personal injury caused by negligence, for fraud, or for any other liability that cannot be limited under Norwegian or EU law. If you are a consumer, your statutory rights are not affected. ## 12\\. Changes to these Terms We may update these Terms from time to time. If we make material changes, we will give you reasonable notice, for example by email or through the Service. Your continued use of the Service after changes take effect constitutes acceptance of the updated Terms. ## 13\\. Governing law and dispute resolution These Terms are governed by Norwegian law. If you are a consumer, you also benefit from any mandatory protections of the law of your country of residence, and mandatory rules determine the courts that may hear a dispute. We are not obliged and have chosen not to participate in dispute resolution proceedings before a consumer arbitration board. ## 14\\. Contact If you have questions about these Terms, contact us at \[mail@irlserver.com\](mailto:mail@irlserver.com). Our full legal and contact details are listed in our \[Imprint\](https://irlserver.com/imprint). --- Source: https://irlserver.com/tools # FREE IRL TOOLS Essential tools for streamers - completely free for everyone \[ POPULAR ### IRL Stream Calculator Calculate streaming bandwidth usage based on bitrate, resolution, and duration. Plan your data needs. \](https://irlserver.com/tools/bitrate-calculator) \[ NEW ### NOALBS Config Generator Generate config.json files for NOALBS automatic scene switching. Configure triggers, scenes, and chat commands. \](https://irlserver.com/tools/noalbs-config) \[ NEW ### Twitch OAuth Generator Generate Twitch OAuth tokens for NOALBS chat bot integration. Full OAuth flow with proper scopes for chat commands. \](https://irlserver.com/tools/oauth-generator) \[ ### Twitch Clip Player Generate custom clip players for your Twitch clips. Perfect for BRB screens. \](https://brbscreen.com/) \[ ### Belabox®-compatible Remote Control Remote control interface compatible with Belabox devices. Manage settings from anywhere. Belabox is a trademark of its respective owner. Not officially affiliated. \](https://remote.irl.ac/) ## RELATED GUIDES \[OBS Studio Setup\](https://irlserver.com/guides/obs-setup) \[Mobile Streaming\](https://irlserver.com/guides/mobile-streaming) \[Hardware Encoders\](https://irlserver.com/guides/encoders) \[NOALBS Setup\](https://irlserver.com/guides/noalbs) MORE TOOLS COMING SOON • \[FOLLOW FOR UPDATES\](https://x.com/irlserver) --- Source: https://irlserver.com/tools/bitrate-calculator # IRL Stream Calculator Calculate bandwidth usage based on bitrate, resolution, and duration 4,500kbps Resolution 720p 1080p 1440p 4K The sweet spot for most IRL streamers Quality Preset Mobile 2.5 Mbps Standard 4.5 Mbps Quality 6.0 Mbps Ultra 8.0 Mbps Fine-tune Bitrate 4.5 Mbps 2 Mbps 10 Mbps Stream Duration 3h Streams / Week 4x Recommended Connection 5G / Fast LTE Per Stream 5.79 GB 3h @ 4.5 Mbps REC Monthly Estimate 100 GB ~17 streams/month Weekly 23.17 GB Yearly 1.2 TB IRLServer Advantage: All plans include unlimited server bandwidth. These estimates help you plan your mobile data usage. Formula (kbps × hours × 3600) ÷ 8 ÷ 1024² = GB ## RELATED GUIDES \[ ### Mobile Streaming Guide Optimize bitrate for mobile SRTLA streaming \](https://irlserver.com/guides/mobile-streaming)\[ ### Hardware Encoders Configure encoder bitrate settings \](https://irlserver.com/guides/encoders)\[ ### Use Cases See how streamers use IRLServer \](https://irlserver.com/use-cases)\[ ### OBS Studio Setup Configure OBS to receive your stream \](https://irlserver.com/guides/obs-setup) --- Source: https://irlserver.com/tools/noalbs-config # NOALBS Config Generator Generate a config.json for NOALBS automatic scene switching. Based on the official NOALBS v2 configuration format. \[NOALBS GitHub\](https://github.com/NOALBS/nginx-obs-automatic-low-bitrate-switching) \[Download NOALBS\](https://github.com/NOALBS/nginx-obs-automatic-low-bitrate-switching/releases) ## OBS WebSocket Connection Host Usually localhost for local OBS Port Default is 4455 for WebSocket 5.x Password Found in OBS → Tools → WebSocket Server Settings ## Stream Servers Server #1(Primary) ENABLED Name Server Type SRT Live Server (SRTLA) Belabox Cloud Nginx RTMP Node Media Server MediaMTX Nimble Streamer RIST WebSocket (push stats) Xiu Stats URL Get this from your IRLServer dashboard or server provider Publisher Format: live/stream/stream\\\_key Priority Lower number = higher priority Add Another Server ## Switching Triggers Low Bitrate (kbps) At or below this, switch to the LOW scene. 0 disables it. Offline Bitrate (kbps) At or below this, switch to the BRB scene. Keep it under the Low bitrate, or the LOW scene never gets used. 0 disables it. Low RTT (ms) At or above this, switch to the LOW scene. 0 disables it. Offline RTT (ms) At or above this, switch to the BRB scene. Keep it over the Low RTT. 0 disables it. Retry Attempts Number of checks before switching scenes ## Scene Names These must match your OBS scene names exactly (case sensitive) Normal Scene Low Bitrate Scene Offline Scene ## Optional ScenesOptional ## Chat Integration ## Advanced Options CONFIG.JSON ## Generated Configuration { "user": { "id": null, "name": "NOALBSbot", "passwordHash": null }, "switcher": { "bitrateSwitcherEnabled": true, "onlySwitchWhenStreaming": false, "instantlySwitchOnRecover": true, "autoSwitchNotification": true, "retryAttempts": 5, "triggers": { "low": 500, "rtt": 1000, "offline": 450, "rttOffline": 3500 }, "switchingScenes": { "normal": "LIVE", "low": "LOW", "offline": "BRB" }, "streamServers": \\\[ { "streamServer": { "type": "SrtLiveServer", "statsUrl": "https://your-stats-url.com/stats", "publisher": "live/stream/stream\\\_key" }, "name": "IRLServer", "priority": 0, "overrideScenes": null, "dependsOn": null, "enabled": true } \\\] }, "software": { "type": "Obs", "host": "localhost", "password": "", "port": 4455 }, "optionalScenes": { "starting": null, "ending": null, "privacy": null, "refresh": null }, "optionalOptions": { "twitchTranscodingCheck": false, "twitchTranscodingRetries": 5, "twitchTranscodingDelaySeconds": 15, "offlineTimeout": null, "recordWhileStreaming": false, "switchToStartingSceneOnStreamStart": false } } Copy Download Quick Setup: 1. Download NOALBS from \[GitHub releases\](https://github.com/NOALBS/nginx-obs-automatic-low-bitrate-switching/releases) 2. Create scenes in OBS: LIVE, LOW, BRB, REFRESH 3. Enable WebSocket in OBS → Tools → WebSocket Server Settings 4. Download this config.json and place it in NOALBS folder 5. For chat: Create .env file with Twitch OAuth token 6. Run NOALBS executable IRLServer users: Your stats URL is available in the dashboard under Server Settings → Endpoints. Use the SrtLiveServer type for SRTLA endpoints. Remember to update the WebSocket password and stats URLs with your actual values. Scene names must match your OBS scenes exactly. ## Related Resources \[NOALBS Setup Guide\](https://irlserver.com/guides/noalbs) \[OBS Setup Guide\](https://irlserver.com/guides/obs-setup) \[OAuth Token Generator\](https://irlserver.com/tools/oauth-generator) --- Source: https://irlserver.com/tools/oauth-generator # Twitch OAuth Generator Generate Twitch OAuth tokens for NOALBS chat commands. One click to authorize and get your token. ## Generate Twitch Token For NOALBS chat bot integration ### Permissions Requested \`chat:read\` Read messages from your chat \`chat:edit\` Send messages to your chat Authorize with Twitch You will be redirected to Twitch to authorize. Your token is generated securely on our server. ### How It Works 1. 1\\. Click the button above 2. 2\\. Authorize on Twitch 3. 3\\. Copy your token 4. 4\\. Add to NOALBS .env file ### Using with NOALBS Create a .env file in your NOALBS folder: TWITCH\\\_BOT\\\_USERNAME=your\\\_username TWITCH\\\_BOT\\\_OAUTH=oauth:xxx Need to revoke a token? \[Manage Connections in Twitch Settings\](https://www.twitch.tv/settings/connections) ## Related Resources \[NOALBS Setup Guide\](https://irlserver.com/guides/noalbs) \[NOALBS Config Generator\](https://irlserver.com/tools/noalbs-config) --- Source: https://irlserver.com/guides/connect-liveu-solo-pro # How to Connect a LiveU Solo Pro to Your Relay over SRT The \[combined LiveU guide\](https://irlserver.com/guides/connect-liveu) covers both units and is the right starting point if you are choosing between them. This page is the Solo Pro specifically, because the two things it adds over a Solo — SRT and HEVC — both need decisions the Solo never asks you for. SRT not SRTLA 2500 ms latency to start at HEVC more picture per megabit ## First: LiveU bonds itself This trips people up coming from a Belabox or an IRLBox. Those encoders hand the bonding problem to SRTLA and expect the relay to reassemble the pieces. LiveU does not. Its LRT layer bonds your modems inside the unit and emits one stream. So there is no SRTLA to configure and no SRTLA endpoint to create. You want a plain \*\*SRT\*\* endpoint, and the Solo Pro will fill it with an already-bonded feed. ## Step 1: create an SRT endpoint In the dashboard, create an SRT relay endpoint in the region nearest to where the unit will be, not nearest your OBS machine. You need the hostname, the port and the stream id: \`\`\` srt://srt.sfj.irl.ac:4001?streamid=live/YOUR-STREAM-KEY \`\`\` Regions are \`sfj\`, \`fin\`, \`ord\`, \`hil\` and \`sgp\`, and the endpoint answers in all of them, so travelling is a hostname edit rather than a migration. ## Step 2: add a custom SRT destination In the LiveU Solo Portal, add a custom destination and choose \*\*SRT\*\*, in \*\*caller\*\* mode. Caller means the unit dials out to us — the only direction that works when the unit is on cellular and unreachable from outside. Enter the hostname and port \`4001\` in their fields, and your stream id (\`live/YOUR-STREAM-KEY\`) in the stream id field. If the portal build you have offers only a single URL box, paste the full form above. 4001 is SRT, 5000 is SRTLA The SRTLA port will not accept a plain SRT connection, and the failure looks like a network problem rather than a wrong number. If the destination refuses to connect and everything else looks correct, check the port first. ## Step 3: set the latency to 2500 ms SRT's latency setting is a buffer: it is how long the protocol is allowed to hold a packet while asking for a missing one again. Too small and there is no time to retransmit, so SRT behaves like RTMP with extra steps. Start at 2500 ms. LiveU is already doing its own recovery underneath, and the number needs to cover both that and the cellular jitter below it. Once you have a stream that holds up on a real walk, \[SRT latency settings\](https://irlserver.com/guides/srt-latency-settings-irl-streaming) explains what you are trading if you want to bring it down. ## Step 4: decide about HEVC The Solo Pro can encode HEVC. At IRL bitrates that is a real gain — the same 6 Mbps carries visibly more detail than it does in H.264, which matters most in exactly the conditions IRL streams live in: motion, low light, and compression artefacts on faces. The catch is the other end. Current OBS releases decode HEVC over SRT; older ones do not, and they fail silently with a black source rather than an error message. Test it at your desk before you rely on it in the field, and keep H.264 as the fallback if your studio machine is old. Our SRT and RTMP endpoints accept both, so this is a decision about your OBS, not about the relay. ## Step 5: assign, go live, and pull it into OBS Assign the destination to your unit and start streaming. On our side there is nothing to enable. In your own OBS, add a \*\*Media Source\*\*, uncheck \_Local File\_, and paste the playback URL from the dashboard. The buffering and the checkboxes that let a stalled feed recover are covered in the \[OBS setup guide\](https://irlserver.com/guides/obs-setup). Why not send LiveU straight to Twitch You can, and for a single stable location it is fine. The reason to put a relay in the middle is your OBS: overlays, scene switching, and a connection to the platform that lives on a stable network at home rather than on the back of a bonded unit walking through a city. \[Get an SRT endpoint\](https://irlserver.com/pricing) Add \[drop protection\](https://irlserver.com/guides/keep-stream-live-when-signal-drops) so NOALBS shows a BRB scene during a rough patch instead of letting the broadcast end. ## FAQ What does the Solo Pro do that the Solo does not? SRT and HEVC. A LiveU Solo streams RTMP only, which means no gap tolerance and H.264 alone. The Solo Pro adds SRT, which recovers from brief losses instead of ending, and HEVC, which gets more picture out of the same bitrate. If you have a Pro, using it as an RTMP unit wastes both. Do I configure SRTLA on a Solo Pro? No. LiveU bonds with its own LRT layer inside the unit and sends you one already-bonded SRT stream. SRTLA is a different bonding scheme for encoders that do not have one. Point the Solo Pro at the SRT endpoint, not the SRTLA one. Which SRT latency should I use? Start at 2500 ms. That is enough room for LiveU's own recovery plus the cellular jitter underneath it. Lower values look attractive on paper and give SRT less room to retransmit, which is the thing you are paying for. Will HEVC work in my OBS? Current OBS releases decode HEVC over SRT. Older builds do not, and the failure is silent — a black source rather than an error. Test HEVC before you rely on it, and keep H.264 as the fallback if your studio machine is old. Caller or listener mode? Caller. The Solo Pro dials out to our relay, which is what you want on a cellular connection where nothing can dial in to the unit. --- Source: https://irlserver.com/guides/connect-liveu # How to Connect LiveU Solo and Solo Pro to Your Relay LiveU encoders are a different animal from a Belabox or a phone. LiveU does its own bonding with its \*\*LRT\*\* layer, so it hands your relay a single, already bonded stream. That means you do not set up SRTLA on a LiveU. You just point it at the right endpoint. The protocol depends on which unit you have. Solo RTMP only Solo Pro adds SRT LRT LiveU's own bonding ## How LiveU bonding differs A Belabox or a phone app bonds with \[SRTLA\](https://irlserver.com/guides/srtla-bonding), which our relay reassembles. LiveU does not. Both LiveU Solos bond with LiveU's own LRT layer, on the device and through LiveU's service, and the result is a single stream. You send that single stream to our relay over RTMP or SRT. There is no SRTLA setting to configure on a LiveU. ## LiveU Solo (RTMP) The Solo streams over RTMP. 1. Create an \*\*RTMP\*\* endpoint in your \[dashboard\](https://irl.ac/) and copy the server URL and stream key. 2. In the LiveU portal, add a \*\*Custom RTMP\*\* destination. 3. Enter the relay details: - Server: \`rtmp://rtmp..irl.ac:1935/publish\` - Stream key: your key from the dashboard 4. Assign it to your unit and start streaming. ## LiveU Solo Pro (SRT) The Solo Pro adds SRT, which holds up better on a rough connection. 1. Create an \*\*SRT\*\* endpoint in your dashboard and copy the details. 2. In the LiveU portal, add a \*\*Custom SRT\*\* destination. 3. Enter the relay details: - Server: \`srt://srt..irl.ac:4001\` - Stream id: \`live/stream/YOUR\_KEY\` - Latency: \`2500ms\` (recommended) 4. Assign it to your unit and start streaming. Pick the region nearest you Your dashboard shows the exact server, key, and stream id, and lets you pick a region (Singapore, the US, Norway, or Finland). Closer is lower latency. ## Then broadcast from your own OBS However your LiveU sends its stream, the broadcast layer is the same as every other rig. Pull the relay into your own OBS as a media source, and let OBS stay connected to Twitch or Kick while \[NOALBS\](https://irlserver.com/guides/noalbs) switches scenes when the feed gets rough. Full picture in \[keep your stream live\](https://irlserver.com/guides/keep-stream-live-when-signal-drops). \[Get a relay for your LiveU\](https://irlserver.com/pricing) Worth knowing if you have not bought the rig yet: LRT bonding is an ongoing cost on top of the LiveU hardware, because the bonding runs through LiveU's service. SRTLA bonding is not billed separately, it is part of the relay. A \[Belabox\](https://irlserver.com/guides/connect-belabox) or a bonding phone app takes that route, and adds remote control on top. ## FAQ Does LiveU support SRTLA bonding? No. LiveU does its own bonding with its LRT layer on both the Solo and Solo Pro. It does not use SRTLA. LiveU bonds your connections itself, then sends a single stream to your relay, so you do not configure SRTLA on a LiveU. Which protocol does each LiveU use? The LiveU Solo streams over RTMP only. The LiveU Solo Pro adds SRT, which is the better choice for an unpredictable connection. Pick an RTMP endpoint for a Solo and an SRT endpoint for a Solo Pro. Do I still need OBS with a LiveU? Yes, for a reliable broadcast. LiveU sends to your relay, and your own OBS pulls that in and stays connected to Twitch or Kick, with NOALBS holding a scene when the feed gets rough.

---

Source: https://irlserver.com/llms.txt

\# IRLServer > IRLServer runs RTMP, SRT and SRTLA relay endpoints for IRL streamers: your encoder sends to a relay near you, the relay forwards to the streaming software you already run, and your stream survives the moment a mobile uplink does not. - Every page below is also available as markdown by appending \`.md\` to its URL, by adding \`?format=md\`, or by sending \`Accept: text/markdown\`. - \`/llms-full.txt\` contains the full text of every page in one file. - The relay is the product most customers buy. It does not include a compositor: you bring your own OBS, Streamlabs or vMix. ## Product - \[IRLServer - Stream Relay Endpoints for IRL Streamers\](https://irlserver.com/index.md): RTMP, SRT and SRTLA relay endpoints for IRL streamers. Custom optimizations for maximum stream stability. Automatic scene switching and drop protection. Servers in EU, US & Norway. - \[IRL Streaming Features - SRTLA, Drop Protection, Global Servers\](https://irlserver.com/features.md): Explore IRLServer features: RTMP, SRT, and SRTLA support, custom optimizations, automatic scene switching, and global relay coverage for stable IRL streaming. - \[IRL Streaming Relay Pricing - Plans for Streamers\](https://irlserver.com/pricing.md): See IRLServer pricing for professional relay endpoints with RTMP, SRT, and SRTLA support, automatic scene switching, and global server coverage, plus Stage cloud compositor plans. ## Guides - \[IRL Streaming Setup Guides & Tutorials\](https://irlserver.com/guides.md): Complete setup guides for IRL streaming. Learn how to configure OBS, mobile streaming apps, hardware encoders, and NOALBS for automatic scene switching. - \[Hardware Encoder Setup Guide - Belabox, LiveU, IRLBox\](https://irlserver.com/guides/encoders.md): Configure hardware encoders for IRL streaming. Setup guides for Belabox, LiveU Solo Pro, IRLBox, and other portable encoders with SRTLA and SRT support. - \[Mobile Streaming Apps Setup Guide - Moblin, IRL Pro, Larix\](https://irlserver.com/guides/mobile-streaming.md): Complete setup guides for mobile streaming apps. Configure Moblin for iOS, IRL Pro for Android, and Larix Broadcaster with SRTLA bonding for reliable IRL streaming. - \[SRT and RTMP into OBS: Setup Guide for IRL Streaming\](https://irlserver.com/guides/obs-setup.md): How to receive an SRT, SRTLA or RTMP relay in OBS Studio: the media source URL for each protocol, the four checkboxes that make a dropped feed recover, buffering, and NOALBS scenes. - \[How to Connect a LiveU Solo Pro to Your Relay over SRT\](https://irlserver.com/guides/connect-liveu-solo-pro.md): Set up an SRT custom destination for a LiveU Solo Pro, pick the right latency, and use HEVC to get more picture out of the same bonded uplink. - \[How to Connect LiveU Solo and Solo Pro to Your Relay\](https://irlserver.com/guides/connect-liveu.md): Connect a LiveU Solo (RTMP) or Solo Pro (SRT) to an IRLServer relay. LiveU bonds with its own LRT layer, then sends a single stream to your relay and OBS. ## Comparisons - \[IRL Streaming Relay Comparison - IRLServer vs Competitors\](https://irlserver.com/compare.md): Compare IRL streaming relay providers. See how IRLServer stacks up against alternatives with detailed feature comparisons, pricing, and server locations. ## Tools - \[Free IRL Streaming Tools - Calculator & Generators\](https://irlserver.com/tools.md): Use free IRL streaming tools including bitrate calculator, NOALBS config generator, and Twitch OAuth token generator. - \[Streaming Bitrate Calculator - Free Tool for IRL Streamers\](https://irlserver.com/tools/bitrate-calculator.md): Calculate optimal streaming bitrate for IRL streams. Estimate data usage and tune settings for RTMP, SRT, and SRTLA workflows. - \[NOALBS Config Generator - Free Tool for IRL Streamers\](https://irlserver.com/tools/noalbs-config.md): Generate NOALBS config.json files for automatic OBS scene switching. Configure bitrate triggers, stream servers, and chat commands. Free tool for IRL streamers. - \[Twitch OAuth Token Generator for NOALBS | IRLServer Tools\](https://irlserver.com/tools/oauth-generator.md): Generate Twitch OAuth tokens for NOALBS chat bot integration. Full OAuth flow with chat:read and chat:edit scopes for automatic scene switching commands. ## Optional - \[Imprint\](https://irlserver.com/imprint.md): Legal disclosure (Impressum) for IRLServer, operated by Lekanger Solutions, in accordance with § 5 DDG. - \[Privacy Policy\](https://irlserver.com/privacy.md): Read IRLServer's privacy policy, including information on data collection, usage, cookies, and user rights. - \[Terms of Service\](https://irlserver.com/terms.md): Read IRLServer's terms of service covering the streaming relay subscription, billing, acceptable use, and your rights as a customer.

---

Source: https://irlserver.com/compare

# RELAY PROVIDER COMPARISON

See how IRLServer compares to other cloud streaming solutions. We focus on reliability, features, and value for IRL streamers.

## Why Choose IRLServer?

### Custom SRTLA Optimizations

Our SRTLA implementation includes in-house optimizations for better reliability and performance compared to standard implementations.

### Many Protocols Available

RTMP, RTMPS, SRT, and SRTLA - all protocols available. Choose what fits your needs.

### Global Server Network

Strategically positioned servers in EU and US for low-latency streaming from anywhere in the world.

### No Data Caps

We do not meter your transfer or charge for overage. One flat price, however long you stream, with a 20 Mb/s input bitrate.

## Feature Comparison

| Feature | IRLServer | Typical Competitor |
| --- | --- | --- |
| Protocols |     |     |
| SRTLA Support | Yes | Varies |
| SRT Support | Yes | Most |
| RTMP Support | Yes | All |
| RTMPS (Secure) | Yes | Some |
| Features |     |     |
| Drop Protection (NOALBS compatible) | Yes | Most |
| No Data Caps | Yes | Some |
| Max Input Bitrate | 20 Mb/s | Tiered |
| Custom SRTLA Optimizations | Yes | Rare |
| Belabox-compatible Remote | Yes | Rare |
| Stats API for NOALBS | Yes | Most |
| Server Coverage |     |     |
| EU Servers | Yes | Most |
| US Servers | Yes | Most |
| Support |     |     |
| Discord Community | Yes | Most |
| Setup Guides | Yes | Some |
| Free Tools (Calculator, Config Gen) | Yes | Few |

## Simple, Transparent Pricing

### What's Included

-   All protocols (RTMP, RTMPS, SRT, SRTLA)
-   No data caps
-   Multiple endpoints
-   Stats API for NOALBS
-   Discord support

### No Hidden Fees

-   No bandwidth overage charges
-   No setup fees
-   No long-term contracts
-   Cancel anytime

[View Pricing](https://irlserver.com/pricing)

## Ready to Get Started?

Join thousands of IRL streamers who trust IRLServer for their cloud streaming needs.

[Start Streaming](https://irl.ac/) [View Setup Guides](https://irlserver.com/guides)

---

Source: https://irlserver.com/features

# IRL Streaming Features - SRTLA, Drop Protection, Global Servers | IRLServer

## BUILT FOR IRL

RTMP, SRT and SRTLA relay endpoints with custom optimizations for professional IRL streaming.

### Enhanced SRTLA Bonding

Custom optimizations for maximum stream stability. Our SRTLA relays deliver superior reliability and performance.

### Drop Protection

Never lose your audience. Automatic BRB scene switching when your connection drops, keeping viewers engaged until you reconnect.

### Wide Compatibility

Works with Moblin, Belabox, IRLBox, LiveU Solo and Solo Pro, IRL Pro, Larix and more.

### Automatic Scene Switching

With NOALBS, detect low bitrate and disconnects to automatically switch to a BRB scene.

### No Data Caps

Stream as long as you like. We never meter your transfer or bill for overage. The only ceiling is the 20 Mb/s input bitrate.

### Easy Setup

One-click setup for most streaming apps. Guides available for manual configuration.

### Manage From Anywhere

Control, customize and monitor your streaming endpoints from our dashboard.

### Protocol Support

We support RTMP, SRTLA, SRT and RTMPS protocols.

---

Source: https://irlserver.com/guides

# SETUP GUIDES

Step-by-step tutorials to get your IRL stream up and running. From basic OBS setup to advanced encoder configuration.

Get started

[

Get started

### SRTLA Bonding Explained: Stream IRL Without Dropping

What SRTLA bonding is, how it holds your IRL stream together across multiple modems, and why a custom optimized relay beats the basic open source version.

SRTLA Bonding Relay

7 min read

](https://irlserver.com/guides/srtla-bonding)[

Get started

### The Best IRL Streaming Setup for Twitch and Kick in 2026

A complete, reliable IRL streaming setup for Twitch and Kick: phone or encoder, SRTLA bonding, a relay, your own OBS, and NOALBS scene switching, explained end to end.

Twitch Kick SRTLA

8 min read

](https://irlserver.com/guides/best-irl-streaming-setup-twitch-kick)

Stage

[

Stage

### How to IRL Stream Without a PC at Home

Every other setup assumes a PC running OBS while you are out. If you do not have one, here is the path that does the compositing in the cloud instead.

Stage No PC Phone only

6 min read

](https://irlserver.com/guides/irl-stream-without-a-pc)[

Stage

### How to Multistream to Twitch, Kick and YouTube at Once

Multistreaming an IRL feed comes down to which machine makes the copies: your own OBS at home, or a compositor in the cloud. What each one costs you.

Stage Multistreaming Twitch

6 min read

](https://irlserver.com/guides/multistream-twitch-kick-youtube)

Protocols

[

Protocols

### SRT Latency Settings for IRL Streaming: What to Set and Why

What the SRT latency number actually does, why 2000 to 3000 ms is the right starting point for cellular and bonded rigs, how to read freezes vs bitrate drops, and why a lower number rarely makes your stream feel faster.

SRT SRTLA Latency

7 min read

](https://irlserver.com/guides/srt-latency-settings-irl-streaming)[

Protocols

### SRTLA vs RTMP for IRL Streaming: Which Protocol to Use

How SRTLA, SRT, and RTMP differ for IRL streaming: recovery, bonding, latency, and when each one is actually the right call.

SRTLA RTMP SRT

6 min read

](https://irlserver.com/guides/srtla-vs-rtmp)

Reliability

[

Reliability

### NOALBS Scene Switching

Automatic scene switching based on bitrate. Switch between LIVE, LOW, and BRB scenes when connection quality changes.

NOALBS Automation

15 min

](https://irlserver.com/guides/noalbs)[

Reliability

### How to Keep Your IRL Stream Live When the Signal Drops

A field tested setup that stops your Twitch or Kick stream from ending when phone signal dies: SRTLA bonding, the relay as a source in your own OBS, and NOALBS auto scene switching.

Drop protection SRTLA NOALBS

9 min read

](https://irlserver.com/guides/keep-stream-live-when-signal-drops)[

Reliability

### How to Stop Your Stream From Ending on Twitch and Kick

Why Twitch and Kick end an IRL broadcast when your connection drops, and the setup that keeps the session alive: your own OBS broadcasting through a relay with NOALBS.

Twitch Kick Drop protection

6 min read

](https://irlserver.com/guides/stop-streams-ending-twitch-kick)[

Reliability

### Why Mobile Signal Gets Bad While You Stream (and How to Fix It)

The real reasons cellular signal drops during an IRL stream: congestion, tower handoffs, crowds, and weak uploads, plus the setup that keeps you live anyway.

Connectivity SRTLA Bonding

6 min read

](https://irlserver.com/guides/why-mobile-signal-drops-irl)

Encoders

[

Encoders

### Hardware Encoders

Configure Belabox, LiveU Solo, and IRLBox. Set up SRT and SRTLA streaming with your relay endpoint.

Belabox LiveU

12 min

](https://irlserver.com/guides/encoders)[

Encoders

### How to Connect a LiveU Solo Pro to Your Relay over SRT

Set up an SRT custom destination for a LiveU Solo Pro, pick the right latency, and use HEVC to get more picture out of the same bonded uplink.

LiveU SRT HEVC

6 min read

](https://irlserver.com/guides/connect-liveu-solo-pro)[

Encoders

### How to Connect an IRLBox to Your Relay

Send an IRLBox feed to an SRT or RTMP relay endpoint, get it into your own OBS, and understand where IRLBox's own RIST bonding fits.

IRLBox SRT RTMP

6 min read

](https://irlserver.com/guides/connect-irlbox)[

Encoders

### How to Connect Belabox to Your Relay (with Remote Control)

Connect a Belabox to an SRTLA relay step by step, and remote control the box while you are live. The custom remote control most providers cannot offer.

Belabox SRTLA Remote control

6 min read

](https://irlserver.com/guides/connect-belabox)[

Encoders

### How to Connect LiveU Solo and Solo Pro to Your Relay

Connect a LiveU Solo (RTMP) or Solo Pro (SRT) to an IRLServer relay. LiveU bonds with its own LRT layer, then sends a single stream to your relay and OBS.

LiveU SRT RTMP

6 min read

](https://irlserver.com/guides/connect-liveu)[

Encoders

### How to Stream from a DJI Osmo Pocket to Your Relay over RTMP

Send a DJI Osmo Pocket 3 or Pocket 4 straight to an RTMP relay endpoint using the DJI Mimo app, then pull the feed into your own OBS.

DJI RTMP Phone

6 min read

](https://irlserver.com/guides/connect-dji-osmo-pocket)

Phone streaming

[

Phone streaming

### Mobile Streaming Apps

Setup guides for Moblin, IRL Pro, and Larix Broadcaster with SRTLA bonding for reliable mobile streaming on iOS and Android.

SRTLA Mobile

8 min

](https://irlserver.com/guides/mobile-streaming)[

Phone streaming

### How to Connect IRL Pro to Your Relay (Android SRTLA Setup)

Point IRL Pro on Android at an SRTLA relay step by step: protocol, server, port, and stream id, plus bonding multiple connections for a stable IRL stream.

IRL Pro Android SRTLA

5 min read

](https://irlserver.com/guides/connect-irl-pro)[

Phone streaming

### How to Connect Moblin to Your Relay (iPhone SRTLA Setup)

Point Moblin on iPhone at an SRTLA relay step by step: protocol, server, port, and stream id, plus bonding multiple connections for a stable IRL stream.

Moblin iPhone SRTLA

5 min read

](https://irlserver.com/guides/connect-moblin)[

Phone streaming

### How to Go Live IRL From Your Android Phone in 2026

Everything you need to IRL stream from Android: the right app (IRL Pro), bonded connections, a relay, and your own OBS, so your stream holds when you move.

Android IRL Pro SRTLA

6 min read

](https://irlserver.com/guides/go-live-from-android)[

Phone streaming

### How to Go Live IRL From Your iPhone in 2026

Everything you need to IRL stream from an iPhone: the right app (Moblin), bonded connections, a relay, and your own OBS, so your stream holds when you move.

iPhone Moblin SRTLA

6 min read

](https://irlserver.com/guides/go-live-from-iphone)[

Phone streaming

### How to Use a DJI Camera with Moblin for Bonded IRL Streaming

Pair a DJI Osmo Pocket or Osmo Action to Moblin over Bluetooth, let Moblin receive it on its own RTMP server, and send the result to an SRTLA relay so the feed bonds across cellular and WiFi.

DJI Moblin SRTLA

7 min read

](https://irlserver.com/guides/dji-through-moblin)

OBS

[

OBS

### OBS Studio Setup

Configure OBS Studio for IRL streaming with relay endpoints: media source setup, scene creation, and network buffering.

OBS Beginner

10 min

](https://irlserver.com/guides/obs-setup)

Collab

[

Collab

### How to Share Your IRL Feed With Other Streamers (Play Keys)

Co-stream your IRL feed with other creators using play keys. Generate a named, shareable player key per streamer, all pulling from your single publisher feed.

Collab Play keys OBS

5 min read

](https://irlserver.com/guides/share-your-feed-with-other-streamers)

Need more help?

[Join Discord](https://irlserver.com/discord) [Free Tools](https://irlserver.com/tools) [Use Cases](https://irlserver.com/use-cases)

---

Source: https://irlserver.com/guides/encoders

Hardware 12 min read

# Hardware Encoder Setup Guide

Configure hardware encoders for professional IRL streaming. Learn how to set up Belabox, LiveU Solo, IRLBox, and other portable encoders with your relay endpoint.

## Why Use a Hardware Encoder?

### Better Battery Life

Dedicated encoders don't drain your phone battery

### Multi-SIM Bonding

Bond 4+ cellular connections for maximum reliability

### HDMI Input

Use any camera with HDMI output for better quality

## Belabox

### Belabox

SRTLA

Open-source software for Orange Pi 5 Plus, Radxa Rock 5A/5B, and Jetson Nano. Supports multi-modem SRTLA bonding for reliable mobile streaming.

SRTLA Bonding Multi-modem Open Source 4G/5G Support

#### Configuration

SRTLA receiver address `srt.region.irl.ac`

SRTLA receiver port `5000`

SRT Stream ID `live/stream/YOUR_KEY`

#### Setup Steps

1.  Access Belabox web interface (usually at 192.168.x.x)
2.  Navigate to "SRTLA Settings"
3.  If given the choice for SRTLA relay server, choose "CUSTOM"
4.  Enter your SRTLA receiver address, port and SRT streamid from your dashboard
5.  Configure your modems in the Network section
6.  Start streaming

Use the IRLServer [Belabox-compatible remote control](https://remote.irl.ac/) to manage your Belabox from anywhere.

## LiveU Solo Pro

### LiveU Solo Pro

SRT

Professional portable encoder with reliable low-latency delivery. Supports SRT protocol.

SRT Professional Grade Built-in Battery Easy Setup

#### SRT Configuration

SRT URL `srt://srt.region.irl.ac:4001`

Stream ID `live/stream/YOUR_KEY`

Latency `2500ms (recommended)`

#### Setup Steps

1.  Log in to your LiveU Solo Portal
2.  Navigate to Destinations → Custom SRT
3.  Enter the SRT URL with your stream ID
4.  Set latency to 2500ms for optimal stability
5.  Save and assign to your unit

LiveU Solo Pro connects via SRT to your relay endpoint. LiveU handles bonding with its own LRT layer, and you still get the benefits of our relay.

## LiveU (RTMP)

### LiveU

RTMP

Standard LiveU encoders using RTMP protocol for streaming to relay endpoints.

RTMP Professional Reliable Easy Config

#### RTMP Configuration

Server URL `rtmp://rtmp.region.irl.ac:1935/publish`

Stream Key `YOUR_KEY`

#### Setup Steps

1.  Access LiveU Central portal
2.  Create a Custom RTMP destination
3.  Enter the server URL and stream key
4.  Assign to your encoder unit

## IRLBox

### IRLBox

SRT / RTMP / RIST

Portable IRL streaming encoder supporting both SRT and RTMP protocols.

SRT RTMP RIST Portable Multi-modem Budget-friendly

#### SRT Configuration

Server URL `srt.region.irl.ac`

Port `4001`

Stream ID `live/stream/YOUR_KEY`

Latency `2500ms (recommended)`

#### RTMP Configuration (Alternative)

Server URL `rtmp://rtmp.region.irl.ac:1935/publish`

Stream Key `YOUR_KEY`

SRTLA is recommended over RTMP for mobile streaming as it provides better reliability with connection bonding.

## General Tips for Hardware Encoders

**Latency Setting:** Start with 2500ms latency for SRTLA/SRT. You can lower it to 2000ms for less delay if your connection is stable.

**Bitrate:** Most hardware encoders work well at 4000-6000 kbps for 1080p. Don't go too high - it wastes data and doesn't improve quality much.

**Heat Management:** Hardware encoders can get hot during extended streams. Ensure good ventilation in your backpack.

**Power:** Use a quality power bank with USB-PD or 12V output. Cheap power banks can cause encoder instability.

## Encoder Comparison

| Encoder | Protocol | Bonding | Price Range |
| --- | --- | --- | --- |
| Belabox | SRTLA | Yes (up to 8 modems) | $200-400 (DIY) |
| LiveU Solo | RTMP | With expensive LRT Subscription | $1,500+ |
| LiveU Solo Pro | SRT | With expensive LRT Subscription | $1,500+ |

## Next Steps

[

### OBS Setup Guide

Configure OBS to receive your stream

](https://irlserver.com/guides/obs-setup)[

### NOALBS Setup

Automatic scene switching

](https://irlserver.com/guides/noalbs)[

### Mobile Streaming Guide

Stream from your phone with SRTLA

](https://irlserver.com/guides/mobile-streaming)[

### Bitrate Calculator

Calculate optimal stream settings

](https://irlserver.com/tools/bitrate-calculator)

---

Source: https://irlserver.com/guides/mobile-streaming

Mobile 8 min read

# Mobile Streaming Apps Guide

Setup guides for the best mobile streaming apps. Configure SRTLA bonding for reliable streaming over cellular networks with automatic failover.

## Why SRTLA for Mobile Streaming?

SRTLA (SRT with Link Aggregation) bonds multiple cellular connections together for maximum reliability. This means:

-   **Connection Redundancy:** If one network connection loses signal, others keep the stream alive
-   **Higher Bitrate:** Combine bandwidth from multiple connections
-   **Better in Crowds:** Different carriers handle congestion differently

## Moblin (iOS)

### Moblin

iOS (iPhone, iPad)

SRTLA SRT RTMP 4K 60fps H.265/HEVC Chat Integration Twitch Kick

Moblin is the most popular iOS streaming app for IRL streamers. It supports SRTLA bonding, allowing you to use multiple cellular connections simultaneously.

#### Quick Setup

1.  Download Moblin from the [App Store](https://apps.apple.com/us/app/moblin/id6466745933)
2.  Open Settings → Stream → Add new stream
3.  Select "SRTLA" as the protocol
4.  Enter your server details from the IRLServer dashboard

#### Connection Settings

Server: `srt.region.irl.ac`

Port: `5000`

Stream ID: `live/stream/YOUR_KEY`

Use "SRTLA" to bond multiple connections. Enable WiFi and cellular simultaneously for best results.

You can use the network connection of other iPhones and Android phones. Use the Moblink feature (Moblin iOS) or download the [Moblink app (Android)](https://play.google.com/store/apps/details?id=com.eerimoq.moblink).

## IRL Pro (Android)

### IRL Pro

Android

SRTLA SRT RTMP Multi-connection H.264/H.265

IRL Pro is a professional streaming app for Android with SRTLA bonding support. It allows multi-connection redundancy for reliable mobile streaming.

#### Quick Setup

1.  Download IRL Pro from the [Play Store](https://play.google.com/store/apps/details?id=app.irlpro.android)
2.  Go to Settings → Stream Settings
3.  Add a new SRTLA destination
4.  Enter your IRLServer endpoint details

#### Connection Settings

Server URL: `srt.region.irl.ac`

Port: `5000`

Stream ID: `live/stream/YOUR_KEY`

IRL Pro supports multiple network interfaces. Enable WiFi and mobile data simultaneously for bonded connections.

## Larix Broadcaster (iOS & Android)

### Larix Broadcaster

iOS & Android

SRT RTMP RIST NDI H.264/HEVC Multi-camera

Larix Broadcaster is a professional streaming camera app available on both iOS and Android. It supports SRT and RTMP protocols with advanced encoding options.

#### Quick Setup

1.  Download Larix from [softvelum.com](https://softvelum.com/larix/)
2.  Open Settings → Connections → New connection
3.  Select SRT as the protocol
4.  Configure with your IRLServer SRT URL

#### SRT URL Format

`srt://srt.region.irl.ac:4001?streamid=live/stream/YOUR_KEY&latency=2000000`

Larix supports SRT but not SRTLA bonding. For multi-SIM bonding, use Moblin (iOS) or IRL Pro (Android) instead.

## Recommended Encoding Settings

| Setting | 4G/LTE | 5G  |
| --- | --- | --- |
| Resolution | 1080p | 1080p / 1440p |
| Frame Rate | 30 fps | 30-60 fps |
| Bitrate | 3000-5000 kbps | 5000-8000 kbps |
| Codec | H.264 / H.265 | H.265 (HEVC) |
| Keyframe | 2 seconds | 2 seconds |

## Pro Tips for Mobile Streaming

**Battery Management:** Enable battery saver mode for background apps. Use a power bank - streaming at 1080p can drain your battery in 2-3 hours.

**Data Usage:** At 5000 kbps, you'll use about 2.2 GB per hour. Use our [bitrate calculator](https://irlserver.com/tools/bitrate-calculator) to plan your data needs.

**Heat Management:** Phones can throttle when hot. Remove your case and avoid direct sunlight during long streams.

**Network Priority:** Disable WiFi if you're only using cellular, or your phone may try to switch networks and cause drops.

## Next Steps

[

### OBS Setup Guide

Configure OBS to receive your stream

](https://irlserver.com/guides/obs-setup)[

### NOALBS Setup

Automatic scene switching

](https://irlserver.com/guides/noalbs)[

### Bitrate Calculator

Calculate optimal stream settings

](https://irlserver.com/tools/bitrate-calculator)

---

Source: https://irlserver.com/guides/noalbs

Automation 15 min read

# NOALBS Setup Guide

NOALBS (Nginx OBS Automatic Low Bitrate Switching) monitors your stream health and automatically switches OBS scenes when your connection drops or has low bitrate. This keeps your viewers engaged even when you're experiencing connection issues.

## What Does NOALBS Do?

### Bitrate Monitoring

Monitors your stream bitrate in real-time. When it drops below your threshold, NOALBS automatically switches to your LOW or BRB scene.

### Disconnect Detection

Detects when your encoder completely disconnects and switches to a BRB scene so viewers see something instead of a frozen frame.

### Chat Commands

Control OBS from Twitch/Kick chat. Switch scenes, check bitrate, and manage your stream without touching your computer.

### Auto Recovery

Automatically switches back to LIVE scene when your connection recovers, with configurable retry logic.

## Prerequisites

-   OBS Studio with WebSocket enabled (OBS 28+ has it built-in)
-   Scenes created in OBS: LIVE, LOW, BRB (and optionally REFRESH, STARTING, ENDING)
-   An IRLServer endpoint with stats URL (available in your dashboard)
-   Windows, macOS, or Linux computer to run NOALBS

## Setup Steps

1

### Download NOALBS

Download the latest NOALBS release from GitHub. Choose the version for your operating system:

[Download from GitHub](https://github.com/NOALBS/nginx-obs-automatic-low-bitrate-switching/releases)

Extract the downloaded ZIP file to a folder on your computer. You should see the NOALBS executable and a config.json file.

2

### Enable OBS WebSocket

NOALBS communicates with OBS through WebSocket. Enable it in OBS:

1.  Open OBS Studio
2.  Go to Tools → WebSocket Server Settings
3.  Check "Enable WebSocket server"
4.  Set a password (you'll need this for NOALBS config)
5.  Note the port (default is 4455)

3

### Create Your Scenes

Create the following scenes in OBS:

-   `LIVE` Your main streaming scene with the media source
-   `LOW` Shown during low bitrate (can include the feed + a warning)
-   `BRB` Shown when disconnected (clip player, static image, etc.)
-   `REFRESH` (Optional) Shown while refreshing the media source

Scene names are case-sensitive. Make sure they match exactly what you put in the config.

4

### Configure NOALBS

Edit the config.json file with your settings. Use our config generator for an easy setup:

[Open NOALBS Config Generator](https://irlserver.com/tools/noalbs-config)

Key settings to configure:

-   OBS WebSocket host, port, and password
-   Your stats URL from the IRLServer dashboard
-   Bitrate triggers (e.g., switch to LOW below 800 kbps)
-   Scene names matching your OBS scenes exactly

5

### Setup Chat Integration (Optional)

For Twitch chat commands, you need a Twitch OAuth token. Create a .env file in the NOALBS folder:

`TWITCH_BOT_USERNAME=your_bot_username   TWITCH_BOT_OAUTH=oauth:your_token_here`

Get your OAuth token from [twitchtokengenerator.com](https://twitchtokengenerator.com/)

6

### Run NOALBS

Start the NOALBS executable. You should see it connect to OBS and start monitoring your stream stats.

Keep NOALBS running whenever you stream. You can minimize it to the system tray or run it as a service.

## Chat Commands

NOALBS supports various chat commands organized by permission level. Default prefix is "!".

### Admin Commands

`!start`

Start streaming in OBS

Admin

`!stop`

Stop streaming in OBS

Admin

`!switch [scene]`

Switch to a specific scene

Admin

`!live`

Switch to LIVE scene

Admin

`!privacy`

Switch to privacy scene

Admin

`!record`

Toggle recording

Admin

### Moderator Commands

`!trigger [value]`

Set low bitrate trigger threshold (kbps)

Mod

`!otrigger [value]`

Set offline trigger threshold (kbps)

Mod

`!fix / !refresh`

Try to fix the stream (refresh media source)

Mod

`!sourceinfo`

Show current source information

Mod

### Public Commands

`!bitrate`

Show current stream bitrate

Public

## Troubleshooting

**NOALBS can't connect to OBS:** Check that WebSocket is enabled in OBS and the password/port in your config matches OBS settings.

**Scene switching not working:** Verify scene names in config.json match your OBS scenes exactly (case sensitive).

**Stats URL returning errors:** Make sure your encoder is streaming to the endpoint. Check the stats URL in your browser - you should see JSON data.

**Need help?** Join our [Discord](https://irlserver.com/discord) or check the [NOALBS Wiki](https://github.com/NOALBS/nginx-obs-automatic-low-bitrate-switching/wiki).

## Resources

[

### Config Generator

Generate your config.json

](https://irlserver.com/tools/noalbs-config)[

### NOALBS GitHub

Source code & releases

](https://github.com/NOALBS/nginx-obs-automatic-low-bitrate-switching)[

### OBS Setup Guide

Configure OBS for IRL streaming

](https://irlserver.com/guides/obs-setup)[

### OAuth Token Generator

Generate Twitch OAuth tokens

](https://irlserver.com/tools/oauth-generator)

---

Source: https://irlserver.com/guides/obs-setup

Beginner 10 min read

# OBS Studio Setup Guide

Learn how to configure OBS Studio to receive your IRL stream from a relay endpoint. This guide covers both basic setup for beginners and advanced NOALBS configuration for automatic scene switching.

## Prerequisites

-   [OBS Studio](https://obsproject.com/download) installed (version 28.0 or later recommended)
-   An IRLServer account with an active endpoint (get one at [irl.ac](https://irl.ac/))
-   Your stream URL from the dashboard (RTMP or SRT/SRTLA)

## Choose Your Setup

### Simplified Setup

Just one LIVE scene. Best for beginners who want to get started quickly without automatic scene switching.

Recommended for beginners

### Advanced Setup (NOALBS)

Multiple scenes (LIVE, LOW, BRB, REFRESH) with automatic switching when your connection drops or has low bitrate.

Recommended for regular streamers

## Step-by-Step Setup

1

### Launch OBS Studio

Open OBS Studio on your computer. If this is your first time, complete the auto-configuration wizard or click Cancel to set up manually.

2

### Create Your Scenes

For simplified setup, create one scene:

-   `LIVE` \- Your main streaming scene

For NOALBS setup, create these scenes:

-   `LIVE` \- Main stream view
-   `LOW` \- Low bitrate warning scene
-   `BRB` \- Disconnected/be right back scene
-   `REFRESH` \- Connection refresh scene

Right-click in the Scenes panel → Add Scene. Use EXACT names (case sensitive) for NOALBS compatibility.

3

### Add Media Source

In your LIVE scene, add a Media Source:

1.  Right-click in Sources panel → Add → Media Source
2.  Name it something like "IRL Feed" or "Stream Input"
3.  Uncheck "Local File"
4.  Check "Show nothing when playback ends"
5.  Check "Restart playback when source becomes active"
6.  Check "Close file when inactive"

4

### Configure Your Stream URL

In the Media Source properties, paste your stream URL from the IRLServer dashboard.

For RTMP endpoints:

`rtmp://rtmp.region.irl.ac/publish/YOUR_KEY`

For SRT/SRTLA endpoints:

`srt://srt.region.irl.ac:4000?streamid=play/stream/YOUR_KEY&latency=2000000`

Your actual stream URLs are available in your dashboard at [irl.ac/dashboard/endpoints](https://irl.ac/dashboard/endpoints)

5

### Set Network Buffering

Configure network buffering for stable playback. In the Media Source properties:

-   **Network Buffering:** 1 MB (recommended) or higher for unstable connections
-   **Reconnect Delay:** 3 seconds

Higher buffer = more stable but more delay. Start with 1 MB and increase if you see stuttering.

6

### Stretch to Screen

Make the media source fill your canvas:

1.  Right-click on the media source in the preview
2.  Transform → Stretch to Screen

Or press Ctrl+F with the source selected to fit to screen.

7

### Copy to Other Scenes (NOALBS)

If using NOALBS, copy your media source to other scenes:

1.  Right-click your media source → Copy
2.  Go to LOW scene → Right-click → Paste (Reference)
3.  Repeat for REFRESH scene

Using "Paste (Reference)" ensures all scenes use the same source. Changes to one will apply to all.

8

### Test Your Setup

Start streaming from your encoder (Belabox, Moblin, etc.) to your IRLServer endpoint. You should see your stream appear in OBS within a few seconds.

If the stream doesn't appear, check that your encoder is connected and streaming to the correct URL. You can verify connection status in your IRLServer dashboard.

## Next Steps

[

### Setup NOALBS

Automatic scene switching

](https://irlserver.com/guides/noalbs)[

### NOALBS Config Generator

Generate config.json

](https://irlserver.com/tools/noalbs-config)[

### Bitrate Calculator

Calculate optimal stream settings

](https://irlserver.com/tools/bitrate-calculator)[

### Mobile Streaming Guide

Stream from your phone with SRTLA

](https://irlserver.com/guides/mobile-streaming)

## Resources

[OBS Wiki](https://obsproject.com/wiki/) [IRLServer Discord](https://irlserver.com/discord)

---

Source: https://irlserver.com/imprint

# Impressum

Imprint / Legal Disclosure

## Angaben gemäß § 5 DDG

LEKANGER SOLUTIONS
Dalehaugen 2A
0657 Oslo
Norwegen

## Inhaber

Thomas Lekanger

## Kontakt

E-Mail: [mail@irlserver.com](mailto:mail@irlserver.com)

## Registereintrag

Eingetragen im norwegischen Unternehmensregister (Enhetsregisteret), geführt von den Brønnøysundregistrene.
Organisationsnummer (Org.nr.): 934 927 230

## Verantwortlich für den Inhalt nach § 18 Abs. 2 MStV

Thomas Lekanger
Anschrift wie oben

## Verbraucherstreitbeilegung

Wir sind nicht bereit und nicht verpflichtet, an Streitbeilegungsverfahren vor einer Verbraucherschlichtungsstelle teilzunehmen.

---

## Information pursuant to § 5 DDG

LEKANGER SOLUTIONS
Dalehaugen 2A
0657 Oslo
Norway

## Owner

Thomas Lekanger

## Contact

Email: [mail@irlserver.com](mailto:mail@irlserver.com)

## Company registration

Registered in the Norwegian Register of Legal Entities (Enhetsregisteret), maintained by the Brønnøysund Register Centre.
Organisation number (Org.nr.): 934 927 230

## Responsible for content per § 18 (2) MStV

Thomas Lekanger
Address as above

## Consumer dispute resolution

We are neither willing nor obliged to participate in dispute resolution proceedings before a consumer arbitration board.

---

Source: https://irlserver.com/pricing

# IRL Streaming Relay Pricing - Plans for Streamers | IRLServer

## CHOOSE YOUR PLAN

Simple pricing for professional streaming

POPULAR

### STANDARD

$9.99 /mo

RTMP, SRT & SRTLA relay endpoint

Custom SRTLA optimizations

Max input bitrate: 20Mb/s

Max resolution: Uncapped

Drop protection with NOALBS

No data caps or overage fees

Bring your own OBS, Streamlabs or vMix

IRLServer is a relay. You bring your own OBS (or Streamlabs, vMix) to receive your stream and go live to Twitch, YouTube or Kick.

[GET STARTED](https://irl.ac/)

### CUSTOM SOLUTIONS

Contact us

Need something special? We build custom IRL solutions for all kinds of streamers.

Custom IRL backpack setup

Multiple relay endpoints

Belabox®-compatible remote

Scene switching automation

Custom software development

White-label dashboard

[GET IN TOUCH](https://irlserver.com/discord)

ALL PLANS INCLUDE 24/7 SUPPORT • CANCEL ANYTIME

---

Source: https://irlserver.com/privacy

# Privacy Policy

Last updated: February 2, 2022

Our Privacy Policy governs the privacy terms of our website, located at IRLServer.com, and the tools we provide you (the "Website" or the "Service"). Any capitalized terms not defined in our Privacy Policy, have the meaning as specified in our Terms of Service accessible at [https://IRLServer.com/terms](https://irlserver.com/terms)

## Your Privacy

Our Website follows all legal requirements to protect your privacy. Our Privacy Policy is a legal statement that explains how we may collect information from you, how we may share your information, and how you can limit our sharing of your information. You will see terms in our Privacy Policy that are capitalized. These terms have meanings as described in the Definitions section below.

## Definitions

-   **Personal Data:** Personal Data means data about a living individual who can be identified from those data (or from those and other information either in our possession or likely to come into our possession).
-   **Usage Data:** Usage Data is data collected automatically either generated by the use of the Service or from the Service infrastructure itself (for example, the duration of a page visit).
-   **Cookies:** Cookies are small pieces of data stored on a User's device.
-   **Data Controller:** Data Controller means a natural or legal person who (either alone or jointly or in common with other persons) determines the purposes for which and the manner in which any personal data are, or are to be, processed. For the purpose of this Privacy Policy, we are a Data Controller of your data.
-   **Data Processors (or Service Providers):** Data Processor (or Service Provider) means any natural or legal person who processes the data on behalf of the Data Controller. We may use the services of various Service Providers in order to process your data more effectively.
-   **Data Subject:** Data Subject is any living individual who is the subject of Personal Data.
-   **User:** The User is the individual using our Service. The User corresponds to the Data Subject, who is the subject of Personal Data.

## Information Collection And Use

We collect several different types of information for various purposes to provide and improve our Service to you.

### Types of Data Collected

-   **Personal Data**

    While using our Service, we may ask you to provide us with certain personally identifiable information that can be used to contact or identify you ("Personal Data"). Personally identifiable information may include, but is not limited to: Email address, Name, Address, State, Province, ZIP/Postal code, City, Cookies and Usage Data.

    We may use your Personal Data to contact you with newsletters, marketing or promotional materials and other information that may be of interest to you. You may opt out of receiving any, or all, of these communications from us by following the unsubscribe link or instructions provided in any email we send.

-   **Usage Data**

    We may also collect information how the Service is accessed and used ("Usage Data"). This Usage Data may include information such as your computer's Internet Protocol address (e.g. IP address), browser type, browser version, the pages of our Service that you visit, the time and date of your visit, the time spent on those pages, unique device identifiers and other diagnostic data.

-   **Tracking & Cookies Data**

    We use cookies and similar tracking technologies to track the activity on our Service and hold certain information.

    Cookies are files with small amount of data which may include an anonymous unique identifier. Cookies are sent to your browser from a website and stored on your device. Tracking technologies also used are beacons, tags, and scripts to collect and track information and to improve and analyze our Service.

    You can instruct your browser to refuse all cookies or to indicate when a cookie is being sent. However, if you do not accept cookies, you may not be able to use some portions of our Service.

    Examples of Cookies we use: **session cookies** (we use these cookies to operate our Service) and **preference cookies** (we use these cookies to remember your preferences and various settings).

## Use of Data

We use the collected data for various purposes:

-   To provide and maintain our Service
-   To notify you about changes to our Service
-   To allow you to participate in interactive features of our Service when you choose to do so
-   To provide customer support
-   To gather analysis or valuable information so that we can improve our Service
-   To monitor the usage of our Service
-   To detect, prevent and address technical issues
-   To provide you with news, special offers and general information about other goods, services and events which we offer that are similar to those that you have already purchased or enquired about unless you have opted not to receive such information

## Retention of Data

We will retain your Personal Data only for as long as is necessary for the purposes set out in this Privacy Policy. We will retain and use your Personal Data to the extent necessary to comply with our legal obligations (for example, if we are required to retain your data to comply with applicable laws), resolve disputes, and enforce our legal agreements and policies.

We will also retain Usage Data for internal analysis purposes. Usage Data is generally retained for a shorter period of time, except when this data is used to strengthen the security or to improve the functionality of our Service, or we are legally obligated to retain this data for longer time periods.

## Transfer Of Data

Your information, including Personal Data, may be transferred to — and maintained on — computers located outside of your state, province, country or other governmental jurisdiction where the data protection laws may differ than those from your jurisdiction.

We will take all steps reasonably necessary to ensure that your data is treated securely and in accordance with this Privacy Policy and no transfer of your Personal Data will take place to an organization or a country unless there are adequate controls in place including the security of your data and other personal information.

Your consent to this Privacy Policy followed by your submission of such information represents your agreement to that transfer.

## Disclosure Of Data

-   **Business Transaction.** If we are involved in a merger, acquisition or asset sale, your Personal Data may be transferred. We will provide notice before your Personal Data is transferred and becomes subject to a different Privacy Policy.
-   **Disclosure for Law Enforcement.** Under certain circumstances, we may be required to disclose your Personal Data if required to do so by law or in response to valid requests by public authorities (e.g. a court or a government agency).

## Security Of Data

The security of your data is important to us, but remember that no method of transmission over the Internet, or method of electronic storage is 100% secure. While we strive to use commercially acceptable means to protect your Personal Data, we cannot guarantee its absolute security.

## Legal Basis for Processing Personal Data Under General Data Protection Regulation (GDPR)

IRLServer may process your Personal Data because:

-   We need to perform a contract with you
-   You have given us permission to do so
-   The processing is in our legitimate interests and it's not overridden by your rights
-   For payment processing purposes
-   To comply with the law

## Your Data Protection Rights Under General Data Protection Regulation (GDPR)

If you are a resident of the European Union (EU) and European Economic Area (EEA), you have certain data protection rights. IRLServer aims to take reasonable steps to allow you to correct, amend, delete, or limit the use of your Personal Data.

If you wish to be informed what Personal Data we hold about you and if you want it to be removed from our systems, please contact us.

In certain circumstances, you have the following data protection rights:

-   The right to access, update or to delete the information we have on you
-   The right of rectification
-   The right to object
-   The right of restriction
-   The right to data portability
-   The right to withdraw consent

## Contact Us

If you have any questions about this Privacy Policy, please contact us by email or by visiting our contact page.

---

Source: https://irlserver.com/terms

# Terms of Service

Last updated: June 6, 2026

These Terms of Service (the "Terms") govern your access to and use of IRLServer, including our website at irlserver.com, the streaming relay service, and any related tools (together, the "Service"). The Service is operated by LEKANGER SOLUTIONS (organisation number 934 927 230), a sole proprietorship registered in Norway ("IRLServer", "we", "us", or "our"). Full provider details are available in our [Imprint](https://irlserver.com/imprint).

By creating an account, subscribing, or otherwise using the Service, you agree to these Terms and to our [Privacy Policy](https://irlserver.com/privacy). If you do not agree, do not use the Service.

## 1\. The Service

IRLServer provides a streaming relay for live broadcasters. A paid subscription gives you a relay endpoint (RTMP, RTMPS, SRT, or SRTLA), access to our server regions, support for automatic scene switching via NOALBS, and a stats API for monitoring your stream. We may add, change, or remove features over time to improve or maintain the Service.

## 2\. Eligibility and accounts

You must be at least 16 years old to use the Service. If you are under 18, you may only use the Service with the consent of a parent or legal guardian, who must also authorise any payment method used.

You are responsible for keeping your account credentials secure and for all activity that occurs under your account. You must provide accurate information and keep it up to date. Notify us promptly of any unauthorised use of your account.

## 3\. Subscriptions and billing

The relay service is offered on a recurring subscription basis. Payments are processed by Stripe; we do not store your full card details. By subscribing, you authorise us (through Stripe) to charge the applicable fee for each billing period until you cancel.

Subscriptions renew automatically at the end of each billing period at the then-current price unless you cancel before the renewal date. You can upgrade or downgrade your plan at any time; changes take effect immediately and billing is prorated.

Prices are shown inclusive of any applicable taxes where required. We may change our prices, but a price change will only apply to you from your next billing period, and we will give you reasonable notice before it takes effect.

## 4\. Right of withdrawal and refunds

If you are a consumer, you may request a full refund of your initial subscription payment within 14 days of your first purchase, for any reason. To exercise this right, contact us at [mail@irlserver.com](mailto:mail@irlserver.com) within the 14-day period.

This 14-day money-back guarantee applies to your initial purchase only. Renewal payments for subsequent billing periods are non-refundable; to avoid a renewal charge, cancel before the renewal date. Nothing in this section limits any non-waivable rights you have under Norwegian or EU consumer law.

## 5\. Cancellation and termination

You may cancel your subscription at any time. Cancellation takes effect at the end of the current billing period, and you retain access to the paid Service until then.

We may suspend or terminate your access to the Service, with or without notice, if you breach these Terms, if your use poses a risk to the Service or other users, or if we are required to do so by law.

## 6\. Acceptable use

You agree that you will not:

-   use the Service to transmit content that is illegal, or that infringes the intellectual property, privacy, or other rights of any third party;
-   relay content you do not have the rights to broadcast, or content that violates the terms of the platform you stream to (for example Twitch, YouTube, or Kick);
-   resell, sublicense, or share your relay endpoint with third parties, or use a single subscription for more concurrent streams than your plan permits;
-   attempt to disrupt, overload, reverse-engineer, or gain unauthorised access to the Service or its infrastructure; or
-   use the Service to send spam, malware, or otherwise harm others.

## 7\. Your content and our role as host

You retain all rights to the streams and other content you transmit through the Service ("Your Content"). IRLServer acts only as a technical relay and hosting provider for Your Content; we do not monitor, control, or claim ownership of what you stream, and you are solely responsible for it.

As a hosting provider we are not liable for Your Content unless we have actual knowledge that specific content is illegal and fail to act. If you believe content transmitted through the Service is unlawful or infringing, contact us at [mail@irlserver.com](mailto:mail@irlserver.com) and we will review and, where appropriate, remove or disable access to it.

## 8\. Intellectual property

The Service, including the IRLServer name, logo, website content, and software, is owned by LEKANGER SOLUTIONS and protected by applicable intellectual property laws. We grant you a limited, non-exclusive, non-transferable, revocable licence to use the Service in accordance with these Terms. You may not copy, modify, or distribute any part of the Service without our written permission.

## 9\. Third-party services

The Service integrates with or relies on third parties, including Stripe for payments and the streaming platforms you broadcast to. We are not responsible for third-party services, and your use of them is governed by their own terms and privacy policies.

## 10\. Availability and disclaimers

We work to keep the Service reliable, but it is provided "as is" and "as available" without warranties of any kind, whether express or implied, including warranties of merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that the Service will be uninterrupted, error-free, or that it will meet your specific requirements. Maintenance, network conditions, and factors outside our control may affect availability. This section does not exclude any liability that cannot be excluded under applicable law.

## 11\. Limitation of liability

To the extent permitted by law, IRLServer will not be liable for any indirect, incidental, or consequential damages, or for lost profits, revenue, data, or goodwill, arising from your use of or inability to use the Service. Nothing in these Terms limits liability for death or personal injury caused by negligence, for fraud, or for any other liability that cannot be limited under Norwegian or EU law. If you are a consumer, your statutory rights are not affected.

## 12\. Changes to these Terms

We may update these Terms from time to time. If we make material changes, we will give you reasonable notice, for example by email or through the Service. Your continued use of the Service after changes take effect constitutes acceptance of the updated Terms.

## 13\. Governing law and dispute resolution

These Terms are governed by Norwegian law. If you are a consumer, you also benefit from any mandatory protections of the law of your country of residence, and mandatory rules determine the courts that may hear a dispute.

We are not obliged and have chosen not to participate in dispute resolution proceedings before a consumer arbitration board.

## 14\. Contact

If you have questions about these Terms, contact us at [mail@irlserver.com](mailto:mail@irlserver.com). Our full legal and contact details are listed in our [Imprint](https://irlserver.com/imprint).

---

Source: https://irlserver.com/tools

# FREE IRL TOOLS

Essential tools for streamers - completely free for everyone

[

POPULAR

### IRL Stream Calculator

Calculate streaming bandwidth usage based on bitrate, resolution, and duration. Plan your data needs.

](https://irlserver.com/tools/bitrate-calculator)

[

NEW

### NOALBS Config Generator

Generate config.json files for NOALBS automatic scene switching. Configure triggers, scenes, and chat commands.

](https://irlserver.com/tools/noalbs-config)

[

NEW

### Twitch OAuth Generator

Generate Twitch OAuth tokens for NOALBS chat bot integration. Full OAuth flow with proper scopes for chat commands.

](https://irlserver.com/tools/oauth-generator)

[

### Twitch Clip Player

Generate custom clip players for your Twitch clips. Perfect for BRB screens.

](https://brbscreen.com/)

[

### Belabox®-compatible Remote Control

Remote control interface compatible with Belabox devices. Manage settings from anywhere.

Belabox is a trademark of its respective owner. Not officially affiliated.

](https://remote.irl.ac/)

## RELATED GUIDES

[OBS Studio Setup](https://irlserver.com/guides/obs-setup) [Mobile Streaming](https://irlserver.com/guides/mobile-streaming) [Hardware Encoders](https://irlserver.com/guides/encoders) [NOALBS Setup](https://irlserver.com/guides/noalbs)

MORE TOOLS COMING SOON • [FOLLOW FOR UPDATES](https://x.com/irlserver)

---

Source: https://irlserver.com/tools/bitrate-calculator

# IRL Stream Calculator

Calculate bandwidth usage based on bitrate, resolution, and duration

4,500kbps

Resolution

720p 1080p 1440p 4K

The sweet spot for most IRL streamers

Quality Preset

Mobile

2.5 Mbps

Standard

4.5 Mbps

Quality

6.0 Mbps

Ultra

8.0 Mbps

Fine-tune Bitrate

4.5 Mbps

2 Mbps 10 Mbps

Stream Duration

3h

Streams / Week

4x

Recommended Connection

5G / Fast LTE

Per Stream

5.79 GB

3h @ 4.5 Mbps

REC

Monthly Estimate

100 GB

~17 streams/month

Weekly

23.17 GB

Yearly

1.2 TB

IRLServer Advantage: All plans include unlimited server bandwidth. These estimates help you plan your mobile data usage.

Formula

(kbps × hours × 3600) ÷ 8 ÷ 1024² = GB

## RELATED GUIDES

[

### Mobile Streaming Guide

Optimize bitrate for mobile SRTLA streaming

](https://irlserver.com/guides/mobile-streaming)[

### Hardware Encoders

Configure encoder bitrate settings

](https://irlserver.com/guides/encoders)[

### Use Cases

See how streamers use IRLServer

](https://irlserver.com/use-cases)[

### OBS Studio Setup

Configure OBS to receive your stream

](https://irlserver.com/guides/obs-setup)

---

Source: https://irlserver.com/tools/noalbs-config

# NOALBS Config Generator

Generate a config.json for NOALBS automatic scene switching. Based on the official NOALBS v2 configuration format.

[NOALBS GitHub](https://github.com/NOALBS/nginx-obs-automatic-low-bitrate-switching) [Download NOALBS](https://github.com/NOALBS/nginx-obs-automatic-low-bitrate-switching/releases)

## OBS WebSocket Connection

Host

Usually localhost for local OBS

Port

Default is 4455 for WebSocket 5.x

Password

Found in OBS → Tools → WebSocket Server Settings

## Stream Servers

Server #1(Primary)

ENABLED

Name

Server Type SRT Live Server (SRTLA) Belabox Cloud Nginx RTMP Node Media Server MediaMTX Nimble Streamer RIST WebSocket (push stats) Xiu

Stats URL

Get this from your IRLServer dashboard or server provider

Publisher

Format: live/stream/stream\_key

Priority

Lower number = higher priority

Add Another Server

## Switching Triggers

Low Bitrate (kbps)

At or below this, switch to the LOW scene. 0 disables it.

Offline Bitrate (kbps)

At or below this, switch to the BRB scene. Keep it under the Low bitrate, or the LOW scene never gets used. 0 disables it.

Low RTT (ms)

At or above this, switch to the LOW scene. 0 disables it.

Offline RTT (ms)

At or above this, switch to the BRB scene. Keep it over the Low RTT. 0 disables it.

Retry Attempts

Number of checks before switching scenes

## Scene Names

These must match your OBS scene names exactly (case sensitive)

Normal Scene

Low Bitrate Scene

Offline Scene

## Optional ScenesOptional

## Chat Integration

## Advanced Options

CONFIG.JSON

## Generated Configuration

{
  "user": {
    "id": null,
    "name": "NOALBSbot",
    "passwordHash": null
  },
  "switcher": {
    "bitrateSwitcherEnabled": true,
    "onlySwitchWhenStreaming": false,
    "instantlySwitchOnRecover": true,
    "autoSwitchNotification": true,
    "retryAttempts": 5,
    "triggers": {
      "low": 500,
      "rtt": 1000,
      "offline": 450,
      "rttOffline": 3500
    },
    "switchingScenes": {
      "normal": "LIVE",
      "low": "LOW",
      "offline": "BRB"
    },
    "streamServers": \[
      {
        "streamServer": {
          "type": "SrtLiveServer",
          "statsUrl": "https://your-stats-url.com/stats",
          "publisher": "live/stream/stream\_key"
        },
        "name": "IRLServer",
        "priority": 0,
        "overrideScenes": null,
        "dependsOn": null,
        "enabled": true
      }
    \]
  },
  "software": {
    "type": "Obs",
    "host": "localhost",
    "password": "",
    "port": 4455
  },
  "optionalScenes": {
    "starting": null,
    "ending": null,
    "privacy": null,
    "refresh": null
  },
  "optionalOptions": {
    "twitchTranscodingCheck": false,
    "twitchTranscodingRetries": 5,
    "twitchTranscodingDelaySeconds": 15,
    "offlineTimeout": null,
    "recordWhileStreaming": false,
    "switchToStartingSceneOnStreamStart": false
  }
}

Copy Download

Quick Setup:

1.  Download NOALBS from [GitHub releases](https://github.com/NOALBS/nginx-obs-automatic-low-bitrate-switching/releases)
2.  Create scenes in OBS: LIVE, LOW, BRB, REFRESH
3.  Enable WebSocket in OBS → Tools → WebSocket Server Settings
4.  Download this config.json and place it in NOALBS folder
5.  For chat: Create .env file with Twitch OAuth token
6.  Run NOALBS executable

IRLServer users: Your stats URL is available in the dashboard under Server Settings → Endpoints. Use the SrtLiveServer type for SRTLA endpoints.

Remember to update the WebSocket password and stats URLs with your actual values. Scene names must match your OBS scenes exactly.

## Related Resources

[NOALBS Setup Guide](https://irlserver.com/guides/noalbs) [OBS Setup Guide](https://irlserver.com/guides/obs-setup) [OAuth Token Generator](https://irlserver.com/tools/oauth-generator)

---

Source: https://irlserver.com/tools/oauth-generator

# Twitch OAuth Generator

Generate Twitch OAuth tokens for NOALBS chat commands. One click to authorize and get your token.

## Generate Twitch Token

For NOALBS chat bot integration

### Permissions Requested

`chat:read`

Read messages from your chat

`chat:edit`

Send messages to your chat

Authorize with Twitch

You will be redirected to Twitch to authorize. Your token is generated securely on our server.

### How It Works

1.  1\. Click the button above
2.  2\. Authorize on Twitch
3.  3\. Copy your token
4.  4\. Add to NOALBS .env file

### Using with NOALBS

Create a .env file in your NOALBS folder:

TWITCH\_BOT\_USERNAME=your\_username
TWITCH\_BOT\_OAUTH=oauth:xxx

Need to revoke a token?

[Manage Connections in Twitch Settings](https://www.twitch.tv/settings/connections)

## Related Resources

[NOALBS Setup Guide](https://irlserver.com/guides/noalbs) [NOALBS Config Generator](https://irlserver.com/tools/noalbs-config)

---

Source: https://irlserver.com/use-cases

# STREAMING USE CASES

Different streaming scenarios require different setups. Find the right configuration for your content style and get tips from experienced IRL streamers.

### Travel Streaming

Stream your adventures around the world. Our global server network ensures low latency wherever you go.

#### Key Features

-   Global server coverage (EU and US)
-   SRTLA bonding for unstable connections
-   Automatic scene switching when signal drops
-   Works with local SIM cards anywhere

#### Recommended Setup

Encoder:

Moblin (iOS) or Belabox

Bitrate:

3000-5000 kbps

Resolution:

1080p 30fps

#### Pro Tips

-   • Use SRTLA with multiple local SIM cards for best reliability
-   • Set conservative bitrate (3-4 Mbps) for developing countries
-   • Configure BRB scene with clip player for dead zones

### City Walking

Explore urban environments and share your city with viewers. Handle crowded areas with confidence.

#### Key Features

-   SRTLA bonding handles network congestion
-   Quick recovery from tall building interference
-   Low latency for real-time chat interaction
-   Drop protection keeps viewers engaged

#### Recommended Setup

Encoder:

Phone (Moblin/IRL Pro)

Bitrate:

4000-6000 kbps

Resolution:

1080p 30fps

#### Pro Tips

-   • Use multiple carriers - different networks perform better in different areas
-   • Enable instant recover in NOALBS for quick scene switches
-   • Consider 720p in very crowded events for stability

### Food & Restaurant Streams

Share culinary experiences from restaurants, markets, and food tours. Works great with venue WiFi.

#### Key Features

-   Hybrid WiFi + cellular for best reliability
-   Clean audio capture for ambient sounds
-   Scene overlays for menu/price info
-   Multi-destination to clip for VODs

#### Recommended Setup

Encoder:

Phone with gimbal

Bitrate:

5000-7000 kbps

Resolution:

1080p 30fps

#### Pro Tips

-   • Ask venue for WiFi password as backup connection
-   • Use directional mic attachment for better food audio
-   • Create restaurant info overlay scenes

### Events & Conventions

Cover conferences, conventions, and gatherings. Handle high-density network environments.

#### Key Features

-   Multi-SIM bonding essential for crowded venues
-   Works even when venue WiFi is overloaded
-   Low enough latency for interviews
-   Remote OBS control for scene switching

#### Recommended Setup

Encoder:

Belabox or IRLBox (hardware)

Bitrate:

3000-5000 kbps

Resolution:

1080p 30fps (720p backup)

#### Pro Tips

-   • Arrive early to test connections before crowds
-   • Use 4+ SIM cards from different carriers
-   • Have backup scene with recorded content ready
-   • Consider reducing resolution during peak hours

### Outdoor & Hiking

Stream from trails, parks, and natural environments. Handle spotty coverage with grace.

#### Key Features

-   Drop protection shows BRB in dead zones
-   Battery-efficient encoding options
-   Works with portable power solutions
-   Auto-reconnect when signal returns

#### Recommended Setup

Encoder:

Phone or lightweight encoder

Bitrate:

2500-4000 kbps

Resolution:

720p-1080p 30fps

#### Pro Tips

-   • Check coverage maps before planning routes
-   • Use external antenna for better reception
-   • Set NOALBS to show hiking map during drops
-   • Bring extra power banks (stream + encode uses power)

### Bike & Vehicle Streams

Stream while cycling, driving, or riding. Handle rapid cell tower handoffs smoothly.

#### Key Features

-   SRTLA handles fast cell tower switches
-   Low latency despite movement
-   Multiple connections for redundancy
-   Works with action cameras via HDMI

#### Recommended Setup

Encoder:

Action camera + Belabox

Bitrate:

4000-6000 kbps

Resolution:

1080p 30fps

#### Pro Tips

-   • Mount phone/encoder securely to reduce shake
-   • Use action camera for better stabilization
-   • Consider helmet or chest mount for POV
-   • Test routes beforehand for dead zones

### Multi-Camera Setup

Professional multi-camera productions for events, interviews, or elaborate setups.

#### Key Features

-   Multiple endpoints for different cameras
-   Scene switching between camera feeds
-   Works with video switchers
-   Low enough latency for live directing

#### Recommended Setup

Encoder:

Multiple encoders or switcher

Bitrate:

5000-8000 kbps per feed

Resolution:

1080p 30fps

#### Pro Tips

-   • Use separate endpoints for each camera
-   • Configure NOALBS to switch between camera scenes
-   • Consider dedicated hardware encoder per camera
-   • Use wired connections where possible

### Shopping & Mall Streams

Browse stores and share shopping experiences. Handle indoor cellular challenges.

#### Key Features

-   Indoor cellular support with bonding
-   Quick recovery from store transitions
-   Stable for talking to cameras/viewers
-   Works with mall WiFi as backup

#### Recommended Setup

Encoder:

Phone

Bitrate:

3000-5000 kbps

Resolution:

1080p 30fps

#### Pro Tips

-   • Mall WiFi can be good backup connection
-   • Stay near windows/entrances for better signal
-   • Lower bitrate in deep indoor areas
-   • Create overlay scenes for store info

## Ready to Start Streaming?

Get started with IRLServer and stream from anywhere in the world with confidence.

[Get Started](https://irl.ac/) [Setup Guides](https://irlserver.com/guides) [Bitrate Calculator](https://irlserver.com/tools/bitrate-calculator) [Compare Plans](https://irlserver.com/compare)

---

Source: https://irlserver.com/guides/best-irl-streaming-setup-twitch-kick

# The Best IRL Streaming Setup for Twitch and Kick in 2026

There is no single magic box for IRL streaming. The setups that hold up all share the same shape: bond your connections, send to a relay, broadcast from your own OBS, and let NOALBS cover the rough patches. Everything below is detail on those four moves.

Phone or encoder

bonded with SRTLA

Relay

near you, unlimited bandwidth

Your OBS

\+ NOALBS holds the broadcast

## 1\. Pick your encoder

This is what captures and sends your stream.

-   **Phone (easiest start).** Moblin on iPhone or IRL Pro on Android both bond connections with SRTLA. See [go live from iPhone](https://irlserver.com/guides/go-live-from-iphone) or [go live from Android](https://irlserver.com/guides/go-live-from-android).
-   **Belabox (dedicated rig).** A backpack box that bonds up to several modems and is built for serious field use. See [connect Belabox](https://irlserver.com/guides/connect-belabox), and remote control it from your phone with our setup.
-   **Hardware encoders (LiveU, IRLBox).** Covered in the [hardware encoders guide](https://irlserver.com/guides/encoders).

Start with a phone if you are new. You can grow into a backpack later.

## 2\. Bond more than one connection

A single connection is the thing that ends streams. Bond at least two (Wi-Fi plus cellular, or two SIMs on different carriers) so a dead one cannot take you down. [SRTLA bonding explained](https://irlserver.com/guides/srtla-bonding) covers why this is the foundation, and [why mobile signal drops](https://irlserver.com/guides/why-mobile-signal-drops-irl) covers what you are protecting against.

## 3\. Send to a relay near you

Your encoder bonds and sends to an SRTLA relay. Pick a region close to where you stream (Singapore, the US, the EU, or Scandinavia) for lower latency. A tuned relay with unlimited bandwidth is what turns a bonded connection into a stable feed.

## 4\. Broadcast from your own OBS

Pull the relay into your own OBS as a media source. **OBS is what connects to Twitch or Kick**, and it never moves, so the platform never sees your fragile field connection. This is the layer that stops [streams from ending](https://irlserver.com/guides/stop-streams-ending-twitch-kick).

## 5\. Add NOALBS for automatic scene switching

[NOALBS](https://irlserver.com/guides/noalbs) watches your bitrate and switches your OBS scene on its own: LOW when it dips, BRB when it drops, back to LIVE when it recovers. Your viewers see an intentional holding scene, not a frozen frame, and the broadcast keeps running.

## Why this beats streaming straight to the platform

Streaming a phone or encoder directly to Twitch ties your whole broadcast to one connection. The setup above breaks that dependency at every layer: bonding for a dead modem, the relay for a clean feed, your OBS for the platform session, and NOALBS for what is on screen. That is why it holds when you actually move.

[Build your setup on a tuned relay](https://irlserver.com/pricing)

If step 2 is the unfamiliar part, [SRTLA bonding explained](https://irlserver.com/guides/srtla-bonding) covers it in depth, and [keep your stream live when the signal drops](https://irlserver.com/guides/keep-stream-live-when-signal-drops) covers steps 4 and 5 together.

## FAQ

Do I need a backpack and a Belabox to IRL stream?

No. A phone with a bonding app (Moblin on iPhone, IRL Pro on Android) and two connections is a real setup. A Belabox is a step up for a dedicated rig, but it is not required to start.

Do I need OBS for IRL streaming?

For a reliable stream, yes. Your own OBS sits in front of Twitch or Kick and stays connected, so a rough field connection becomes a held scene instead of an ended broadcast.

Is the same setup good for both Twitch and Kick?

Yes. Your OBS is what connects to the platform, so the same rig streams to Twitch, Kick, or both with only the destination changed.

---

Source: https://irlserver.com/guides/connect-belabox

# How to Connect Belabox to Your Relay (with Remote Control)

A Belabox is the workhorse of a serious IRL rig. It bonds your modems, it is rugged, and it does not care that it is buried in a backpack. Two things make or break it: the relay it talks to, and how easily you can reach the box once it is sealed up and on your back.

SRTLA

bonded ingest

From your phone

live remote control

Global

SG · US · EU · Scandinavia

## Step 1: create your relay endpoint

In the dashboard, set up an SRTLA relay in the region nearest you. Copy three things: the host, the port, and the stream id.

New to the protocol? Start with [SRTLA bonding explained](https://irlserver.com/guides/srtla-bonding), then come back.

## Step 2: point the Belabox at the relay

On the Belabox:

1.  Set the streaming protocol to SRTLA.
2.  Paste in the relay host and port.
3.  Add the stream id.

That is the whole ingest setup. The box now knows where to send your bonded stream.

## Step 3: add SIMs and go live

Insert your modems and confirm each one connects. Start the stream. SRTLA spreads across every connection and our relay joins them back together on the other end. Walk around and watch it lean on different connections as your coverage changes. That movement is bonding doing its job.

Give it more than two connections if you can

Two SIMs is the minimum that earns the word bonded. A third connection gives SRTLA somewhere to go when you switch towers, which is exactly when two SIM rigs stutter.

## Step 4: turn on remote control

A Belabox already has a web interface you can open on its local IP, over any of its connections, as long as you are on the same network. The catch in the field is that you usually are not. Your connections are cellular modems and SIMs that nothing outside can reach, so the local web interface is not much help once you are out walking.

Remote control fixes that. We are one of the only options besides official Belabox cloud that lets you reach a Belabox from anywhere, not just the same network. We run an endpoint at [remote.irl.ac](https://remote.irl.ac/) that your box talks to instead of Belabox cloud.

SSH into the box. The web interface shows the username and password under _System_. Then run:

```
curl -fsSL https://remote.irl.ac/install.sh | sudo sh
```

The script comes from us with our address already in it, so it takes no arguments. The install does not modify the Belabox software itself, so it survives an `apt upgrade`, and `sudo bb-agent uninstall` puts the box back on Belabox cloud whenever you want.

Check that it took:

```
bb-agent status
```

You want `NODE_OPTIONS active` and a `preload loaded` line. The command exits non-zero if anything is wrong.

Now set a remote key. It links the box to the browser page. Either use the box's own web interface (`http://belabox.local`, then _Remote_), or run:

```
sudo bb-agent set-key my-secret-key
```

Any key works. You choose it, we do not issue it, and whoever knows it can control the encoder, so treat it like a password.

Then open `https://remote.irl.ac/?key=my-secret-key`. From your phone, while live, you can nudge the bitrate as your signal changes, restart the encoder if it gets unhappy, and adjust settings without ever opening the bag. Anyone else on your team who has the key can do the same, so a mod can fix a setting while you keep walking.

If the box will not connect

Run `bb-agent logs` and look for `DNS validation failure`. If it is there, run `sudo bb-agent set-dns-mode pin-all` and try again.

What remote control actually adds

The box is already reachable on its local web interface when you are on its network. Remote control adds the two things that matter in the field: reaching it from anywhere (not just the same WiFi or modem), and letting your whole team control it.

## Belabox cloud, or us?

If you already looked at official Belabox cloud, the side by side (regions, payment, support, what overlaps) is in [Belabox cloud vs IRLServer](https://irlserver.com/compare/belabox-cloud). Both are good. The right pick depends on where you stream and how you want to pay.

[Connect your Belabox](https://irlserver.com/pricing)

Once the box is bonded and you can reach it from your phone, pair it with [drop protection](https://irlserver.com/guides/keep-stream-live-when-signal-drops): your own OBS pulling the relay as a source, with NOALBS switching scenes so a rough feed never ends the broadcast.

## FAQ

Can I change settings on the Belabox while I am live?

Yes. With remote control linked you can change bitrate, restart the encoder, and adjust settings from your phone. You do not have to stop and open the backpack.

Do I need remote control if the Belabox already has a local web interface?

The local web interface works when you are on the same network as the box. In the field your connections are cellular modems you cannot reach from outside, so remote control is what lets you (and your team) reach the box from anywhere. We are one of the only options besides official Belabox cloud that offers it.

Which protocol should I pick on the Belabox?

SRTLA, so the box bonds across all your modems. Plain SRT works on a single connection, but then you lose the whole point of a bonded rig.

---

Source: https://irlserver.com/guides/connect-dji-osmo-pocket

# How to Stream from a DJI Osmo Pocket to Your Relay over RTMP

A DJI Osmo Pocket is a lot of camera for its size: gimbal-stabilised, pocketable, and good enough in low light to survive a night walk. What it is not is a streaming encoder. It has no SIM, no bonding, and no reconnect logic. DJI Mimo on your phone supplies all three jobs, and this guide points that at your own relay instead of at Twitch.

RTMP

what Mimo speaks

4-6 Mb/s

realistic on cellular

Your OBS

where the feed lands

## Step 1: create an RTMP endpoint

In the dashboard, create an RTMP relay endpoint in the region nearest to where you will be walking, not nearest to your house. Copy two values:

```
rtmp://rtmp.sfj.irl.ac:1935/live
```

and the stream key underneath it. Swap `sfj` for whichever region you picked — `fin`, `ord`, `hil` and `sgp` are the others. The endpoint works from all of them, so if you fly somewhere you change the region in the URL and nothing else.

## Step 2: pair the camera with DJI Mimo

Open DJI Mimo on your phone and connect the Pocket. Before you go near the livestream menu, decide what the phone is connected to. Mimo streams over whatever the phone has — WiFi, cellular, or a tethered modem — and the camera does not get a say.

If you are testing at home, do the first run on WiFi. Get a clean stream landing in OBS once, so that when it breaks later you know it is the network and not the setup.

## Step 3: choose custom RTMP and paste the relay

In Mimo, open the livestream function and pick the RTMP option — the one that takes a custom URL rather than a named platform. Paste the server URL in the address field, then the stream key.

Some Mimo builds want a single combined string instead of two fields. If you only get one box, join them with a slash:

```
rtmp://rtmp.sfj.irl.ac:1935/live/YOUR-STREAM-KEY
```

Type the key, do not trust autocorrect

Stream keys are long and case-sensitive, and a phone keyboard will happily capitalise the first character for you. If the stream refuses to start and the URL looks right, that is the first thing to check.

## Step 4: pick a bitrate you can hold

Mimo lets you set bitrate and resolution before you go live. The temptation is to pick the top option. Do not.

On cellular, 4 to 6 Mbps at 1080p is the band that survives walking. Higher numbers look better in a speed test and worse in a stream, because RTMP has no tolerance for a connection that briefly stops delivering. The moment the uplink cannot keep up, the stream does not degrade — it ends.

Start the stream. The relay accepts it immediately; there is nothing to enable on our side.

## Step 5: pull the feed into your own OBS

Your relay is a bridge, not a broadcaster. The finished show comes out of your OBS, which stays on a stable connection at home while the camera moves.

In OBS, add a **Media Source**, uncheck _Local File_, and paste the playback URL from your dashboard. The full walkthrough, including the buffering settings that matter, is in the [OBS setup guide](https://irlserver.com/guides/obs-setup).

## When direct RTMP is the wrong choice

Be honest about where you stream. Direct RTMP from Mimo is a good fit for one situation: a fixed spot with a connection you trust. A convention booth, a studio, a garden, an event with real WiFi.

It is a poor fit for the thing most people buy a Pocket for — walking around outside. RTMP was designed for a wired connection to a datacentre. It has no bonding, so you get one connection and no second chance, and it treats a two-second cellular gap as a fatal error.

The fix is not a better bitrate. It is a different protocol. Send the camera into [Moblin on your phone](https://irlserver.com/guides/dji-through-moblin) and let SRTLA carry it instead — same camera, same relay, a transport that expects the connection to be bad.

[Get an RTMP endpoint](https://irlserver.com/pricing)

Once the feed lands in OBS, add [drop protection](https://irlserver.com/guides/keep-stream-live-when-signal-drops) so a rough patch shows a BRB scene instead of ending your broadcast.

## FAQ

Does the Osmo Pocket stream on its own without a phone?

No. The camera has no cellular radio and no RTMP client of its own. DJI Mimo on your phone does the streaming, and the phone's connection carries it. The camera is the lens and the encoder; the phone is the uplink.

Why does my stream die when I walk out of WiFi?

Direct RTMP has no bonding and no gap tolerance. One dropped packet run and the connection ends. That is a property of RTMP, not of your relay. If you stream anywhere with patchy coverage, send the camera through Moblin instead and use SRTLA.

Which bitrate should I pick in Mimo?

On cellular, 4 to 6 Mbps. Mimo will happily offer more, and on a good tower it works, but the number you can hold while moving matters more than the number you can hit standing still.

Can I use H.265 to save bandwidth?

Our RTMP endpoints accept H.264 and H.265/HEVC. Whether your Pocket offers HEVC for livestreaming depends on the model and the Mimo build, so check the livestream menu rather than the camera's recording settings.

---

Source: https://irlserver.com/guides/connect-irl-pro

# How to Connect IRL Pro to Your Relay (Android SRTLA Setup)

IRL Pro is the go to streaming app for IRL on Android, with SRTLA bonding built in. The setup is four fields and a couple of toggles.

Android

IRL Pro

SRTLA

bonded connections

Global

SG · US · EU · Scandinavia

## Set up the stream

1.  Open IRL Pro and go to **Settings, Connections**.
2.  Add a new connection.
3.  Enter your relay details from the [dashboard](https://irl.ac/):
    -   Name: `IRL Pro`
    -   URL: `srtla://srt.<region>.irl.ac:5000/?streamid=live/stream/YOUR_KEY`

Pick the region nearest you. The dashboard shows your exact server and stream id.

## Bond your connections

Enable Wi-Fi and mobile data at the same time so IRL Pro spreads the stream across both. Add more interfaces if you have them. The more healthy connections SRTLA has, the better it rides out a dead one. More on how that works in [SRTLA bonding explained](https://irlserver.com/guides/srtla-bonding).

Two connections minimum

One connection is not bonding. Run at least two (Wi-Fi plus mobile data, or two SIMs) so a single dead link cannot take your feed down.

## Then bring it into OBS

IRL Pro sends your bonded stream to the relay. To broadcast it, pull the relay into your own OBS as a media source, then run NOALBS so OBS switches to a holding scene if the feed gets rough. The full OBS side is in the [OBS setup guide](https://irlserver.com/guides/obs-setup) and [NOALBS setup](https://irlserver.com/guides/noalbs).

That keeps the broadcast on Twitch or Kick even when the field connection wobbles, because OBS stays connected the whole time. See [keep your stream live](https://irlserver.com/guides/keep-stream-live-when-signal-drops) for the full picture.

[Get a relay for IRL Pro](https://irlserver.com/pricing)

On iPhone the equivalent app is [Moblin](https://irlserver.com/guides/connect-moblin).

## FAQ

Does IRL Pro support SRTLA bonding?

Yes. IRL Pro is the go to Android app for bonded IRL streaming. Enable Wi-Fi and mobile data at the same time, and add more interfaces if you have them.

Where do I get the server, port, and stream id?

From your IRLServer dashboard. It gives you the relay address, the port, and your stream id. Paste those into IRL Pro's stream settings.

What do I do with the stream after IRL Pro?

Pull the relay into your own OBS as a media source and run NOALBS for automatic scene switching. OBS is what broadcasts to Twitch or Kick.

---

Source: https://irlserver.com/guides/connect-irlbox

# How to Connect an IRLBox to Your Relay

IRLBox is an encoder operating system rather than a box we ship — it runs on small single-board machines and gives them features that used to need expensive hardware. This guide is about pointing one at a relay you control, so the finished broadcast comes out of your own OBS instead of going straight to a platform.

SRT · RTMP

what we take from it

irlbox.local

where you configure it

5 regions

one endpoint, all of them

## First, the honest part about bonding

IRLBox's own documentation lists its built-in protocols as **SRT, RTMP and RIST**. RIST is the one it leans on for bonding across several connections, and its docs make a detailed case for RIST over SRTLA.

We do not offer RIST today. So if you bought an IRLBox specifically for RIST link aggregation, we are not the relay for that part of your setup yet, and we would rather say so here than let you find out after checkout.

What we do serve well is everything else IRLBox does: a single connection over SRT or RTMP, delivered to a relay near you and handed to your own OBS. That is the setup below.

If your build has SRTLA available in Stream settings — some do, as an installed extra rather than a headline feature — then our SRTLA endpoints will take that too, and the [Belabox guide](https://irlserver.com/guides/connect-belabox) covers the shape of it.

## Step 1: create the endpoint

In the dashboard, create an **SRT** relay endpoint in the region nearest to where you will be streaming. You need the hostname, the port and the stream id:

```
srt://srt.sfj.irl.ac:4001?streamid=live/YOUR-STREAM-KEY
```

Regions are `sfj`, `fin`, `ord`, `hil` and `sgp`.

Prefer RTMP? Create an RTMP endpoint instead and use `rtmp://rtmp.sfj.irl.ac:1935/live` with the stream key underneath it. Everything after this step is the same.

## Step 2: open the IRLBox dashboard

Put the box on a network and open **`irlbox.local`** from a browser on that same network. Find **Stream settings** — the place where you would otherwise put a platform ingest URL.

## Step 3: pick the protocol and enter the relay

Select SRT (or RTMP). Then enter:

1.  Hostname: `srt.sfj.irl.ac`, with your region.
2.  Port: `4001` for SRT.
3.  Stream id: `live/YOUR-STREAM-KEY`.

Some builds take a single combined URL instead of separate fields. If so, paste the full form from step 1.

4001 is SRT, 5000 is SRTLA

If your build does offer SRTLA and you choose it, the port changes to 5000. Pointing one protocol at the other's port fails in an unhelpful way — it looks like a network problem rather than a wrong number. Check the port before you check anything else.

Save the profile, connect your camera, and start the stream.

## Step 4: pull it into OBS

Your relay is a bridge, not a broadcaster. The finished show comes out of your OBS, which stays on a stable connection at home.

In OBS, add a **Media Source**, uncheck _Local File_, and paste the playback URL from your dashboard. The settings that matter — buffering, and the checkboxes that let a stalled feed recover instead of freezing — are in the [OBS setup guide](https://irlserver.com/guides/obs-setup).

Confirm the input before you go live

Check the feed arrives and looks right in OBS on a connection you trust, before you put it in front of an audience on a connection you do not. Most setup problems are obvious at a desk and hard to diagnose on a street.

## Travelling with it

There is no region migration to request and no ticket to open. Your endpoint answers in every region we run, so flying to Singapore means changing `sfj` to `sgp` in the box's hostname. The stream id stays the same, your OBS keeps the same playback URL, and nothing on our side has to move.

[Get an SRT endpoint](https://irlserver.com/pricing)

Pair it with [drop protection](https://irlserver.com/guides/keep-stream-live-when-signal-drops) so NOALBS holds a BRB scene during a rough patch rather than letting the broadcast end.

## FAQ

Does IRLBox bond across its modems with SRTLA?

Not by default. IRLBox's own documentation lists SRT, RTMP and RIST as its built-in protocols, and RIST is what it uses for link aggregation. Some builds can install SRTLA as an extra, so if your Stream settings offer it, our SRTLA endpoints will take it. Do not assume it is there.

Do you support RIST?

Not yet. RIST is IRLBox's own answer to bonding and it is genuinely good at it, so if RIST bonding is the reason you bought the box, we are not the right relay for that today. Our SRT and RTMP endpoints work fine for a single connection, and RIST is something we are looking at.

Which region should I choose?

The one nearest the box, not the one nearest your OBS machine. The fragile half of the journey is the cellular hop from the box to us; the relay to your OBS runs over ordinary internet and tolerates distance far better.

Can I change region while travelling?

Yes, and there is nothing to migrate. Your endpoint answers in every region we run, so you edit the hostname in the box and keep the same stream id.

What bitrate should I set?

IRLBox advertises up to 30 Mbps upstream; our endpoints accept up to 20 Mb/s. Either way the number that matters is what your connection sustains while moving, which for most rigs is somewhere between 6 and 12 Mbps.

How is this different from a Belabox?

Mostly the bonding. A Belabox speaks SRTLA and hands the reassembly to the relay, which is exactly what our endpoints are built for. IRLBox is a RIST-first encoder OS. For a single connection the two are interchangeable from our side; for bonding they take different routes.

---

Source: https://irlserver.com/guides/connect-liveu-solo-pro

# How to Connect a LiveU Solo Pro to Your Relay over SRT

The [combined LiveU guide](https://irlserver.com/guides/connect-liveu) covers both units and is the right starting point if you are choosing between them. This page is the Solo Pro specifically, because the two things it adds over a Solo — SRT and HEVC — both need decisions the Solo never asks you for.

SRT

not SRTLA

2500 ms

latency to start at

HEVC

more picture per megabit

## First: LiveU bonds itself

This trips people up coming from a Belabox or an IRLBox. Those encoders hand the bonding problem to SRTLA and expect the relay to reassemble the pieces. LiveU does not. Its LRT layer bonds your modems inside the unit and emits one stream.

So there is no SRTLA to configure and no SRTLA endpoint to create. You want a plain **SRT** endpoint, and the Solo Pro will fill it with an already-bonded feed.

## Step 1: create an SRT endpoint

In the dashboard, create an SRT relay endpoint in the region nearest to where the unit will be, not nearest your OBS machine. You need the hostname, the port and the stream id:

```
srt://srt.sfj.irl.ac:4001?streamid=live/YOUR-STREAM-KEY
```

Regions are `sfj`, `fin`, `ord`, `hil` and `sgp`, and the endpoint answers in all of them, so travelling is a hostname edit rather than a migration.

## Step 2: add a custom SRT destination

In the LiveU Solo Portal, add a custom destination and choose **SRT**, in **caller** mode. Caller means the unit dials out to us — the only direction that works when the unit is on cellular and unreachable from outside.

Enter the hostname and port `4001` in their fields, and your stream id (`live/YOUR-STREAM-KEY`) in the stream id field. If the portal build you have offers only a single URL box, paste the full form above.

4001 is SRT, 5000 is SRTLA

The SRTLA port will not accept a plain SRT connection, and the failure looks like a network problem rather than a wrong number. If the destination refuses to connect and everything else looks correct, check the port first.

## Step 3: set the latency to 2500 ms

SRT's latency setting is a buffer: it is how long the protocol is allowed to hold a packet while asking for a missing one again. Too small and there is no time to retransmit, so SRT behaves like RTMP with extra steps.

Start at 2500 ms. LiveU is already doing its own recovery underneath, and the number needs to cover both that and the cellular jitter below it. Once you have a stream that holds up on a real walk, [SRT latency settings](https://irlserver.com/guides/srt-latency-settings-irl-streaming) explains what you are trading if you want to bring it down.

## Step 4: decide about HEVC

The Solo Pro can encode HEVC. At IRL bitrates that is a real gain — the same 6 Mbps carries visibly more detail than it does in H.264, which matters most in exactly the conditions IRL streams live in: motion, low light, and compression artefacts on faces.

The catch is the other end. Current OBS releases decode HEVC over SRT; older ones do not, and they fail silently with a black source rather than an error message. Test it at your desk before you rely on it in the field, and keep H.264 as the fallback if your studio machine is old.

Our SRT and RTMP endpoints accept both, so this is a decision about your OBS, not about the relay.

## Step 5: assign, go live, and pull it into OBS

Assign the destination to your unit and start streaming. On our side there is nothing to enable.

In your own OBS, add a **Media Source**, uncheck _Local File_, and paste the playback URL from the dashboard. The buffering and the checkboxes that let a stalled feed recover are covered in the [OBS setup guide](https://irlserver.com/guides/obs-setup).

Why not send LiveU straight to Twitch

You can, and for a single stable location it is fine. The reason to put a relay in the middle is your OBS: overlays, scene switching, and a connection to the platform that lives on a stable network at home rather than on the back of a bonded unit walking through a city.

[Get an SRT endpoint](https://irlserver.com/pricing)

Add [drop protection](https://irlserver.com/guides/keep-stream-live-when-signal-drops) so NOALBS shows a BRB scene during a rough patch instead of letting the broadcast end.

## FAQ

What does the Solo Pro do that the Solo does not?

SRT and HEVC. A LiveU Solo streams RTMP only, which means no gap tolerance and H.264 alone. The Solo Pro adds SRT, which recovers from brief losses instead of ending, and HEVC, which gets more picture out of the same bitrate. If you have a Pro, using it as an RTMP unit wastes both.

Do I configure SRTLA on a Solo Pro?

No. LiveU bonds with its own LRT layer inside the unit and sends you one already-bonded SRT stream. SRTLA is a different bonding scheme for encoders that do not have one. Point the Solo Pro at the SRT endpoint, not the SRTLA one.

Which SRT latency should I use?

Start at 2500 ms. That is enough room for LiveU's own recovery plus the cellular jitter underneath it. Lower values look attractive on paper and give SRT less room to retransmit, which is the thing you are paying for.

Will HEVC work in my OBS?

Current OBS releases decode HEVC over SRT. Older builds do not, and the failure is silent — a black source rather than an error. Test HEVC before you rely on it, and keep H.264 as the fallback if your studio machine is old.

Caller or listener mode?

Caller. The Solo Pro dials out to our relay, which is what you want on a cellular connection where nothing can dial in to the unit.

---

Source: https://irlserver.com/guides/connect-liveu

# How to Connect LiveU Solo and Solo Pro to Your Relay

LiveU encoders are a different animal from a Belabox or a phone. LiveU does its own bonding with its **LRT** layer, so it hands your relay a single, already bonded stream. That means you do not set up SRTLA on a LiveU. You just point it at the right endpoint.

The protocol depends on which unit you have.

Solo

RTMP only

Solo Pro

adds SRT

LRT

LiveU's own bonding

## How LiveU bonding differs

A Belabox or a phone app bonds with [SRTLA](https://irlserver.com/guides/srtla-bonding), which our relay reassembles. LiveU does not. Both LiveU Solos bond with LiveU's own LRT layer, on the device and through LiveU's service, and the result is a single stream. You send that single stream to our relay over RTMP or SRT. There is no SRTLA setting to configure on a LiveU.

## LiveU Solo (RTMP)

The Solo streams over RTMP.

1.  Create an **RTMP** endpoint in your [dashboard](https://irl.ac/) and copy the server URL and stream key.
2.  In the LiveU portal, add a **Custom RTMP** destination.
3.  Enter the relay details:
    -   Server: `rtmp://rtmp.<region>.irl.ac:1935/publish`
    -   Stream key: your key from the dashboard
4.  Assign it to your unit and start streaming.

## LiveU Solo Pro (SRT)

The Solo Pro adds SRT, which holds up better on a rough connection.

1.  Create an **SRT** endpoint in your dashboard and copy the details.
2.  In the LiveU portal, add a **Custom SRT** destination.
3.  Enter the relay details:
    -   Server: `srt://srt.<region>.irl.ac:4001`
    -   Stream id: `live/stream/YOUR_KEY`
    -   Latency: `2500ms` (recommended)
4.  Assign it to your unit and start streaming.

Pick the region nearest you

Your dashboard shows the exact server, key, and stream id, and lets you pick a region (Singapore, the US, Norway, or Finland). Closer is lower latency.

## Then broadcast from your own OBS

However your LiveU sends its stream, the broadcast layer is the same as every other rig. Pull the relay into your own OBS as a media source, and let OBS stay connected to Twitch or Kick while [NOALBS](https://irlserver.com/guides/noalbs) switches scenes when the feed gets rough. Full picture in [keep your stream live](https://irlserver.com/guides/keep-stream-live-when-signal-drops).

[Get a relay for your LiveU](https://irlserver.com/pricing)

Worth knowing if you have not bought the rig yet: LRT bonding is an ongoing cost on top of the LiveU hardware, because the bonding runs through LiveU's service. SRTLA bonding is not billed separately, it is part of the relay. A [Belabox](https://irlserver.com/guides/connect-belabox) or a bonding phone app takes that route, and adds remote control on top.

## FAQ

Does LiveU support SRTLA bonding?

No. LiveU does its own bonding with its LRT layer on both the Solo and Solo Pro. It does not use SRTLA. LiveU bonds your connections itself, then sends a single stream to your relay, so you do not configure SRTLA on a LiveU.

Which protocol does each LiveU use?

The LiveU Solo streams over RTMP only. The LiveU Solo Pro adds SRT, which is the better choice for an unpredictable connection. Pick an RTMP endpoint for a Solo and an SRT endpoint for a Solo Pro.

Do I still need OBS with a LiveU?

Yes, for a reliable broadcast. LiveU sends to your relay, and your own OBS pulls that in and stays connected to Twitch or Kick, with NOALBS holding a scene when the feed gets rough.

---

Source: https://irlserver.com/guides/connect-moblin

# How to Connect Moblin to Your Relay (iPhone SRTLA Setup)

Moblin is the go to streaming app for IRL on iPhone, and one of the few iOS apps that bonds multiple connections with SRTLA. The setup is four fields and a couple of toggles.

iPhone

Moblin (iOS)

SRTLA

bonded connections

Global

SG · US · EU · Scandinavia

## Set up the stream

1.  Open Moblin and go to **Settings, Stream**, then add a new stream.
2.  Set the protocol to **SRTLA** so Moblin can bond your connections.
3.  Enter your relay details from the [dashboard](https://irl.ac/):
    -   Server: `srt.<region>.irl.ac`
    -   Port: `5000`
    -   Stream id: `live/stream/YOUR_KEY`

Pick the region nearest you. The dashboard shows your exact server and stream id.

## Bond your connections

Enable Wi-Fi and cellular at the same time so Moblin spreads the stream across both. Add more modems if you have them. The more healthy connections SRTLA has, the better it rides out a dead one. More on how that works in [SRTLA bonding explained](https://irlserver.com/guides/srtla-bonding).

Two connections minimum

One connection is not bonding. Run at least two (Wi-Fi plus cellular, or two SIMs) so a single dead link cannot take your feed down.

## Then bring it into OBS

Moblin sends your bonded stream to the relay. To broadcast it, pull the relay into your own OBS as a media source, then run NOALBS so OBS switches to a holding scene if the feed gets rough. The full OBS side is in the [OBS setup guide](https://irlserver.com/guides/obs-setup) and [NOALBS setup](https://irlserver.com/guides/noalbs).

That keeps the broadcast on Twitch or Kick even when the field connection wobbles, because OBS stays connected the whole time. See [keep your stream live](https://irlserver.com/guides/keep-stream-live-when-signal-drops) for the full picture.

[Get a relay for Moblin](https://irlserver.com/pricing)

On Android the equivalent app is [IRL Pro](https://irlserver.com/guides/connect-irl-pro).

## FAQ

Does Moblin support SRTLA bonding?

Yes. Moblin is one of the iOS apps that bonds multiple connections with SRTLA. Enable Wi-Fi and cellular at the same time, and add more modems if you have them.

Where do I get the server, port, and stream id?

From your IRLServer dashboard. It gives you the relay address, the port, and your stream id. Paste those into Moblin's stream settings.

What do I do with the stream after Moblin?

Pull the relay into your own OBS as a media source and run NOALBS for automatic scene switching. OBS is what broadcasts to Twitch or Kick.

---

Source: https://irlserver.com/guides/dji-through-moblin

# How to Use a DJI Camera with Moblin for Bonded IRL Streaming

A DJI camera gives you a better picture than a phone lens. A phone gives you connections a camera does not have. Moblin is how you get both: the camera supplies the image, the phone supplies the uplink, and SRTLA bonds that uplink across everything the phone can reach.

SRTLA

bonded transport

Cellular + WiFi

used at the same time

Bluetooth

how Moblin drives the camera

## Why this beats streaming from the camera directly

[Streaming a DJI camera straight over RTMP](https://irlserver.com/guides/connect-dji-osmo-pocket) works, and for a fixed location it is the simpler setup. It falls apart while walking, for a reason that has nothing to do with your gear: RTMP runs over a single TCP connection, and it treats a stalled connection as a dead one.

SRTLA is built the other way around. It expects connections to be unreliable, so it spreads the stream across all of them and keeps going when one drops. Your phone has cellular. It probably also has WiFi in range some of the time. SRTLA uses both, at once, and shifts weight between them as coverage changes.

Moblin is what turns your phone into that bonded encoder — and, usefully, it drives the camera for you.

## Step 1: create an SRTLA endpoint

In the dashboard, create an SRTLA relay endpoint in the region nearest to where you will be streaming. You need the host, the port, and the stream id:

```
srtla://srt.sfj.irl.ac:5000
```

with a stream id shaped like `live/YOUR-STREAM-KEY`. The regions are `sfj`, `fin`, `ord`, `hil` and `sgp`, and your endpoint answers on all of them — travelling means editing the hostname, not moving anything.

New to the protocol? [SRTLA bonding explained](https://irlserver.com/guides/srtla-bonding) covers what it is actually doing before you configure it.

## Step 2: add the relay to Moblin

In Moblin, add a new stream and choose SRTLA as the protocol. Enter the URL with the stream id included:

```
srtla://srt.sfj.irl.ac:5000/live/YOUR-STREAM-KEY
```

Leave the latency at Moblin's default for the first run. Tune it later, once you know the stream works — [SRT latency settings](https://irlserver.com/guides/srt-latency-settings-irl-streaming) explains what you are trading when you change it.

## Step 3: turn on Moblin's RTMP server

This is the piece people miss. Moblin does not just _see_ the camera — it runs its own RTMP server on the phone, and the camera publishes into it.

In Moblin's settings, enable the **RTMP server** and create a stream inside it. That stream gets its own key, and Moblin builds the publish URL from the phone's WiFi address, the server port and that key. If you skip this, the DJI screen will tell you there are no RTMP server streams to pick.

Leave the address on automatic

Moblin can work out the RTMP URL itself from the phone's WiFi IPv4 address, so there is nothing to type. That also means the phone has to be on WiFi for it to have an address to hand out — on cellular alone there is nothing for the camera to connect to.

## Step 4: pair the camera over Bluetooth

Under DJI devices in Moblin, add the camera and let it scan. Pairing happens over **Bluetooth**, and from then on Moblin configures the camera directly — you do not open DJI Mimo at any point.

Moblin asks for three things:

1.  **The WiFi network** the camera should join, by SSID and password. This is the network the camera uses to reach the phone's RTMP server, so it has to be one both devices are on.
2.  **Where to publish.** Pick _Server_ and choose the RTMP server stream you made in step 3. _Custom_ is there if you want to type a URL by hand.
3.  **How to encode.** Resolution, frame rate, bitrate, codec, and image stabilisation on the models that offer it.

Moblin's defaults are sensible: 1080p, 30 fps, 6 Mbps, H.265/HEVC. The settings screen warns that high bitrates may be unstable, and it is right — this hop is local, but every bit you feed Moblin is a bit it has to re-send over cellular. Keep it near what you intend to stream out.

You will see the camera walk through discovering, pairing, connecting, setting up WiFi, configuring, and then preparing to stream. There is also an **auto-restart live stream when broken** option, which is worth having on for a rig you cannot reach mid-walk.

Test the local hop before the internet hop

Get the DJI feed showing inside Moblin first, without starting the stream to the relay. If the camera is not arriving locally, no amount of relay configuration will help, and it is much easier to diagnose one problem at a time.

## Step 5: turn on every connection and go live

In Moblin, enable cellular and WiFi together. This is the entire point of the exercise — with one connection enabled, SRTLA is doing nothing that plain SRT would not do.

Then start the stream. On our side the relay accepts it as soon as it arrives.

In your own OBS, add a **Media Source** and paste the playback URL from the dashboard. The [OBS setup guide](https://irlserver.com/guides/obs-setup) walks through the buffering settings, which matter more here than they do on a wired feed.

Where each piece is doing its job

The DJI camera is the lens. Moblin is the encoder, the bonding layer, and the thing configuring the camera. The relay is the bridge. Your OBS is the studio and the thing actually talking to Twitch or Kick. If any one of those is doing two jobs, that is usually the part that breaks.

[Get an SRTLA endpoint](https://irlserver.com/pricing)

Add [NOALBS drop protection](https://irlserver.com/guides/keep-stream-live-when-signal-drops) on top and a bad stretch of coverage becomes a BRB scene rather than an ended broadcast.

## FAQ

Why put Moblin between the camera and the relay at all?

Bonding. A DJI camera streaming on its own sends RTMP over one connection, and one connection is one point of failure. Moblin receives the camera on its own local RTMP server, then sends the result over SRTLA across every connection your phone has. The camera keeps being a camera; Moblin becomes the encoder.

Do I need the DJI Mimo app for this?

No. Moblin talks to the camera directly over Bluetooth and sets the WiFi network, the RTMP destination, the resolution, the frame rate, the bitrate, the codec and (on models that support it) image stabilisation. Mimo is not in the path at all. Keep it installed for firmware updates and leave it closed.

Does this add latency?

A little. You are adding a local hop and an SRTLA latency buffer, so budget a couple of seconds more end to end than direct RTMP. In exchange, a two-second cellular gap becomes a recoverable event instead of the end of your stream.

Which DJI cameras work?

Moblin lists the Osmo Pocket 3 and Pocket 4, the Osmo Action 2, 3, 4, 5 Pro and 6, and the Osmo 360. Image stabilisation is only offered on the Action 4, 5 Pro and 6 and the Osmo 360 — the Pocket models handle it themselves.

Is Moblin iPhone only?

Yes, Moblin is an iOS app. On Android the equivalent route is IRL Pro, which also speaks SRTLA to the same endpoint.

---

Source: https://irlserver.com/guides/go-live-from-android

# How to Go Live IRL From Your Android Phone in 2026

A modern Android phone is already a capable camera and encoder, so the backpack full of gear is optional. What the phone cannot do alone is survive a walk across a city. That takes four things around it: a bonding app, more than one connection, a relay, and your own OBS.

IRL Pro

bonding app (Android)

2+

connections bonded

Your OBS

broadcasts to Twitch/Kick

## 1\. Get a bonding app

The app matters. You want one that bonds multiple connections with SRTLA, so a single dead modem cannot end your stream. On Android that is **IRL Pro**, the go to IRL app. Larix can stream too, but it does not do SRTLA bonding, so it is single connection only.

## 2\. Line up more than one connection

Bonding needs something to bond. Enable Wi-Fi and mobile data together, and add another SIM or modem if you have one. Two connections is the floor. More gives SRTLA somewhere to go when you switch towers or walk into a weak spot.

## 3\. Point IRL Pro at a relay

IRL Pro sends your bonded stream to an SRTLA relay. The exact steps (protocol, server, port, stream id) are in [connect IRL Pro to your relay](https://irlserver.com/guides/connect-irl-pro). Pick a relay region near you for lower latency.

## 4\. Broadcast from your own OBS

This is the step that keeps the stream alive. Your own OBS pulls the relay in as a media source, and OBS is what stays connected to Twitch or Kick. When the field connection wobbles, [NOALBS](https://irlserver.com/guides/noalbs) switches OBS to a holding scene instead of ending the broadcast.

The phone is not the only piece

A common mistake is streaming straight from the phone to Twitch. That ties your whole broadcast to one connection. The relay plus your own OBS is what turns a phone into a stream that holds when you move. Full walk through in [keep your stream live](https://irlserver.com/guides/keep-stream-live-when-signal-drops).

[Get a relay for your Android phone](https://irlserver.com/pricing)

The iPhone version of this walkthrough uses [Moblin](https://irlserver.com/guides/go-live-from-iphone) in place of IRL Pro.

## FAQ

Can I IRL stream straight from the Android camera?

Yes. With a bonding app like IRL Pro, your Android phone is the camera and encoder. You do not need a separate capture device for a basic mobile rig.

Do I need OBS if I am streaming from a phone?

For a reliable IRL stream, yes. The phone sends to a relay, and your own OBS pulls that in and broadcasts to Twitch or Kick, with NOALBS holding a scene when the feed drops. That OBS layer keeps the broadcast from ending.

Why not just stream straight to Twitch from the phone?

Because then the broadcast is tied to one connection. Lose it and Twitch ends the stream. Sending to a relay and broadcasting from OBS is what makes a mobile IRL stream hold together.

---

Source: https://irlserver.com/guides/go-live-from-iphone

# How to Go Live IRL From Your iPhone in 2026

You do not need a backpack full of gear to IRL stream. A modern iPhone is a capable camera and encoder on its own. What turns it into a stream that survives a walk through a city is the setup around it: a bonding app, more than one connection, a relay, and your own OBS.

Moblin

bonding app (iOS)

2+

connections bonded

Your OBS

broadcasts to Twitch/Kick

## 1\. Get a bonding app

The app matters. You want one that bonds multiple connections with SRTLA, so a single dead modem cannot end your stream. On iPhone that is **Moblin**, the go to IRL app on iOS. Larix can stream too, but it does not do SRTLA bonding, so it is single connection only.

## 2\. Line up more than one connection

Bonding needs something to bond. Enable Wi-Fi and cellular together, and add another SIM or modem if you have one. Two connections is the floor. More gives SRTLA somewhere to go when you switch towers or walk into a weak spot.

## 3\. Point Moblin at a relay

Moblin sends your bonded stream to an SRTLA relay. The exact steps (protocol, server, port, stream id) are in [connect Moblin to your relay](https://irlserver.com/guides/connect-moblin). Pick a relay region near you for lower latency.

## 4\. Broadcast from your own OBS

This is the step that keeps the stream alive. Your own OBS pulls the relay in as a media source, and OBS is what stays connected to Twitch or Kick. When the field connection wobbles, [NOALBS](https://irlserver.com/guides/noalbs) switches OBS to a holding scene instead of ending the broadcast.

The phone is not the only piece

A common mistake is streaming straight from the phone to Twitch. That ties your whole broadcast to one connection. The relay plus your own OBS is what turns a phone into a stream that holds when you move. Full walk through in [keep your stream live](https://irlserver.com/guides/keep-stream-live-when-signal-drops).

[Get a relay for your iPhone](https://irlserver.com/pricing)

The Android version of this walkthrough uses [IRL Pro](https://irlserver.com/guides/go-live-from-android) in place of Moblin.

## FAQ

Can I IRL stream straight from the iPhone camera?

Yes. With a bonding app like Moblin, the iPhone is your camera and encoder. You do not need a separate capture device for a basic mobile rig.

Do I need OBS if I am streaming from a phone?

For a reliable IRL stream, yes. The phone sends to a relay, and your own OBS pulls that in and broadcasts to Twitch or Kick, with NOALBS holding a scene when the feed drops. That OBS layer is what keeps the broadcast from ending.

Why not just stream straight to Twitch from the phone?

Because then the broadcast is tied to one connection. Lose it and Twitch ends the stream. Sending to a relay and broadcasting from OBS is what makes a mobile IRL stream hold together.

---

Source: https://irlserver.com/guides/irl-stream-without-a-pc

# How to IRL Stream Without a PC at Home

Every other setup guide on this site ends the same way: pull the relay into your own OBS. That instruction quietly assumes a PC at home, powered on and stable for the entire time you are out walking. If you do not own one, or do not want to leave one running unattended, that whole architecture is closed to you.

No PC

nothing at your house

Phone only

Moblin or IRL Pro

Up to 3

destinations at once

## Why the usual setup needs a PC

The relay architecture works because your own OBS is the thing connected to Twitch or Kick. Your phone bonds its connections and sends to the relay, the relay hands OBS a clean feed as a media source, and OBS holds the platform session no matter what your field connection does.

That is genuinely the right answer for most people, and it is cheaper. It just has a hard requirement in the middle of it: a machine at home doing the compositing, which has to survive the whole broadcast without you there to fix it.

## What replaces it

Stage moves that machine into our cloud. Your phone sends to an ingest, Stage does the compositing that OBS would have done, and Stage hands the finished picture to your destinations. Nothing in the chain lives in your flat.

It is not a rented cloud OBS. There is no desktop to log into, no plugins to install, and no instance for you to keep alive. You configure it from Discord while you are moving, or from your browser at a desk.

## Getting your phone into it

Stage comes with its own ingest, so there is no separate relay to point at first.

1.  In Discord, run `/ingest info` with `format: moblin` or `format: irlpro`. It replies with a QR code.
2.  Scan it. The app imports the bonded SRTLA URL directly, with plain SRT kept as a backup connection.
3.  On anything that is not a phone, including a Belabox or a LiveU, run the same command without a format and paste the SRTLA or SRT URL into the encoder by hand.

Bonding still matters here

Removing the PC does not remove the need to bond. Your phone is still on cellular, and a single connection still dies under a bridge. Run at least two so [SRTLA](https://irlserver.com/guides/srtla-bonding) has somewhere to go.

## Adding destinations

`/destinations create` adds Twitch, Kick, or any custom RTMP or SRT address. Three can run at the same time. Kick uses a per-user address you copy from your own Kick settings rather than a shared one.

## What a dropout looks like

Stage watches your actual bitrate and round trip time rather than waiting for the connection to die outright. When the feed degrades it holds your picture with an unstable badge; when it drops far enough it cuts to your fallback scene, and it cuts back when you recover.

The fallback starts as a text card. Replace it with your own art using `/fallback image`, or a looping clip with `/fallback video`, attaching the file to the command itself. `/fallback ingest` goes further and makes a second encoder the fallback source, so a backup phone takes over instead of a still image.

By default it will keep broadcasting that fallback for a long time before giving up. `/fallback timeout` sets how long in minutes, where zero means keep going until you stop it.

## What you give up

This is the part worth being straight about, because it is where Stage is the wrong answer:

-   No plugins, no VSTs, no Stream Deck, and no remote desktop into the machine.
-   No capture card or webcam at your house feeding in, since there is no machine there. A rented cloud OBS cannot do this either.
-   Sessions run 24 hours by default, and an instance with nothing streaming into it shuts down after ten minutes idle. Your scenes, destinations and ingest URL survive that and come back on restart. If you need to stay live longer than a day, ask and we will raise the cap.

If any of those are load-bearing for your show, the relay plus your own OBS is the better setup and you should stay on it.

## What it costs

Stage is $45 a month and bundles an ingest. If you already pay $9.99 for an endpoint, the real difference is $35 a month, because the endpoint is included rather than charged twice. Stage+ is $65 and adds more tracks.

Stage is in early access and invite only, so there is no self-serve checkout yet. You request access and we open it.

[See what Stage does](https://irlserver.com/stage)

If you do have a PC and it is reliable, the cheaper path is worth reading first: [keep your stream live when the signal drops](https://irlserver.com/guides/keep-stream-live-when-signal-drops) is the relay and own-OBS version of the same problem.

## FAQ

Can I IRL stream with no computer at all?

Yes, if the compositing happens somewhere other than your house. A phone alone can send a stream to Twitch, but then the broadcast is tied to your field connection and ends when that connection does. Stage runs the compositing in our cloud, so there is no PC at home and no local OBS to crash.

Do I still need OBS?

Not at home. Stage does the work OBS would normally do: overlays, alerts, your BRB screen, filters. There is nothing to install, update or restart.

Is a relay enough on its own if I have no PC?

No. A relay hands you a clean bonded feed, but something still has to composite it and stay connected to the platform, and in the relay setup that something is your own OBS. Without a PC you need the compositing hosted, which is what Stage does.

---

Source: https://irlserver.com/guides/keep-stream-live-when-signal-drops

# How to Keep Your IRL Stream Live When the Signal Drops

There are two ways an IRL stream dies. A link drops (one modem browns out), or every link fills up at once (you walk into a dead zone). A reliable rig has an answer for both, and the answer is not "hope." It is an architecture where the thing connected to Twitch never has to care about your field connection.

Bonded

survives a dead link

Your OBS

always on the platform

NOALBS

auto BRB scene

## Why streams end instead of holding

If your encoder streams straight to Twitch or Kick, the broadcast is tied to that one connection. The moment a field link drops, the platform sees the source disappear and ends the session. Viewers get kicked, the VOD splits.

The fix is to put a local OBS between your field rig and the platform. Your encoder sends to a relay, the relay feed becomes a media source in your OBS, and OBS is what stays connected to Twitch or Kick. Now a wobble in the field is just a media source going quiet, not the platform losing its source.

## Layer 1: bond your links with SRTLA

A single connection has a single point of failure. Bonding removes it.

Run an [SRTLA](https://irlserver.com/guides/srtla-bonding) capable encoder across two or more connections (SIMs, a wired modem, Wi-Fi). The stream rides all of them at once. Lose one and the others carry the load. No gap, no restart. This is the layer that survives the bridge, the elevator, switching towers.

## Layer 2: send to the relay, pull it into your own OBS

The relay joins your bonded connections back into one clean feed. You add that relay as a media source in your own local OBS, so you keep full control of your scenes, overlays, and alerts.

Two things make our relay worth pointing at:

-   Custom SRTLA tuning, not the plain open source defaults. It is built to ride out a rough connection, the difference between a quick stutter and a long freeze.
-   Global servers (Singapore, the US, the EU, and Scandinavia) with unlimited bandwidth, so you connect to one near wherever you are streaming.

This is the layer most setups skip

Plenty of rigs bond at the encoder and then send straight to the platform. The bonding looks great in a speed test and the stream still ends in the field, because there was nothing holding the platform session when a link dropped. Local OBS in the middle is what turns a drop into a held scene.

## Layer 3: auto switch scenes with NOALBS

When you hit a genuine dead zone, your encoder's adaptive bitrate lowers quality to keep moving. If it gets bad enough that the feed stutters or stops, something should cover it on screen. That is NOALBS.

[NOALBS](https://irlserver.com/guides/noalbs) watches your incoming bitrate and switches your OBS scene automatically:

-   Bitrate dips: it switches to a LOW scene built for a rough feed.
-   Bitrate collapses: it switches to a BRB scene and holds there.
-   Bitrate recovers: it switches you back to LIVE.

NOALBS does scene switching, not bitrate. Your encoder handles bitrate, NOALBS handles what the viewer sees. Because OBS never disconnects from the platform, the session simply never ends. Pair the BRB scene with a clip player so viewers get highlights instead of a frozen frame.

## Which layer covers what

The three get confused constantly, so it is worth being blunt about the division of labour. Bonding handles lost links. Your local OBS holds the platform session. NOALBS handles what is on screen when the feed goes rough. Skip any one of them and you have left a specific failure uncovered: a dead modem, an ended broadcast, or a frozen frame.

[Get a relay built for IRL](https://irlserver.com/pricing)

On a Belabox rig, the [connect Belabox guide](https://irlserver.com/guides/connect-belabox) walks the SRTLA setup plus remote control, so you can fix a misbehaving box without stopping to dig it out of the backpack.

## FAQ

Why does my IRL stream keep ending instead of just showing a holding screen?

Usually because the encoder is connected straight to Twitch or Kick. When the field link drops, the platform sees the source vanish and ends the broadcast. The fix is to run a local OBS that pulls the relay as a media source. OBS stays connected to the platform, and NOALBS swaps to a BRB scene when the feed drops, so the session never ends.

Will bonding alone stop every drop?

No. Bonding survives a dead modem. When every link is full at once, your encoder's own adaptive bitrate lowers quality and NOALBS switches to a holding scene. Bonding covers lost links, NOALBS covers a feed that goes bad.

Does this work on both Twitch and Kick?

Yes. Your local OBS is what is connected to the platform, so the same setup keeps the broadcast alive on Twitch, Kick, or wherever OBS is streaming.

---

Source: https://irlserver.com/guides/multistream-twitch-kick-youtube

# How to Multistream to Twitch, Kick and YouTube at Once

Your field rig already sends one feed to one ingest, and that part does not change when you add platforms. Multistreaming is a question about the other end of the chain: which machine makes the copies, and what that machine costs you.

One in

single bonded uplink

Three out

simultaneous destinations

1080p60

encoded once

## Where the fan-out happens

There are two places it can live, and the choice is mostly about what hardware you already have.

**Your own OBS.** If you run the relay setup, OBS is already the thing connected to the platform, so adding outputs there is the obvious move. Nothing extra to subscribe to beyond the $9.99 endpoint. The cost is borne by your PC and your home upload: every additional output is another encode and another outbound stream from your house, so a machine that comfortably handled one destination will not automatically handle three.

**A compositor in the cloud.** Stage takes your single bonded feed, encodes it once at 1080p60, and pushes it to three destinations from our side. Your home connection is not in the path at all, so the number of destinations stops being your problem.

Neither is the clever answer. If you have a PC that is already up and has upload headroom, fanning out there is cheaper and you should do that. If you do not have that machine, or do not want it running unattended while you are out, [streaming without a PC](https://irlserver.com/guides/irl-stream-without-a-pc) covers the other route.

## Setting up destinations on Stage

`/destinations create` in Discord adds each one. Three can run at once on Stage and Stage+, and ten on the Custom tier.

-   **Twitch** and **YouTube** use their standard ingest addresses.
-   **Kick** uses an address tied to your own account, which you copy out of your Kick settings rather than getting from us.
-   **Custom** accepts any `rtmp://`, `rtmps://` or `srt://` target, which covers everything else.

Three is a real cap, not a soft one

Stage and Stage+ both stop at three simultaneous destinations. If you need more than that, the Custom tier is the one that goes to ten. It is worth checking that against your actual list before you plan around it.

## Enhanced Broadcasting, and where it applies

Stage+ adds Enhanced Broadcasting, which sends several bitrates rather than one. The point is viewers on weak connections: instead of buffering against a single 1080p60 output, they drop to a lower rung. This matters most if you are not a Twitch partner and therefore have no transcodes of your own.

Two limits worth knowing before you count on it. It is RTMP only, so an SRT destination does not get it, and it applies to Twitch and Kick.

## What this does not solve

Multistreaming multiplies your outputs. It does nothing about the input. If your field connection drops, every destination drops together, because they are all downstream of the same uplink.

That is a separate layer, and it is the one worth fixing first: bond your connections with [SRTLA](https://irlserver.com/guides/srtla-bonding) so a dead modem cannot take the feed down, and make sure something holds the platform session when the feed goes rough. [Keep your stream live when the signal drops](https://irlserver.com/guides/keep-stream-live-when-signal-drops) covers that stack.

## FAQ

Can I multistream directly from my phone?

That is not how a bonded IRL rig is put together. Your phone sends one feed up to an ingest, and the fan-out to several platforms happens after that, either in your own OBS at home or in the cloud. The phone is not the place to solve this.

How many platforms can Stage send to at once?

Three at the same time on Stage and Stage+. Twitch, Kick, YouTube, or any custom RTMP or SRT address. The Custom tier raises that to ten.

Do I need a separate multistreaming service?

Not if the compositing already happens off your machine. Stage encodes your feed once and pushes it to your destinations from our side. If you run your own OBS on a PC with real upload, you can fan out from there instead.

Does multistreaming cost me quality on Twitch?

Not on its own, since each destination gets its own output. Stage+ adds Enhanced Broadcasting, which sends multiple bitrates so viewers on weaker connections do not buffer, but that is RTMP only and applies to Twitch and Kick.

---

Source: https://irlserver.com/guides/share-your-feed-with-other-streamers

# How to Share Your IRL Feed With Other Streamers (Play Keys)

Co-streaming an IRL moment is half the fun. One person is out in the field with the rig, and everyone else wants that feed live in their own stream. Play keys make that clean: one publisher (you), a separate named key for each co-streamer, all pulling the same feed.

1 publisher

your field rig

Many keys

one per streamer

Their OBS

pulls your feed

## How it works

You are the publisher. Your phone or encoder bonds and sends your feed to the relay as usual. A **play key** is a separate, shareable credential that lets someone else pull that same feed into their own OBS. Each key is its own, so you can name them, hand them out, and turn any of them off later without touching your stream.

This is what makes a collab simple: you do not re-stream anything, and your co-streamers do not need your login. They just get a key.

## Create and share a play key

1.  In your [dashboard](https://irl.ac/), open your **SRTLA endpoint** and go to the **Play Keys** tab.
2.  Add a play key and **name it for the person** it is for, for example "Guest Streamer".
3.  Copy the **Media Source URL** the dashboard generates for that key.
4.  Send that URL to your co-streamer.

Repeat for each person. Each gets their own named key, and you can disable or delete any of them at any time.

## What your co-streamer does

They add your Media Source URL as a **media source** in their own OBS, the same way they would add any IRL feed:

1.  In OBS, add a Media Source to a scene.
2.  Paste in the Media Source URL you sent.
3.  Set Network Buffering to about 1 MB and Reconnect Delay to a few seconds for a steady pull.

Now your live IRL feed shows up inside their stream, pulled straight from the relay.

Name your keys per person

Give each play key the streamer's name. When a collab ends, you disable or delete just that one key, and the rest keep working. No resetting your whole setup.

[Get a relay with play keys](https://irlserver.com/pricing)

All of this assumes the publishing side is already working. If it is not, [SRTLA bonding explained](https://irlserver.com/guides/srtla-bonding) and [connect Moblin](https://irlserver.com/guides/connect-moblin) cover getting a feed into the relay in the first place.

## FAQ

How many streamers can I share my feed with?

As many as you need. You create a separate, named play key for each person, and they all pull from your single publisher feed. You can enable, disable, or delete each key on its own.

Do co-streamers see exactly what I am streaming?

Yes. Every play key pulls the same feed you are publishing. It is your live IRL feed, shared, not a separate stream.

Is this only for SRTLA endpoints?

Yes. Play keys are generated on an SRTLA endpoint. Your own publish key also works for playback if you need it.

---

Source: https://irlserver.com/guides/srt-latency-settings-irl-streaming

# SRT Latency Settings for IRL Streaming: What to Set and Why

The SRT latency box is not a speed setting. It is the amount of time you give the protocol to notice that a packet went missing, ask for it again, and get it back before the picture needs it. Set it too small and the stream freezes on every bad second of cellular. Set it sensibly and the same bad second is invisible.

For IRL the sensible number is bigger than the studio number. Here is what it does, what to type in, and how to tell whether it is the thing that needs changing.

2000–3000 ms

encoder side, cellular or bonded

2 s

OBS pull from the relay

Larger wins

both ends negotiate, the bigger value is used

## What the number actually is

SRT runs over UDP. When a packet is lost, the receiver notices the gap and asks the sender for that packet again. The latency value is how long the receiver is willing to wait for that answer before it has to give up and play what it has. Anything that arrives inside the window is put back in order and the viewer never sees the loss. Anything that misses the window is dropped, and that is the freeze or the smear of blocks you see on a rough connection.

So the window has to be wider than a full round trip, with room for more than one attempt. Haivision, who wrote the protocol, put it as a multiple of the round trip time: roughly three to four times on a clean link, and more as packet loss climbs.

The part people miss is that it is a two-sided setting. Your encoder declares a latency, the relay declares one, and the handshake uses the larger of the two. Turning your encoder down below the relay's value changes nothing, and turning it up always takes effect.

## Why the IRL number is bigger

A wired studio link has a steady round trip. A phone walking through a city does not. The average round trip to a nearby relay might be under a tenth of a second, but a tower handover, a crowded cell, or a modem waking back up can push one round trip past half a second and stack a few of those in a row. The window is not sized for the average. It is sized for the spike.

With SRTLA bonding there is a second job for the same window. SRTLA spreads your packets across every modem you have. When one modem goes dark, the packets that were in flight on it are gone, and SRT asks for them again. SRTLA sends those retries over the modems that are still healthy. The latency window is the time budget for that reroute. A tight window means a dead modem costs you a freeze even though you have two more working. A roomy window means it costs you nothing visible. That is most of the reason [bonding](https://irlserver.com/guides/srtla-bonding) feels so much smoother than a single SRT link on the same phone.

## What to set

| Where | Setting | Notes |
| --- | --- | --- |
| Belabox (SRTLA) | 2000 ms | The default. Go up, not down, if a route is rough. |
| Moblin on iPhone (SRTLA) | 3000 ms | The default. Leave it; it is already on the roomy side. |
| IRL Pro on Android (SRTLA) | 2000 ms | Same field as Belabox, same starting point. |
| LiveU Solo Pro (SRT) | 2500 ms | What the dashboard shows for this encoder. |
| Larix (SRT) | 2500 ms | Set automatically when you open the connection from the dashboard. |
| OBS media source pulling the relay | `latency=2000000` | Microseconds, not milliseconds. This is two seconds. |

If you only take one thing from the table: there is no good reason to go below 2000 ms on a cellular route, and there is rarely a reason to go above 4000 ms. Between those, higher is safer and the cost is fractions of a second of delay that nobody in chat can feel.

The OBS side counts in microseconds

OBS reads SRT through FFmpeg, and FFmpeg's latency option is in microseconds. Two seconds is `2000000`. Typing `2000` gives you two milliseconds, which is no recovery window at all, and the pull will stutter even on a perfect home connection. The full pull URL is in the [OBS setup guide](https://irlserver.com/guides/obs-setup).

## Reading the symptoms

Most latency questions are really "something is wrong, is this the knob". Usually it is one of three things and only one of them is the latency.

| What you see | What it means | What to change |
| --- | --- | --- |
| Short freezes or blocky frames while the bitrate graph stays healthy | Packets are missing the window | Raise SRT latency by 500 ms and test again |
| Bitrate drops and the picture softens, but it keeps moving | The adaptive bitrate is doing its job on a thin link | Nothing on latency. This is the trade working. |
| The stream ends completely | The connection died, not the buffer | Drop protection: your own OBS holding the broadcast. See [keep your stream live](https://irlserver.com/guides/keep-stream-live-when-signal-drops). |

The first row is the only one the latency setting fixes. The second row is normal and the third row is a different problem entirely. Raising latency to fight a disconnect does nothing, because there is no connection left to recover on.

## SRT latency is not your viewer delay

The window on your encoder is one hop in a chain. The relay hands the stream to your OBS over a second SRT hop with its own window. OBS holds a network buffer, encodes, and pushes to the platform. The platform ingests, transcodes, and the player buffers on top of that.

| Stage | Roughly |
| --- | --- |
| Encoder SRT window | 2 to 3 s |
| Relay to OBS SRT window | 2 s |
| OBS network buffer and encode | under 1 s |
| Platform ingest, transcode, player | several seconds |

Cutting the first row from 2500 to 1000 saves a second and a half out of a chain that runs well past that, and it buys that second with every freeze the window can no longer absorb. People forgive a short delay. They leave when the picture keeps stopping. If chat timing genuinely matters for a segment, the platform's low latency mode moves the total far more than the SRT number does.

## How to tune it without guessing

-   Set the encoder to the number from the table and leave it alone.
-   Stream the worst part of your route: the tunnel, the crowd, the train platform. Not your living room.
-   If the picture freezes while bitrate holds, raise latency by 500 ms and run the same route again.
-   Change one thing at a time. Latency, bitrate, and resolution all move the same symptoms, and adjusting two together tells you nothing.
-   Keep the local recording. Watch the motion and the audio back rather than trusting a green number on a dashboard.

The relay is the other half of the setting

Your encoder only decides one side. Our relay runs a relaxed latency profile by default, built for bonded cellular uplinks rather than a studio link, so a sane encoder value lands on a receiver that expects rough conditions. Pair that with pulling the relay into [your own OBS](https://irlserver.com/guides/obs-setup) and the field connection stops being the thing that ends your broadcast.

[Get a relay tuned for IRL](https://irlserver.com/pricing)

Still choosing a protocol? [SRTLA vs RTMP](https://irlserver.com/guides/srtla-vs-rtmp) covers when SRT alone is enough and when you need bonding.

## FAQ

What SRT latency should I use for IRL streaming?

Start at 2000 to 2500 ms on the encoder side and leave it there until the stream has proven stable on the worst part of your route. Belabox defaults to 2000 ms and Moblin to 3000 ms, and both are fine as they are. Our dashboard hands out 2500 ms for single-connection SRT encoders like the LiveU Solo Pro and Larix.

Does the SRT latency need to match on both ends?

No. Both ends declare a value in the handshake and the connection uses the larger one. That is why setting your encoder below whatever the relay uses does nothing, and why the OBS pull can be tuned separately from the encoder side.

Will 2500 ms make my stream feel slow for chat?

Not noticeably. The SRT window is one piece of a chain that already includes a second SRT hop into OBS, OBS's own buffer, and the platform's ingest and player delay. Cutting the encoder window in half saves about a second out of a chain that runs well past that.

Why does the OBS media source want 2000000 instead of 2000?

OBS reads the SRT URL through FFmpeg, and FFmpeg takes latency in microseconds. 2000000 is two seconds. Typing 2000 there gives you two milliseconds, which is effectively no recovery window at all.

---

Source: https://irlserver.com/guides/srtla-bonding

# SRTLA Bonding Explained: Stream IRL Without Dropping

Your phone shows four bars and your stream still dies the second you walk under a bridge. One tower, one bad handoff, and the whole broadcast drops. SRTLA exists so that never decides your night.

RTMP · SRT · SRTLA

ingest protocols

2 to 4+

connections bonded

Global

SG · US · EU · Scandinavia

## What SRTLA actually is

SRT is a streaming protocol that recovers lost data and rides out a choppy connection far better than RTMP. That is why the IRL scene moved to it. But SRT still uses one connection. Lose that connection and you lose the stream.

SRTLA is the bonded version. It spreads one stream across every connection your encoder has at the same time. Two SIMs, a third modem, the cafe Wi-Fi, all carrying part of it. A relay on the other end catches all the pieces and joins them back into one clean stream.

Bonding is not "switch to a backup when the main one dies." Every connection carries part of the load, all the time.

## How it behaves in the field

Your encoder and the relay keep an eye on every connection. When one modem gets congested or you move between towers, SRTLA leans on the connections that are still healthy and keeps going. Your viewers see nothing.

-   One SIM dies under a bridge. The other two carry the stream.
-   You walk out of a packed arena (dead signal) toward the exit. It rebalances as coverage comes back.
-   A modem drops completely. The stream rides the ones that are left instead of ending.

Bonding is a floor, not a magic ceiling

Bonding raises your reliability floor. It cannot invent bandwidth that is not there. If every connection is maxed out at once, your encoder lowers its bitrate to keep moving, and [NOALBS](https://irlserver.com/guides/noalbs) switches your OBS to a holding scene so viewers see something on purpose instead of a frozen feed.

## SRTLA vs SRT vs RTMP

|     | RTMP | SRT | SRTLA |
| --- | --- | --- | --- |
| Connections used | 1   | 1   | many, at once |
| Recovers lost data | no  | yes | yes |
| Survives a dead modem | no  | no  | yes |
| Needs a relay | no  | optional | yes |
| Right for IRL | rarely | one connection | bonded field rig |

If you stream from a backpack on cellular, SRTLA is the answer. The full protocol breakdown is in [SRTLA vs RTMP](https://irlserver.com/guides/srtla-vs-rtmp).

## What the relay does

SRTLA only works if a relay is catching all the pieces. The relay joins them back into one clean feed, and you pull that feed into your own OBS as a media source. OBS is what you actually broadcast to Twitch or Kick from.

Two things make our relay worth pointing at. It runs custom SRTLA tuning instead of the plain open source defaults, and it runs on global servers (Singapore, the US, the EU, and Scandinavia) with unlimited bandwidth, so you connect to one near wherever you are.

## Why the basic open source version is only half the story

The free open source SRTLA works. It is also bare-bones, and everyone runs it with the same default settings.

Our relay is tuned, closer to what official Belabox cloud does than to the plain version. That tuning is the part that decides whether a rough connection stutters or holds smoothly. That, plus being one of the only options besides official Belabox cloud with a real way to [remote control a Belabox](https://irlserver.com/guides/connect-belabox), is why people move their rig over and stop thinking about it.

## Getting started

1.  Pick an encoder that speaks SRTLA: a Belabox, a bonding box, or a phone app like Moblin (iPhone) or IRL Pro (Android) running more than one modem.
2.  Point it at an SRTLA relay in the region nearest you.
3.  Pull the relay into your own OBS as a media source, and run [NOALBS](https://irlserver.com/guides/noalbs) so OBS switches between your LIVE, LOW, and BRB scenes on its own when the feed changes.

[Spin up an SRTLA relay](https://irlserver.com/pricing)

## FAQ

Is SRTLA the same as SRT?

No. SRT uses one connection. SRTLA spreads that same stream across several connections at once and joins them back together at the relay. SRTLA needs a relay on the other end. Plain SRT does not.

Do I need a special device to use SRTLA?

You need something that speaks SRTLA on your side: a Belabox, a bonding box, or a phone app like Moblin or IRL Pro running more than one modem. The relay handles the other end.

How many modems can SRTLA bond?

As many as your encoder has. Most field rigs run two to four SIMs plus Wi-Fi. SRTLA uses every connection you give it and leans on whichever ones are healthy.

---

Source: https://irlserver.com/guides/srtla-vs-rtmp

# SRTLA vs RTMP for IRL Streaming: Which Protocol to Use

The protocol you pick decides whether a rough connection stutters for half a second or ends your broadcast. For IRL there are really three options, and only one of them survives a dead modem.

RTMP

single wired link

SRT

one connection, recovers

SRTLA

bonded field rig

## RTMP, in one paragraph

RTMP is old, simple, and everywhere. It has no real way to recover when a connection gets choppy. At a desk on a wired connection it is perfectly fine. On cellular it falls apart, because the first rough patch either stalls or kills the stream. If you are streaming IRL on mobile, RTMP is the thing you are trying to escape.

## SRT, in one paragraph

SRT recovers lost data and smooths out a choppy connection, so it rides out the small hiccups that wreck RTMP. The catch: it still uses one connection. Great for a single strong link. But lose that link (dead tower, dropped modem) and SRT has nowhere to go.

## SRTLA, in one paragraph

SRTLA is the bonded version of SRT. It spreads one stream across every connection you have at once, and a relay joins it back together. This is the one built for a backpack on cellular: it survives a dead modem because the other connections keep carrying the stream. Full breakdown in [SRTLA bonding explained](https://irlserver.com/guides/srtla-bonding).

## Side by side

|     | RTMP | SRT | SRTLA |
| --- | --- | --- | --- |
| Recovers lost data | no  | yes | yes |
| Uses multiple connections | no  | no  | yes |
| Survives a dead modem | no  | no  | yes |
| Needs a relay | no  | optional | yes |
| Best for | wired desk | one strong link | bonded mobile rig |

## How to actually choose

-   Wired connection that never moves: RTMP is fine. Do not overthink it.
-   One strong cellular or wired link, no bonding gear: SRT. You get recovery without needing a relay.
-   Two or more connections, a Belabox or bonding phone app, streaming on the move: SRTLA. This is the IRL answer.

The relay is the deciding factor for SRTLA

SRTLA is only as good as the relay joining it back together. The free open source version works, but everyone runs it with the same default settings. Our relay is custom tuned (closer to what official Belabox cloud does than to the plain version) and built to ride out a rough connection. Same protocol, very different field performance.

## What most people are actually choosing between

For most IRL streamers the answer is SRTLA, because the failure you actually hit is a dropped connection, not a shortage of clean bandwidth. Optimising for throughput when your problem is a dead tower solves the wrong thing. The price is a small relay delay.

[Start streaming on SRTLA](https://irlserver.com/pricing)

The [keep your stream live](https://irlserver.com/guides/keep-stream-live-when-signal-drops) guide stacks SRTLA with your own OBS and NOALBS, so neither a dropped connection nor a rough feed can end your broadcast.

## FAQ

Is RTMP ever the right choice for IRL?

On a single rock solid wired connection, RTMP is fine and simple. The moment you are on cellular, walking, or bonding multiple modems, RTMP cannot recover or combine connections, and SRT or SRTLA wins.

What is the difference between SRT and SRTLA?

SRT is one connection that recovers lost data. SRTLA spreads that same stream across several connections at once. SRTLA needs a relay to put it back together. Plain SRT does not.

Does SRTLA add delay?

It adds a small delay at the relay so it can put your stream back together in order. In exchange you get a stream that survives a dead modem. For IRL that trade is almost always worth it, and a tuned relay keeps the added delay low.

---

Source: https://irlserver.com/guides/stop-streams-ending-twitch-kick

# How to Stop Your Stream From Ending on Twitch and Kick

Few things sting like a good IRL stream getting cut off because you walked through a tunnel. The dropout was short. The broadcast ended anyway.

## Why platforms end your broadcast

Twitch and Kick tie the broadcast to whatever is sending to them. The moment that source goes quiet for long enough, they assume you are done and end the session. Your viewers get the offline screen, your VOD splits, and you have to start over.

There is a short grace period, but it is short. A real IRL dropout (a tunnel, an elevator, a dead spot in a crowd) often lasts longer than the platform is willing to wait.

## Why streaming straight from your phone is fragile

If your phone or encoder streams directly to Twitch or Kick, the platform is watching your field connection. That connection is the most fragile part of the whole chain. One bad handoff and the thing the platform is watching disappears, so the platform ends the broadcast.

You cannot make a single cellular connection perfectly reliable. So do not let it be the thing the platform is watching.

## The fix: put your own OBS in front of the platform

Run a local OBS between your field rig and the platform:

1.  Your phone or encoder bonds its connections with [SRTLA](https://irlserver.com/guides/srtla-bonding) and sends to a relay.
2.  The relay hands a clean feed to your own OBS as a media source.
3.  **OBS is what stays connected to Twitch or Kick.**

Now the platform is watching OBS, which never moves and never loses signal. When your field connection wobbles, that is just a media source going quiet inside OBS, not the platform losing its source.

## Cover the rough patches with NOALBS

When the feed does get bad, you want something on screen, not a frozen frame. [NOALBS](https://irlserver.com/guides/noalbs) watches your incoming bitrate and switches your OBS scene automatically: a LOW scene when it dips, a BRB scene when it drops, back to LIVE when it recovers. OBS stays connected the whole time, so the session never ends.

Bonding and OBS solve different halves

Bonding keeps the feed alive across a dead modem. Your local OBS keeps the platform session alive across a rough feed. You want both. The full setup is in [keep your stream live when the signal drops](https://irlserver.com/guides/keep-stream-live-when-signal-drops).

[Get a relay that keeps you live](https://irlserver.com/pricing)

## FAQ

Why does Twitch end my stream when my phone loses signal?

Because the broadcast is tied to whatever is connected to Twitch. If your phone streams straight to Twitch and the connection drops, Twitch sees the source disappear and ends the session. Put your own OBS in front of the platform and OBS keeps the session alive.

Does Kick behave the same way as Twitch?

Yes. Both end the broadcast when the source they are receiving from goes away. The fix is the same: keep a local OBS connected to the platform so the field connection is never what the platform is watching.

Will a grace period save my stream?

Twitch and Kick give only a short window before they end a broadcast, and a real IRL dropout often outlasts it. Relying on the platform's grace period is not a plan. Keeping OBS connected is.

---

Source: https://irlserver.com/guides/why-mobile-signal-drops-irl

# Why Mobile Signal Gets Bad While You Stream (and How to Fix It)

Your signal shows full bars and your stream still falls apart. It is not your phone lying to you, it is that streaming leans on the part of the connection that bars do not measure.

## Bars measure the wrong thing

Signal bars mostly reflect how close you are to a tower and how good your download looks. Streaming runs the other direction. It needs **upload**, which on cellular is the weaker, more crowded lane. You can stand under a tower with four bars and still have almost no upload room, especially in a crowd.

## What actually drags your connection down

-   **Congestion.** A packed arena, a festival, a busy street. Everyone is sharing the same towers, and upload is the first thing that suffers.
-   **Tower handoffs.** As you walk, your phone hops from tower to tower. Each handoff is a moment where packets can stall or drop.
-   **Buildings and bodies.** Concrete, glass, and even big crowds block and absorb signal. Walk indoors or into a tunnel and upload can collapse.
-   **One carrier, one weakness.** A single SIM is at the mercy of one network's coverage and congestion right where you are standing.

None of these are things you can fix by holding the phone higher. They are properties of the network around you.

## The fix: stop depending on any single connection

If one connection can fail, do not rely on one connection.

-   **Bond several connections.** [SRTLA](https://irlserver.com/guides/srtla-bonding) spreads your stream across Wi-Fi and multiple SIMs at once. When one browns out, the others carry it. Different carriers also handle congestion differently, so two networks rarely die in the same spot at the same time.
-   **Broadcast through your own OBS.** Send your bonded stream to a relay, pull it into your own OBS, and let OBS stay connected to Twitch or Kick. When the feed still gets rough, [NOALBS](https://irlserver.com/guides/noalbs) switches to a holding scene instead of ending the broadcast.

Two carriers beat one big SIM

Two SIMs on different networks usually beat one SIM on a great plan. Coverage and congestion are local, and two carriers rarely have a dead spot in exactly the same place.

[Get a relay built for bad signal](https://irlserver.com/pricing)

The mechanics of bonding are in [SRTLA bonding explained](https://irlserver.com/guides/srtla-bonding). The full rig, including the OBS layer, is in [keep your stream live when the signal drops](https://irlserver.com/guides/keep-stream-live-when-signal-drops).

## FAQ

Why does my signal look full but my stream still stutters?

Signal bars show download conditions and tower proximity, not upload headroom. Streaming uses upload, which is the weaker, more congested direction on cellular. Full bars in a crowd can still mean almost no upload.

Does a better phone fix bad signal?

Only a little. The bottleneck is usually the network and the upload path, not the phone. Bonding multiple connections helps far more than a newer handset.

What actually keeps my stream up when signal drops?

Bonding several connections so a dead one does not end the stream, plus your own OBS broadcasting through a relay so a rough feed shows a holding scene instead of ending the broadcast.

---

Source: https://irlserver.com/compare/belabox-cloud

# Belabox Cloud vs IRLServer: How the Two Differ

Official Belabox cloud, from the people behind Belabox, is a strong, respected service. Very few options besides it offer both a tuned SRTLA relay and a real way to remote control a Belabox. We are one of them, which makes this a comparison between two services that overlap on the things that matter most.

Custom SRTLA

tuned relay

Card payments

simple checkout

Global

SG · US · EU · Scandinavia

## What we have in common

-   A custom tuned SRTLA relay, not the plain open source defaults. Both of us tune the part of SRTLA that actually decides field performance.
-   Real Belabox remote control. Change bitrate, restart the encoder, and adjust settings from your phone from any network. See [connect Belabox](https://irlserver.com/guides/connect-belabox).
-   A focus on keeping bonded streams alive rather than on breadth of features.

## Where we differ

-   Payment. We take normal card payments through Stripe. Belabox cloud runs on GitHub Sponsors, with emailed vouchers as the other route. If you would rather just pay with a card, that is a real, everyday difference.
-   Regions. Global servers with no data caps: Singapore, the US, the EU, and Scandinavia. Your endpoint works in all of them, so changing region is a URL edit rather than a migration.
-   Independent option. We are a separate provider, which means a second place to go if you want different regions, payment, or a different support relationship.
-   Wider toolset. Free tools (bitrate calculator, NOALBS config generator, OAuth generator) and a clip player for your BRB screen sit alongside the relay.

## Side by side

|     | IRLServer | Belabox cloud |
| --- | --- | --- |
| Custom tuned SRTLA relay | yes | yes |
| Belabox remote control | yes | yes |
| Payment | card / Stripe | GitHub Sponsors or emailed voucher |
| Global servers (SG, US, EU, Scandinavia) | yes | check their site |
| Extra free tools and clip player | yes | check their site |
| Pricing | see plans | check their site |

Confirm the moving parts on their site

Regions and pricing change. We are not going to quote Belabox cloud's current plans for them. Check their site for the latest and compare on what each plan actually includes.

## Who should pick which

-   Pick IRLServer if card payments, our regions, our wider tool set, or European support fit you better.
-   Pick Belabox cloud if you prefer running everything with the team that builds the Belabox itself and their setup suits you.

Both run a real tuned relay and both let you remote control the box, so the decision comes down to payment, regions, and who you would rather deal with when something breaks.

[See IRLServer plans](https://irlserver.com/pricing)

The other common comparison is against a managed toolkit, which is a different trade entirely: [IRLServer vs IRLToolkit](https://irlserver.com/compare/irltoolkit).

## FAQ

Is IRLServer just a Belabox cloud clone?

No. We run our own tuned SRTLA relay and our own Belabox remote control. We are simply one of the only options besides official Belabox cloud with that combination, plus global servers and card payments.

Should I leave Belabox cloud for IRLServer?

Only if our regions, payment, or support fit you better. Belabox cloud is genuinely good. The right pick comes down to where you stream, how you want to pay, and which support you prefer.

How do I pay for each one?

IRLServer takes normal card payments through Stripe. Belabox cloud runs on GitHub Sponsors, with emailed vouchers as the other option. If you would rather just pay with a card, that is a real difference.

---

Source: https://irlserver.com/compare/irltoolkit

# IRLServer vs IRLToolkit: Cloud OBS or Your Own?

Both IRLServer and IRLToolkit serve IRL streamers, and both are real options. The biggest difference is the model. IRLToolkit hosts a full cloud OBS for you. IRLServer gives you a tuned relay and you run your own OBS. That one difference drives most of the rest, including the price.

Your own OBS

\+ our relay

Lower cost

no cloud OBS to rent

Custom SRTLA

tuned relay

## What you are actually choosing between

IRLToolkit runs a full cloud OBS in the browser. It is convenient, and you pay for that hosted machine running around the clock. IRLServer takes a different route: a custom tuned SRTLA relay that you pull into your own OBS as a media source. You keep your OBS, your overlays, and your scenes, and you skip the cost of renting a cloud OBS.

If you want reliability without paying to host a whole OBS in the cloud, that is the lane we build for.

## Where we focus

-   Lower cost. The expensive part of cloud OBS is the hosted machine. You run your own OBS, so there is nothing to rent, and the price comes in well under a full cloud OBS service.
-   Custom tuned SRTLA relay. Not the plain open source defaults everyone runs. The tuning is what decides field performance, closer to what official Belabox cloud does. See [SRTLA bonding explained](https://irlserver.com/guides/srtla-bonding).
-   Belabox remote control. We are one of the only options besides official Belabox cloud that lets you [remote control a Belabox](https://irlserver.com/guides/connect-belabox) from your phone while live.
-   Global servers, unlimited bandwidth. Singapore, the US, the EU, and Scandinavia, so you connect to one near wherever you stream.

## Side by side

|     | IRLServer | IRLToolkit |
| --- | --- | --- |
| Model | your own OBS + our relay | full cloud OBS |
| Relative cost | lower (nothing to host) | higher (cloud OBS runs for you) |
| Custom tuned SRTLA | yes | check their site |
| Belabox remote control | yes | check their site |
| Global servers (SG, US, EU, Scandinavia) | yes | check their site |
| Free tools (bitrate, NOALBS config) | yes | check their site |

Why some cells say to check their site

We are not going to put words in a competitor's mouth or quote a price that changes next week. Check IRLToolkit's current plans on their own site and compare on what a plan actually includes.

## Who should pick which

-   Pick our relay if you want to keep your own OBS, pay less, and get a tuned bonded relay with Belabox remote control. This is what most people need.
-   Pick IRLToolkit if you specifically want their fully managed cloud OBS in the browser and you are happy paying for that convenience.

## The cloud OBS trade off

A hosted cloud OBS is genuinely convenient: nothing to run locally, reachable from anywhere. The catch is that you are paying for a machine running your OBS around the clock. For most IRL streamers the reliability problem is a bonding and ingest problem, and solving it at the relay (with your own OBS) does the job for a lot less. That is why the relay, not the compositor, is what we point most people at.

[See IRLServer pricing](https://irlserver.com/pricing)

Official Belabox cloud is the other service people weigh us against. That comparison turns on payment and regions rather than on the OBS model: [Belabox cloud vs IRLServer](https://irlserver.com/compare/belabox-cloud).

## FAQ

Is IRLServer cheaper than IRLToolkit?

Generally yes. IRLToolkit hosts a full cloud OBS for you, and that hosted machine is the expensive part. With IRLServer you run your own OBS and pay for the relay, so there is no cloud OBS to rent. Check current plans on each site for exact numbers.

Is IRLServer a drop in replacement for IRLToolkit?

If what you need is a reliable bonded ingest into your own OBS, yes, and that is what most people need.

What does IRLServer do that IRLToolkit does not lead with?

A custom tuned SRTLA relay, a real way to remote control a Belabox, global servers with unlimited bandwidth, and a much lower price because you bring your own OBS.