Desktop host app
Operators launch Beam on Windows, get a share code instantly, start or stop hosting, and reuse prior session IDs from recent history.
Private remote assistance for SaaS teams
Support sessions that feel like part of your product.
Beam gives your team a desktop host app, a browser-ready join flow, and a relay-backed session stack so remote help does not have to feel like sending users into a generic meeting room.
- Desktop host app with share code, hosting controls, recent sessions, and settings
- Browser join path for customers, teammates, or internal users
- Relay, signaling, and API surfaces for real production workflows
Support
Customer success
Internal IT
Onboarding
Host app
Start a session, copy the code, and control when hosting is live.
Viewer flow
Send people to a cleaner browser join experience backed by Beam relay services.
Designed for the teams that live in real customer sessions:
What Beam includes
A real product stack from host app to browser join.
Beam is not only a screen host window. It brings together the desktop operator surface, the viewer entry experience, the network relay layer, and the session API needed to integrate all of that into a product or support operation.
Browser viewer path
Guests can join through a browser-facing flow so the session feels product-led instead of being handed off to a third-party conferencing brand.
Relay + signaling
Beam runs signaling, UDP relay, WebRTC signaling, and media negotiation so sessions work across ordinary networks without exposing host machines directly.
Session API
Your own product can create sessions, exchange join tokens, and manage lifecycle state through a simple control-plane API.
Workflow
Beam keeps the remote help flow straightforward.
The product is most useful when the operator path, the guest path, and the network path all stay understandable. Beam is built around that idea.
Operator opens Beam
The desktop app shows a share code immediately, exposes hosting controls, and gives the operator a direct view of the current session path.
Viewer gets a controlled entry point
Use the Beam join flow from your own support workflow, portal, admin surface, or browser handoff without switching to a generic meeting experience.
Relay handles the network layer
Beam coordinates signaling, relay traffic, and WebRTC negotiation so the session keeps moving across real-world networks.
API keeps the session manageable
Create, accept, inspect, and end sessions through a control-plane API so product teams are not locked into a manual-only support flow.
Why this matters to end users
- The host sees a clean, obvious start path instead of hidden network setup.
- The viewer can be sent into a controlled browser journey.
- Your team can document the product honestly because the system has clear surfaces.
- The public site, docs, and product can finally describe the same thing.
Use cases
Built for teams that need to help users, not schedule meetings.
Beam works best where a product team wants a support-ready, browser-friendly remote session path that can be integrated, branded, and documented without pretending to be a general-purpose calling app.
Customer support
Give support agents a direct host app and a safer handoff path for users who need help on a live screen.
Onboarding
Walk new customers through setup or training sessions without leaving the product context you already control.
Internal operations
Use Beam for admin, back-office, or IT workflows where remote help needs to stay private and predictable.
Production
A production-ready public site should match the real Beam stack.
That means product copy that reflects the desktop app, docs that describe the actual flow, and public pages that point to the right operational surfaces instead of fake pricing, template language, or unrelated imagery.
Quickstart
Learn how the host app works, what the share code does, and how a session begins for the operator and viewer.
Deployment
Review the relay, signaling, API, and WebRTC ports, plus the network model needed to expose Beam safely.
API reference
Use the control-plane API to create sessions, return join information, and manage lifecycle state programmatically.
FAQ
Questions people will actually have when evaluating Beam.
Is Beam a support tool or a meeting tool?
Beam is meant for product-led remote assistance. The goal is to support or guide a user through a remote session path that can live inside your own workflow.
Does the guest need the Windows app too?
No. The operator hosts from the desktop app. Viewer entry is designed around a browser-facing flow backed by Beam’s signaling and relay services.
Can Beam run on our own infrastructure?
Yes. The current deployment model uses a relay host, signaling ports, API surface, and WebRTC media range that can be deployed on your own VPS stack.
Can another product create and control sessions?
Yes. Beam exposes a session lifecycle API so your own app or internal system can create sessions, distribute join data, and manage status.
Why use Beam instead of a generic conferencing link?
Because Beam is built around a host app, a controlled join path, and an integration surface that can feel like part of your own product.
Where should a new team start?
Start with the docs overview, then read Quickstart for the operator path, Deployment for the infrastructure path, and API for the integration path.
Read the whole stack