Choose between the web viewer and Windows Console, install a supported Windows or Linux host, manage devices with web admin, and understand how access is protected.
Managed access needs Farweo Host installed on Windows x64 or x86, or Ubuntu 24.04 LTS x64 in an active X11 session. For one-off attended help on Windows x64, the customer can run Quick Support without installing the Host. Connect from Windows Console or the browser viewer.
The full desktop workflow: remote control, file transfer, text and rich clipboard content, clipboard-file paste, and audio. Includes Wake-on-LAN setup and requests when enabled by the service administrator. Install on your Windows x64 PC without administrator access.
Remote control, text clipboard exchange, and file upload and download for online managed devices or customer-approved Quick Support. Browser clipboard access depends on browser permissions. Add it to your home screen as a progressive web app (PWA). Uploads go to the remote Downloads\RC folder. Sign in to the browser viewer.
The web viewer is a progressive web app (PWA): use it in your browser, or add it to your home screen and open it like an app. You do not need to install Windows Console on your phone or tablet.
Switch between pointer and direct touch modes, pinch to zoom, and use the on-screen keyboard and shortcut keys. Right-click and drag controls are available in the mobile toolbar.
Your phone or tablet needs an internet connection. The remote Windows PC or supported Linux X11 host must be powered on, online, and running Farweo Host. Adding the app to your home screen does not enable offline remote sessions.
Sign in to web admin with your Farweo account to add devices, update their names and groups, check online status and device health, and review activity. To control an online managed PC, use the web viewer.
The free Personal plan includes up to 3 managed devices and one connection at a time for personal, non-commercial use, without a five-minute session cutoff. Business plans cover one technician and up to 100 managed Windows PCs with unlimited concurrent connections. Both include web admin, the web viewer, and Windows Console. Personal signup does not start a trial. Choose Business at signup or start your one-time 90-day Business trial from Account plan whenever you’re ready. After expiry, subscribe for work use or select Personal and choose up to three devices for eligible non-commercial use; other devices stay saved. Compare Personal and Business. An Unlimited plan is also available. Enquire about pricing and plan terms. When enabled, organization workspaces add shared device ownership and individual permissions.
Organizations is an opt-in pilot enabled by the service administrator. Organization remote sessions must also be enabled. Business devices stay separate from personal devices and personal subscriptions. Teams pricing is $5 per member per month; contact us to arrange pilot access and team billing.
Owners manage settings, MFA policy, ownership transfer, and closure. Owners and admins manage members, teams, device groups, enrollment, and grants. Members need explicit device grants; Auditors can read audit records but cannot connect. Team Managers can manage existing members within their delegated team. Membership or an administrative role alone grants no remote access.
Attended access requires approval from the person at the host before a connection opens. Denial, timeout, or an unavailable dialog prevents access. Windows prompts the active console user; Linux needs zenity in the signed-in X11 session. Attended operators cannot block local input. Unattended access requires a separate explicit grant.
Organization devices require a signed-in account, active membership, and current grants. Host ID/password and guest access cannot bypass these requirements. Owners can require MFA. Permissions are enforced at the host and renewed during the session; revoked authorization or lost signaling closes access.
Removing a member clears their assignments while devices remain organization-owned. Overlapping grants can preserve access, so review the removal preview. Release device revokes its registration and requires fresh authorized enrollment to reuse it. Owners, admins, and Auditors can read and export audit records; historical attribution remains after departure.
Quick Support needs a separate explicit delegation from Members. The customer approves each temporary session and sees the operator's identity and organization; support does not enroll their device. Authorized operators use the selected workspace in Windows Console or the browser viewer. Customer-approved clipboard/files and chat are described in the Quick Support guide. Removing support permission ends access; granting it again cannot revive an old recovery ticket.
Use current Host and viewer versions. Organization wake requires a separate grant, approved target and relay settings, and an online relay in the same organization and approved LAN; requests and setup are available in the organization browser console. Windows host updates require an Update host grant. Linux hosts require a local package update. See Linux organization requirements.
The customer host enforces both choices. Browser clipboard sharing is text-only; Windows Console supports rich clipboard content and clipboard-file paste, which requires both permissions. File tools require file consent. Quick Support does not enable audio, secure attention or blocking local input.
Save your work, then use Approve restart and support recovery in the customer window. Current access ends. Quick Support reopens visibly at your next local sign-in; share a new code with the same technician and approve again within five minutes. Recovery cannot increase permissions or extend the original expiry. Applications may block the restart; there is no access before sign-in.
Temporary administrator support is currently disabled pending a trusted release. UAC approval and administrator credentials must be entered locally. Quick Support cannot remotely approve UAC or silently install an unattended Host.
Expiry, customer disconnect, lost signaling or revoked organization support permission ends access. Approved restart recovery is a one-use exception to the planned disconnect and still needs fresh consent. No device enrollment, background service or reusable unattended access is created.
Use compatible current Quick Support, viewer and server versions. Older versions retain screen/control only; optional tools, chat and recovery may require an upgrade.
Farweo uses its server to authenticate devices and coordinate each session. Screen, input, file, clipboard, and audio traffic then use encrypted WebRTC channels, connecting directly when possible and using a TURN relay when needed. Quick Support text chat passes through the authenticated signaling connection; it is not recorded in application audit or logs.
Access to managed devices starts with your Farweo account, with optional multi-factor authentication (MFA). For personal devices, connecting with a separate Host ID and device password remains a separate access method and is not protected by account MFA. Organization devices require account authentication and explicit permissions; password access cannot bypass them. The session is authenticated before remote-control channels open.
Enable an authenticator app in Account security. Once enabled, signing in to web admin, the web viewer, or Windows Console requires your password and a six-digit authenticator code or a single-use recovery code.
Host passwords are protected with Argon2id hashing. Plaintext passwords are not stored by the service.
When connecting with a Host ID and device password, a challenge-response flow using HMAC verifies access without sending the saved password as a reusable secret.
WebRTC protects the live screen, control, audio, clipboard, and file-transfer channels in transit.
The host requires administrator approval, generates its access details during setup, and is installed under Program Files.
Enabling or disabling MFA, or replacing recovery codes, signs out all account sessions. Sign in again after saving your codes. Replacing recovery codes invalidates the previous set.
To disable MFA or replace recovery codes, enter your current password and a fresh authenticator code or an unused recovery code in Account security. Password recovery does not remove MFA.
Install the Host only on computers you are authorized to support. Setup.exe performs the following steps:
This optional feature is disabled by default and requires the service administrator to enable it. In Windows Console, you can request a wake for a configured offline device assigned to your account. An approved, awake Windows or Linux Farweo Host on the target's LAN sends the magic packet; the server coordinates through the relay's authenticated connection.
Automatic selection uses one eligible relay first, with at most one fallback after delivery failure. You can instead select an eligible relay manually. Both devices need explicit approval for the same network under the same account, and the relay needs a local administrator-provisioned allowlist.
“Sending wake request” is followed by “Packet sent; waiting for device”. “Device online” appears only after the intended authenticated Farweo Host reconnects. A successful send means the relay's OS accepted the packet; it does not prove reception or wake.
Optionally open the existing connection flow when the Host comes online. Ordinary access authorization still applies. Cancel to prevent later relay attempts and automatic connection; packets already sent cannot be retracted. Reopen Wake to restore an active request's status.
Windows target setup and diagnostics are included, with Windows and Linux relay delivery and Linux target inventory/guidance. Physical hardware wake tests have not yet been completed. Wi-Fi wake is not guaranteed, and macOS wake support is not implemented.
For organization devices, use the organization browser console with an explicit Wake grant. An owner or admin approves the network, adapters, and relay policy. Both devices must belong to that organization; personal wake approvals do not carry over on transfer. The local relay allowlist and hardware requirements below still apply.
Packets use outbound UDP port 9 on the relay's selected connected IPv4 subnet. No public UDP forwarding, inbound target listener, or router automation is needed. Quick Support sessions cannot act as enrolled wake relays. The initial rollout requires one enabled server instance; the service administrator must confirm this before enabling Wake.
“Device online” means the Host came online after the request; Farweo cannot prove the packet caused it. Magic packets have no meaningful sender authentication on the LAN, so trusted network access remains important. See Linux relay and target guidance.
View the remote desktop and send mouse and keyboard input. Secure desktop control requires a supported installed Windows Host; Quick Support keeps UAC and sign-in input local.
Browse, send, receive, and follow transfer progress over a dedicated data channel.
Move text, rich content, images, and clipboard files between the host and viewer.
View online status, CPU, memory, disk, uptime, pending restarts, and recent activity.
The remote PC must be powered on and connected to the internet. Managed access requires the Host running; unattended access does not require a person at the keyboard after setup. Quick Support needs the customer app open and local approval. For a configured offline managed device, administrator-enabled Wake-on-LAN can request a wake first through an approved awake LAN relay.
Windows x64 and x86. Administrator access is required for the initial service installation. Download the x86 installer for 32-bit Windows. Linux Host is available for Ubuntu 24.04 LTS x64 with X11.
Windows x64. Install Farweo Console for your Windows account, then launch it from the Start menu. No administrator access is needed.
Create a free account for Personal use or choose Business to start a 90-day trial, and install the Host on your remote PC. Choose the web viewer or Windows Console to connect.