IRL.com.de is a free platform that provides IRL streamers with a stable, Germany-hosted stream relay. You can stream via SRT/SRTLA with link bonding on mobile, or via RTMP/RTMPS from OBS, action cams and other encoders directly to the relay. From there you forward reliably to Twitch, Kick or any other target platform – without your own server, without costs.

Yes – completely and without hidden costs. There is no subscription, no premium tier and no payment details you need to provide. The service is privately operated and self-funded by the operator.

• IRL streamers who stream on the go and need a stable relay connection
• Mobile-first streamers who want to use multiple SIM cards or WiFi + mobile data simultaneously (SRTLA bonding)
• Desktop and studio streamers using OBS, vMix or other RTMP-capable encoders
• Twitch and Kick creators who want to avoid the hassle of running their own server
• Beginners looking for an easy, documented solution

All servers are located in Germany on own infrastructure. No third-party cloud services such as AWS, Azure or Google Cloud are used. The current server status is available at status.irl.com.de. Maintenance and outage notices may also appear as banners in the panel.

There are no fixed time limits. The service operates on fair use – no permanently excessive bitrates and no automated mass use. Normal IRL streams at 3–8 Mbit/s run fine; for very high bitrates (4K, 20+ Mbit/s) please get in touch first.

Per account the defaults are (unless individually adjusted):

• 3 streams
• 5 players per stream
• 3 push targets per account (across all streams)

Higher limits come from the Loyalty & Level system. Your current values are shown in the panel.

On first visit, OAuth with Twitch or Kick is enough – a panel account is created automatically. Later you can also sign in with email/username and password (set a password in your profile). Optional 2FA (TOTP) and “Remember me” are available.

A player is a playback/viewer access to the relay – e.g. a player URL you add in OBS as a media source for local monitoring or share with someone. That is different from ingest (your encoder sends to the relay) and from a push target (forward to Twitch/Kick/…).

Yes. In the panel under Profile you can link a second provider (Twitch and Kick). New links are confirmed by email. See the account linking guide for details.

No. Never share your stream key publicly – anyone who has it can publish to the relay as you. If you need a new key, delete the stream in the panel and create a new one.

Live metrics (bitrate, packet loss, etc.) appear on the dashboard while a stream is active. Longer history and sessions are under Usage in the panel – streaming hours for loyalty points also come from there.

The loyalty system awards points for active use and referrals. Your level rises with your point balance and unlocks bonus slots on top of the base limits in the panel.

How to earn points (current defaults):

• 0.1 points per streaming hour
• 5 points for the first stream (one-time)
• 10 points for a successful referral (new user via your referral link)

Balance and history are under Profile → Loyalty in the panel. Your referral short link is under Referral there. Points and levels can be adjusted by the operator – the panel display is authoritative.

What do the bonuses mean?

• +S (Streams) – extra streams (ingest slots with stream URL and key)
• +P (Players per stream) – extra player links per stream
• +W (Push targets) – extra forwards per account (across all streams), e.g. Twitch, Kick, YouTube (see also Technology & Protocol)

The table columns are extra slots at that level.

+S = Streams · +P = Players per stream · +W = Push targets (per account)

SRT (Secure Reliable Transport) is an open streaming protocol designed specifically for unstable network connections. Compared to RTMP, SRT offers:

• Error correction (ARQ/FEC): Lost packets are automatically re-requested or reconstructed from redundancy data
• Latency tolerance: Configurable buffer size adapted to network quality
• Robustness against packet loss: Up to 30% packet loss can be compensated without visible quality loss

RTMP, by contrast, is an older protocol without native error correction – on a poor connection the stream drops immediately.

SRTLA is an extension of the SRT protocol originally developed by the creators of belabox. The key difference: SRTLA supports link bonding – using multiple network connections simultaneously for a single stream.

In practice this means you can use your mobile network (e.g. LTE/5G), a mobile WiFi hotspot and a second SIM card at the same time. SRTLA distributes packets intelligently across all available connections and significantly increases stability and effective bandwidth.

IRL.com.de uses OpenIRL for SRTLA and OpenRTMP (librtmp2-server) for RTMP/RTMPS as server backends.

Yes. When creating a stream in the panel you can choose between SRT/SRTLA and RTMP/RTMPS as the ingest protocol. RTMP streams run on OpenRTMP and librtmp2-server.

The RTMP server supports:

• Legacy RTMP – classic RTMP with H.264, compatible with most encoders and apps
• Enhanced RTMP (e-rtmpv1/v2) – newer RTMP variant with support for HEVC and AV1 alongside H.264
• RTMPS – encrypted RTMP over TLS, when shown in the panel

RTMP is especially suitable for OBS, vMix, action cams (GoPro, DJI) and other devices without native SRT support. For mobile IRL streaming on the go with link bonding, SRTLA remains the recommended choice.

SRT/SRTLA is the better choice on unstable or mobile connections: error correction, configurable latency and with SRTLA link bonding across multiple networks. Ideal for IRL Pro, Moblin and hardware such as belabox.

RTMP/RTMPS is suitable when your encoder or device does not support SRT – e.g. classic OBS streaming, vMix or action cams. On a stable fixed-line connection, RTMP is perfectly fine.

