Skip to main content
Scene Share is the documented standalone self-hosting path. It ships with a relay service and a headless vscene CLI.
The relay forwards the muxed stream by stream identity. It does not transcode, retime, inspect, or mix the media payload.

​
Decide whether to self-host

Self-host when you have an operator who can own:
  • A supported Linux host and service lifecycle.
  • Public DNS and UDP firewall rules.
  • Token and SRT encryption secrets.
  • Monitoring, capacity, upgrades, rollback, and availability.
  • Incident response and credential rotation.
  • End-to-end sender and receiver testing.
Use the hosted relay when you do not want to operate those responsibilities.
Never expose relay or signing secrets in a repository, command transcript, support ticket, OBS log, or shared automation output.

​
Network ports

The current standalone defaults are: Confirm the values for the exact build you deploy. Do not expose the control API merely because the media ports are public.

​
Required secret separation

  • VSCENE_HMAC_SECRET signs role- and expiry-limited session tokens.
  • VSCENE_SRT_PASSPHRASE encrypts the SRT media path.
  • The two values must be strong, distinct, and stored outside source control.
  • VSCENE_STATE_PATH must point to durable state with appropriate service-user permissions.

​
Deployment source

The authoritative build, configuration, token, and service instructions live with the Scene Share server source:
Follow the runbook for the version you deploy. Do not copy commands from an unrelated release or assume hosted vAudioLink credentials work with your relay.

​
Operator workflow

The vscene CLI provides commands to:
  • Validate and print configuration.
  • Start the relay service.
  • Create, list, and end sessions.
  • Inspect status and version information.
Use JSON output for automation, but prevent command output containing live sender or receiver URLs from entering shared logs.

​
Validate the deployment

  • The service starts as a non-root user.
  • Configuration validation succeeds before service start.
  • The sender can reach the SRT ingest port.
  • The receiver can reach the SRT egress port.
  • The control port is not publicly exposed.
  • Invalid, wrong-role, and expired tokens are rejected.
  • Audio and video arrive as one synchronized stream.
  • Restarting the service follows the documented session-recovery behavior.
  • Unrelated OBS settings remain unchanged on both clients.

​
Capacity and recovery

Scene Share commonly uses 3–8 Mbps of video bandwidth per receiver, substantially more than audio-only collaboration.
  • Load-test the expected concurrent sessions.
  • Monitor ingress, egress, packet loss, process health, and disk state.
  • Document secret rotation and session invalidation.
  • Keep a rollback path for the service binary and configuration.
  • Re-run a sender/receiver clap test after upgrades.
Self-hosting changes who operates the relay; it does not add transcoding. The server must remain a forwarding service.