Layerbit

LayerLink Host Terminal

Secure, browser-to-browser screen broadcasting via WebRTC technology.

Host capabilities require a desktop/laptop browser to capture the screen stream.

Transmission Control

System Idle
Stream Offline

WebRTC Architecture

LayerLink utilizes WebRTC (Web Real-Time Communication) to establish a secure, peer-to-peer (P2P) connection directly between your browser and the viewer's browser. Once the initial handshake is completed, video data flows directly between the two devices without passing through a centralized server.

Rapid Client Demos

Share your screen instantly with clients or stakeholders without forcing them to download external applications like Zoom or Microsoft Teams.

Pair Programming

Broadcast your IDE securely to a colleague. Because the connection is P2P, the latency is significantly lower than traditional cloud-routed video software.

Secure Troubleshooting

Share highly sensitive internal dashboards or server logs with remote IT staff, knowing the video stream is encrypted end-to-end and unrecorded.

UI State Simulation

Test the dynamic UI state handling of the LayerLink terminal without initializing hardware media streams. (Safe for mobile testing).

Engineering FAQ

The core JavaScript API required to capture a screen stream (navigator.mediaDevices.getDisplayMedia) is intentionally restricted by Apple and Google on mobile operating systems for security reasons. While a mobile device can view the stream, only a desktop/laptop environment can host it.

Firebase Realtime Database acts purely as the "Signaling Server." In order for a P2P connection to occur, both browsers need to exchange connection data (SDP offers and ICE candidates) so they know how to find each other on the internet. Once the connection is established, Firebase's job is done.

No, this architecture is strictly a 1-to-1 P2P connection. Scaling WebRTC to multiple viewers requires an SFU (Selective Forwarding Unit) server to process and distribute the video streams, which breaks the zero-trust P2P model used here.

Deployment Changelog