Beam Docs

Everything needed to understand Beam from first session to deployment.

Beam combines a desktop host app, a browser-ready join path, a relay-backed network layer, and a session API. These docs are the public reference for how those pieces fit together.

Desktop host app Browser viewer Relay + signaling Control-plane API

Quickstart

See how an operator launches Beam, starts a hosted session, and hands a viewer into the right join path.

Deployment

Review the relay, signaling, API, and media surfaces required to expose Beam in production.

API Reference

See the endpoints used to create sessions, exchange join information, and manage session lifecycle state.

Beam architecture at a glance

Host surface

The Windows host app gives operators a share code, hosting controls, recent sessions, and connection settings in one place.

Viewer surface

Beam is designed so the viewer can enter through a browser-friendly path rather than being redirected to a generic meeting client.

Infrastructure surface

Relay, signaling, WebRTC, and API services work together so a team can run Beam across normal internet connections and still keep control of the experience.