Desktop host app
Operators start hosting, copy the generated connection ID, review recent sessions, and tune relay settings from a dedicated Windows app.
Desktop host app + browser viewer + relay stack
Remote screen sharing that looks like your product, not a meeting tool.
Beam gives operators a desktop host app, viewers a browser-based join flow, and your team a clean control-plane API for managing sessions end to end.
- Desktop host app with share code, recent sessions, and relay settings
- Browser-ready viewer flow powered by signaling, relay, and WebRTC
- Session API for provisioning joins, lifecycle state, and embedded workflows
Relay mode
Connect from anywhere through the Beam relay host.
Session API
Mint sessions, join tokens, and viewer entry points.
What Beam includes
A complete remote assistance stack, not just a single app window.
Browser viewer flow
Customers or teammates can enter the session through a browser-friendly path that can be embedded and branded for your own experience.
Relay + signaling
Beam ships signaling, UDP relay, control-plane lifecycle endpoints, and WebRTC signaling so sessions work across networks without exposing host machines directly.
Control-plane API
Create sessions, accept them, end them, and exchange join tokens over a simple REST surface designed for support flows and internal tooling.
How it works
Beam covers the session from operator launch to viewer connect.
Host launches Beam
The desktop app opens in relay mode, generates a share code, and exposes hosting controls directly from the home screen.
Session is created
Your product or operations tooling can create a session over the Beam API, track state, and route viewers with a join token.
Viewer joins through the browser
The viewer gets signaling information, relay parameters, and WebRTC session details without installing a generic meeting client.
Beam keeps the session moving
Relay, signaling, and WebRTC services stay aligned so support, onboarding, and ops sessions remain responsive under real usage.
Who it is for
Built for support, onboarding, QA, and internal operations teams.
Beam is the right fit when you want remote viewing and assistance to feel like part of your own product. It is especially useful for support desks, customer success, onboarding teams, internal operations, and controlled administrative workflows.
Production readiness
The public site should explain the real Beam stack from desktop app to API.
Current Beam production surfaces
- Public marketing site at
beam.be-online.ro - Beam desktop app in relay mode pointing at
relay.be-online.ro - Control-plane API with session lifecycle and join token exchange
- WebRTC signaling and media relay for browser-based viewing
What changed in this production pass
- Removed generic template messaging and replaced it with Beam-specific product content
- Changed the full site palette to Beam’s red-led visual direction
- Added real docs covering quickstart, deployment, and API usage
- Re-centered the content around the actual Beam product and flow
What to read next
FAQ
Answers that match the real Beam product.
Why does the public site look different now?
The previous public page still inherited structure and copy from a third-party SaaS template. This production pass replaces that mismatch with Beam-specific product, workflow, and documentation content.
Does Beam require both sides to install software?
No. The operator uses the desktop host app, while viewer flows can be handled through browser entry points backed by Beam’s signaling, relay, and WebRTC stack.
Can Beam be embedded into our own platform?
Yes. The session API exists specifically so a third-party product can create sessions, distribute join tokens, and manage status from its own support or admin workflow.
Ship it properly