Both ingest types use the same relay: players, statistics and push targets work identically.

Latency depends on several factors: network quality, chosen SRT buffer size and geographic distance to the server. Typical values:

• SRT buffer (latency setting): Default 2000 ms – affects error correction, not the actual viewer latency. For OBS we recommend a maximum of 500 ms.
• Relay processing latency: Under 100 ms
• Total latency to the viewer: Depends on Twitch/Kick (Twitch Low Latency: approx. 3–5 seconds)

The SRT buffer should be about 4× the RTT (round trip time) of your connection, but not more than 2500 ms. At 500 ms RTT that means a 2000 ms buffer.

Mobile apps:

• IRL Pro (Android) – built for IRL streaming, native SRTLA support
• Moblin (iOS) – native SRTLA support for iPhone

Hardware:

• belabox – dedicated IRL streaming hardware with native SRTLA support
• IRLBox – another dedicated hardware solution for SRTLA bonding

In the panel, matching streams offer one-tap buttons (“Open in Moblin” / “Open in IRL Pro”), including SRT/SRTLA and RTMP/RTMPS – step by step in the Moblin & IRL Pro guide.

• Open the panel at panel.irl.com.de and create a stream – choose SRT/SRTLA or RTMP/RTMPS as the ingest protocol
• Copy the stream URL and stream key from the panel
• In OBS open: Settings → Stream
• Select “Custom…” as the service
• For SRT/SRTLA: Enter the SRT URL as server and the stream key. Recommendation: SRT buffer max. 500 ms
• For RTMP/RTMPS: Enter the RTMP or RTMPS publish URL (server + key) from the panel
• Start streaming – the relay forwards to your configured push targets

More detail: guides.

SRT and SRTLA are built for exactly these scenarios. On a short connection drop (a few seconds):

• SRTLA immediately switches to another available connection (if bonding is active)
• SRT tries to re-request lost packets via ARQ (Automatic Repeat Request)
• Gaps are filled within the SRT buffer

If the connection drops completely, the stream on the target platform (Twitch, Kick, etc.) will also drop – that is due to the link between relay and target, not the SRTLA protocol itself. With pure RTMP ingest (no bonding), the stream typically drops sooner on network loss.

In the panel you create push targets per stream, but the count is limited per account (default: 3, plus loyalty bonuses) – not separately per stream. ffmpeg-compatible outputs are supported, including:

• RTMP / RTMPS – e.g. Twitch, Kick, YouTube Live, Facebook Live
• RTSP
• SRT
• UDP
• And other ffmpeg-compatible output protocols

Each push target gets its own ingress pull key (separate from the stream’s default player key).

Codecs: Not all platforms support every codec. H.265 (HEVC) or AV1 can cause issues – Twitch currently only accepts H.264 over RTMP.

We store what is needed for operation and security, including:

• Twitch/Kick username and platform user ID (and linked accounts)
• optional email, profile image and password hash
• stream, player and push-target configuration
• usage/loyalty data and technical logs (e.g. IP, connection times)

In your profile you can request a GDPR data export (JSON). Full details: privacy policy.

No. IRL.com.de is a pure relay service – the video signal is passed through in real time and is not stored or recorded. Only technical metadata (bitrate, connection quality, usage) is kept for the panel and loyalty.

Yes. In the panel under Profile → Delete account: confirm with DELETE, open the email link (valid 24 hours), then a 14-day cooling-off period starts during which you can cancel. After that the account is permanently removed. Alternatively: [email protected].

• Is the server reachable? Check status.irl.com.de and any banners in the panel
• Do stream URL and stream key match the panel exactly (capitalisation)?
• Does the ingest protocol (SRT/SRTLA vs. RTMP/RTMPS) match what your encoder sends?
• For SRT/SRTLA: firewall/router blocking UDP? Adjust SRT buffer (default 2000 ms, OBS max. 500 ms, not above 2500 ms)
• For RTMP/RTMPS: server and key entered correctly? Use RTMPS only when shown in the panel

Otherwise: support ticket in the panel, support.irl.com.de or [email protected].

• Bitrate too high for available upload bandwidth: Reduce the bitrate in OBS or your app
• High packet loss: Check the packet loss statistics in the panel. Above 5% is critical
• SRT buffer too small (SRT/SRTLA): Increase the buffer, but keep it at 2500 ms maximum
• Network congestion: Avoid parallel downloads or other bandwidth-intensive applications

Open Push Targets for your stream in the panel. You will see status and error messages. Common causes:

• Incorrect or expired URL or stream key for the target
• Push target is disabled
• Codec incompatibility (e.g. H.265/AV1 → switch to H.264)
• Connection drop between relay and target
• Account locked or restricted – the panel shows a notice in that case

Live statistics only appear while a stream is active. Otherwise reload the panel and check that JavaScript and cookies are allowed for panel.irl.com.de. Longer history is under Usage.

• Ticket in the panel – internal ticketing when you are logged in
• Support portal – support.irl.com.de (also without panel login)
• Email – [email protected]

Product updates: changelog.irl.com.de. Step-by-step: guides.