Relays: bigger groups
Sharing with more than about 5 people? Set up a relay. A relay is a member of the room with a fast upload that forwards everyone's video, so nobody else has to upload their screen once per viewer.
Why bigger groups need a relay
In a new room everyone sends their video directly to everyone else (a full mesh). That gives the lowest delay, but every sharer uploads their screen once per viewer: in a room of 8, each sharer uploads it 7 times. Most home connections can't keep that up at good quality, so with more than 5 people in a full mesh Bellion Share shows a warning: "6 people in a full mesh: everyone who shares uploads their screen 5 times. Expect lower quality, or have someone with a fast upload volunteer as relay (People menu)."
With a relay, everyone sends their video once, to the relay, and the relay sends it on to whoever watches it.
Relay mode
- Relay mode starts as soon as someone volunteers. Any member can volunteer; the server decides who relays.
- Several relays. The server picks as many volunteers as the room needs, up to 4, preferring the ones with the most upload. Each member is homed on one relay. Relays forward to each other, so any stream crosses at most two relays. Volunteers the room doesn't need yet stand by.
- Capacity. A relay serves between 2 and 16 members, depending on its upload (see How much upload do I need?).
- Only what's watched. Relays pull only the streams someone is watching, and up to 8 people can share at once in any room size.
- Adapts to viewers. A relay can make smaller versions (1080p, 720p) of a stream for viewers whose connection or computer can't take the top size, if it has the processing power to spare (a hardware encoder, or a CPU less than half busy).
- Leaving is fine. When a relay leaves, its members move to another relay without dropping the call; if there's no other volunteer, the room goes back to full mesh.
- Encryption still applies. With end-to-end encryption on (the default), a relay is a member like any other: it gets the room's keys, forwards the encrypted media unchanged, and decrypts only what it shrinks for a viewer. Only run a relay on a machine you trust with your stream.
Relay mode needs everyone in the room on build 31 or newer, and several relays need build 56 or newer. If someone runs a build that only knows one relay, the room uses a single relay and pauses relay mode above 5 people until they update.
Three ways to set up a relay
- Volunteer from the app. Easiest: a member with a fast upload clicks one menu item. Works on any server.
- A dedicated relay machine for your group. A spare PC, a home server or a rented server (VPS) joins your room by its share link and relays, so nobody's gaming PC has to. Works on any server, including bellion.app.
- A hosted relay on your own server. Keeps fixed rooms open around the clock. Needs your own Bellion Share server; it doesn't work with bellion.app.
1. Volunteer from the app
Good for: a group where one person has a fast, stable upload.
- Join the call as usual.
- Open the People menu.
- Choose Volunteer as relay.
- Check the line under the People table: it should say Relays: You relay for 4 people. (the number is how many people you serve), or You are standing by if the room doesn't need you yet.
To stop, choose Stop relaying (or Leave the relay queue while standing by) in the same menu. Your members move to another relay, or back to full mesh.
Volunteer when you have a fast, stable upload (a wired connection helps) and a computer that isn't busy with a demanding game. Relaying while you play makes both worse. Several people can volunteer; the server uses the ones it needs.
2. A dedicated relay machine for your group
Good for: a regular group that is often bigger than 5, when nobody wants to relay from their own PC. Any machine with a fast upload can do it: a spare PC, a home server, or a small rented server (VPS). It runs Bellion Share without a window, joins your room by its share link and volunteers. It works on any server, including the official bellion.app one.
The relay machine needs no screen and no desktop: it shares nothing and shows nothing. Forwarding uses little CPU; making smaller versions for viewers is video encoding, so it helps to have a hardware encoder or a few free CPU cores.
Step 1: install Bellion Share on the relay machine
- Linux (Ubuntu 24.04, Mint 22 or newer, including server installs without a desktop): download the .deb from bellion.app and run
sudo apt install ./blite_*.deb. This installs/usr/bin/bliteand the GStreamer plugins it needs. - Windows 10 or 11: download the zip from bellion.app and unzip it, for example to
C:\BellionRelay. The program you run isbin\blite.exein the unzippedblitefolder.
Step 2: get your room's share link
In the app on your own PC, start or join the session your group uses, and choose Room > Copy share link. It looks like https://bellion.app/j/CODE#password. Keep it private: it contains the room password.
Step 3: start the relay
On Linux, in a terminal (keep the single quotes; replace the link and the upload with yours):
blite -headless -link 'https://bellion.app/j/CODE#password' \
-volunteer -source none -view none \
-name "Group relay" -relay-upload-kbps 50000
On Windows, in PowerShell or a Command Prompt, in the unzipped blite folder:
bin\blite.exe -headless -link "https://bellion.app/j/CODE#password" -volunteer -source none -view none -name "Group relay" -relay-upload-kbps 50000
It prints room CODE link ..., then volunteered as relay, and a status line per member every 5 seconds. In the app, the relay appears in the People table as Group relay, and the line under the table says Relays: Group relay relays for N people. Press Ctrl+C to stop it; it leaves the room cleanly.
| Flag | What it does |
|---|---|
-headless | No window or tray: runs one session from the command line. |
-link URL | The share link to join. It joins on the link's server, so no other server setting is needed. |
-volunteer | Volunteers as relay as soon as it's in. |
-source none | Shares nothing. Required: without it the relay tries to share its screen, and on a machine without a display it stops right away. |
-view none | Shows and plays nothing (no windows, no decoding). Needed on a machine without a display. |
-name NAME | How it shows in the People table (default: the computer's name). |
-relay-upload-kbps N | Its upload in kbit/s (Mbit/s × 1000). The server uses it to decide how many members it serves, and the relay never sends faster than this. See How much upload do I need? |
-udp-port N | The UDP port for all its connections (default 30471; if that's taken, the next free one). See Troubleshooting. |
Don't add -relay: despite its name, it forces all connections through a TURN server, and a volunteer that others can only reach through TURN is never picked as a relay.
Step 4: keep it running
The relay keeps running until you stop it, and keeps the room open while it's in it: everyone else can leave, and the same link still works days later. It rides out short network drops (up to about a minute) without leaving the room. After a longer outage, or when the server restarts, it exits, so let the system start it again.
Linux: a systemd service. Put the link in a file only root can read, /etc/bellion-relay.env (sudo chmod 600 /etc/bellion-relay.env):
RELAY_LINK="https://bellion.app/j/CODE#password"
Create a user for it (sudo useradd --system --create-home --home-dir /var/lib/bellion-relay bellion-relay) and the service, /etc/systemd/system/bellion-relay.service:
[Unit]
Description=Bellion Share relay
Wants=network-online.target
After=network-online.target
[Service]
User=bellion-relay
EnvironmentFile=/etc/bellion-relay.env
ExecStart=/usr/bin/blite -headless -link ${RELAY_LINK} -volunteer \
-source none -view none -name "Group relay" -relay-upload-kbps 50000
Restart=always
RestartSec=3min
[Install]
WantedBy=multi-user.target
Then sudo systemctl daemon-reload && sudo systemctl enable --now bellion-relay, and journalctl -u bellion-relay -f to watch its log. Use Restart=always rather than on-failure: when its session ends (for example after a server restart) the relay exits normally. Keep RestartSec at a few minutes: when the link no longer works, the server counts each failed join from your address, and too many in 10 minutes block joins from it for a while, for everyone on your connection.
Windows. The simplest way is to leave the command running in its terminal window. To start it at boot without a window, create a task in Task Scheduler: trigger At startup, action Start a program with C:\BellionRelay\blite\bin\blite.exe and the flags above as arguments, Run whether user is logged on or not, and under Settings, If the task fails, restart every 5 minutes. Update the relay from time to time by downloading the new zip; the headless relay doesn't update itself.
When things change
- The person who started the room leaves. The room carries on. Ownership passes to whoever has been in the room longest, which can be the relay machine, and a relay can't disconnect or ban anyone. If you own the room, hand ownership to a person before you go: People > their name > Make owner...
- The link stops working. A room ends 5 minutes after the last person (relay included) leaves, and when the server restarts. The relay then can't rejoin: start a new session, put its link in the relay's command (or
/etc/bellion-relay.env) and restart the relay. - Encryption. The relay is a room member and gets the room's keys, like everyone else. It shows up with its own name tag (which changes each time it restarts), and the safety code includes it.
- Updates. When a relay's build is too old for the server, it can't join; install the new version.
3. A hosted relay on your own server
Good for: groups that run their own Bellion Share server. blite -host rooms.json keeps the listed rooms open around the clock with fixed room codes, so their share links never change, and volunteers as each room's relay. Member volunteers can relay alongside it when a room outgrows it.
A hosted relay needs your own signaling server: the fixed room codes are authorized with the server's secret BLITE_HOST_KEY, and the official bellion.app server doesn't hand that out. On bellion.app, use a dedicated relay machine instead.
- Set up your server as in Self-hosting, with
BLITE_HOST_KEYset to a long random secret. - Write
rooms.json. Codes are 4 to 12 letters and digits (no U; O counts as 0, I and L as 1); passwords need at least 4 characters.ownerslists the identity keys of the people who own the room while they're in it (from Room > Your identity key... in their app); otherwise the relay owns it.[ {"code": "7K3Q-X9MD", "password": "a-room-password", "name": "Our relay", "owners": ["<identity key from Room > Your identity key...>"]} ] - Run it with the same key and your server, with good upload and host networking:
The repository'sBLITE_HOST_KEY=<secret> blite -host rooms.json -server wss://share.example.com/ws -relay-upload-kbps 200000Dockerfile.hostbuilds an image for it, anddocs/examples/has a Docker Compose file running both services. - Share
https://share.example.com/j/7K3QX9MD#a-room-passwordwith your group. The link works around the clock.
The hosted relay restarts its rooms by itself when the connection drops. The Docker image includes the GStreamer plugins it needs to make smaller versions for viewers (software x264 encoding, so give it a few free CPU cores).
How much upload do I need?
Each member a relay serves costs it about 4.5 Mbit/s of upload (about one full-size stream plus small previews). The server plans with 70% of the relay's upload, so serving one member takes about 6.5 Mbit/s of upload, and a relay serves at least 2 and at most 16 members:
| Relay's upload | Members it serves |
|---|---|
| up to 25 Mbit/s | 2 to 3 |
| 30 Mbit/s | 4 |
| 50 Mbit/s | 7 |
| 100 Mbit/s | 15 |
| 105 Mbit/s or more | 16 (the most) |
| not known yet | 4 |
- In the app the relay's upload isn't known at first, so it serves 4; once it has sent more, the server uses the most it has seen (never fewer than 4).
- A dedicated or hosted relay should set
-relay-upload-kbpsto its real upload (from a speed test, in kbit/s; round down if it varies). Too high, and it gets more members than it can feed; too low, and it serves fewer and sends slower than it could, because it never sends faster than that. - For more members than one relay can serve, add relays: up to 4 relays share a room. With four 100 Mbit/s relays a room can have about 60 people.
- Download matters too: a relay receives each stream that someone it serves watches, once.
How to tell it's working
- The line under the People table lists the relays and how many people each serves, for example Relays: Group relay relays for 6 people; Sam relays for 4 people; Alex is standing by. Without a relay it says Everyone sends their video to everyone (full mesh).
- In a member's People > their name > Network path, people whose video comes through a relay show via the relay's name.
- A dedicated relay's log shows
volunteered as relay, thenplan ... relays=[...]lines when the server changes the plan, and per memberupKbps, the rate it sends that member.
Troubleshooting
- It says "standing by" and never relays. The room doesn't need another relay yet: the relays already picked have room for everyone. It takes over when one leaves or the room grows.
- The volunteer is never picked, even alone. A volunteer that others can only reach through a TURN server is never picked. Make it reachable directly: let it open its UDP port on the router (UPnP, NAT-PMP or PCP, on by default), or forward UDP port 30471 (or the one you set with
-udp-port) to it on your router, and allow that port in its firewall. On a VPS, open the UDP port in the provider's firewall too. A note at the top of the app window says whether others can reach you. - Two copies on one machine (for example the app and a relay): each needs its own UDP port. The second one takes the next free port, but a router forward only covers the one you forwarded; give the relay its own with
-udp-port 30480and forward that. - "Relay mode needs everyone in the room on Bellion Share build 31 or newer." Someone runs an old version; they need to update. With someone on a build older than 56, only one relay is used and relay mode pauses above 5 people.
- The relay exits right away with "video source". Add
-source none. - The relay exits with "signaling". The link is wrong, the room has ended (start a new session and use its link), or the relay's build is too old.
- Viewers still get low quality. Check the relay's upload (set
-relay-upload-kbpshonestly), and that it's on a wired connection. Each sharer's own upload still has to carry their stream once.