Handle more than one session
Keep several trusted devices available and move between active sessions without losing your place.
Be there, even when you cannot be there.
See the screen they choose to share, guide every step, and control supported devices after they approve access.
Open a secure session, see what they see, and handle the hard part together. Remote Assist keeps controls close and active sessions easy to manage.
Keep several trusted devices available and move between active sessions without losing your place.
Video adapts to weak networks, then spends available bandwidth sharpening a screen that has stopped moving.
Pause streaming, keep a lightweight heartbeat, and ask the Endpoint to resume when support is needed again.
Install Controller where help begins. Install Endpoint on the phone or computer receiving assistance.
See enrolled devices, rename them, open multiple sessions, send text and keys, zoom, sleep, resume, minimize, or end assistance.
Get Controller
The person receiving help sees readiness, permissions, identity, and active assistance in one clear place.
Get Endpoint
Use Google or email and password in Controller. This account keeps every enrolled device separate from other customers.
Enter the short setup key shown on the receiving device. Its installation identity is then remembered securely.
Choose the device and connect. The Endpoint shows the request and the operating system asks for required sharing permissions.
Remote Assist removes repeated account setup while preserving the approval and screen-sharing prompts required by each operating system.
Read the security answersEvery enrolled device proves possession of its private key. An unexpected identity change requires enrollment again.
Screen video and input travel over encrypted peer channels, with the production service coordinating authenticated sessions.
Endpoint status stays visible. Android and Apple capture prompts cannot be silently bypassed by the app.
The service relays session coordination and does not provide cloud video recording in this release.
Each app follows its operating system while sharing the same account, device, session, and language model.
Controller is for the helper. Endpoint is for the device receiving assistance. Both connect only to the production service.
Android APKs are release-signed. macOS is not notarized, Windows is not Authenticode-signed, and iOS currently provides an Apple Silicon Simulator build rather than a physical-device IPA.
Remote access should be understandable. These are the important limits and expectations.
Yes. The one-time setup key enrolls that installation. Later account access is automatic until the device is removed, its identity changes, or trust is revoked. Operating-system capture consent may still be required.
No. Endpoint status remains visible, and Android, iOS, and macOS enforce their own screen-sharing and permission prompts. Remote Assist does not bypass them.
Android, macOS, Windows, and Linux X11 support approved control within operating-system limits. iOS and Linux Wayland are view-only in this release.
The video profile lowers motion frame rate and resolution before sacrificing control delivery. When movement stops, available bandwidth is used to improve picture detail.
Yes. One Controller account can enroll multiple Endpoints and keep multiple independent sessions open. Each Endpoint accepts one helper session at a time.
Version 0.4.0 is an early-access release for controlled use. Broad deployment still requires platform store signing, independent security review, managed operations, monitoring, and physical-device coverage.
Install Controller, add the devices you support once, and be ready when someone calls for help.