Ask us anything.

No. The model is outbound-only from the device to Front Desk. The site does not open inbound VNC, SSH, RDP, or admin ports.

No. Front Desk is a controlled remote-access path for specific devices and services — narrower than a VPN by design. VPNs join networks; Front Desk reaches devices. That narrower scope is easier to review, approve, and repeat across many customer premises.

No. Remote GUI is one access mode. Front Desk is aimed at field-device operations: GUI sessions, terminal access, local HTTP admin pages, logs, file transfer, commands, diagnostics, approval, and audit.

Those work for office users and attended support. Front Desk is aimed at fleets of devices installed in many places, usually with no one sitting at the keyboard.

Then the device becomes a public server, with the patching, password, and firewall exposure that brings. Front Desk exists so the device can stay private and still be reachable by the people responsible for it.

No. Front Desk complements telemetry, billing, monitoring, and RMM systems as the secure device contact path they can rely on — not a replacement for them.

Yes — that is the design target. The customer network normally only needs to allow outbound traffic to approved Front Desk domains. No inbound rules, no address planning, no site-to-site VPN project.

The product direction covers GUI access, SSH or terminal-style access, and local service access such as a device's web admin page. Actual support depends on the device operating system, agent version, and account configuration.

Yes. A customer contact, store manager, supervisor, or your own support lead can review an access attempt — who is asking, for which device — and approve or deny it before the session starts.

Then no live session is possible — and that is visible. The portal shows last contact time and current status, so support knows whether the device is reachable before anyone wastes a trip or a ticket.

If a device can wake and make outbound contact, it fits. A low-power controller can check in when it has Wi-Fi, report status or usage, receive supported actions, and sleep again. The portal always shows last contact and current reachability.

It can be part of that workflow. A rental controller can report usage time or activity windows when it checks in. Front Desk is not the billing system itself — it provides the secure contact path and the reported device data your billing uses.

The model is a strong conceptual fit for cash machines, kiosks, field terminals, and other customer-prem devices. Exact deployment depends on the device OS, security policy, and access method needed.

It follows a zero-trust-style direction: authenticate the device, authenticate the user, avoid broad network trust, scope access to the session, and make access visible — without treating that as a formal certification claim.

SSO, RBAC, audit export, retention controls, APIs, SIEM integration, signed installers, device groups, agent update control, and private deployment options — the product direction expects those requests.

No. Businesses with remote device fleets are the primary audience, but individuals and small teams also use it for remote machines or boards where opening ports was never an acceptable answer.