Relays (AuraBranch)
AuraBranch is an optional relay that carries calls for people far from your server. From January 2027 you can run it from a published image, on another machine.
Turning relays on
Section titled “Turning relays on”Relays are off until you set RELAY_SUBSYSTEM_ENABLED=true on your server. Then pair a relay from Server Settings › Integrations › Relay servers.
- Pairing uses a key exchange and one-time pairing tokens.
- Relays send heartbeats, and fail over automatically.
- Admins can create, suspend, drain and delete relays. Admin › Relays shows each relay’s version and status.
Choosing a relay per channel
Section titled “Choosing a relay per channel”In Channel Settings › Voice relay:
- Main server: calls stay on your server.
- Best relay: picks by latency and load.
- Specific relay: pinned to one relay.
DM and group-DM calls never use a relay.
What a relay operator can see
Section titled “What a relay operator can see”- Members’ IP addresses and when they join and leave a call.
- Not the audio (calls are encrypted end to end) and not names: rooms have opaque names and each call uses per-call pseudonyms.
A member who doesn’t want a relay to see their IP can turn on Route my voice through the main server in Settings › Privacy.
Updates
Section titled “Updates”Relays update themselves by default (RELAY_AUTO_UPDATE=on). They update only when nobody is in a call, drain first, and roll back if the new version fails its health check.
Relay on the same network as the server
Section titled “Relay on the same network as the server”The relay must report an address the server can reach, not localhost. With Docker bridge networking (the default), localhost means the container itself.
# Example: relay on the same LAN as the serverLIVEKIT_PUBLIC_URL=ws://192.168.1.50:7880