CyberCursor is a remote-access pilot for Windows, macOS and Linux, with attended Android sessions in evaluation, and a specific operating model. Every reason on this page points to the release record that backs it, and the last section lists what is not claimed.
The web portal shows the fleet, inventory, performance, groups, licences and users, and lists files read-only. Screen viewing, keyboard and mouse control, terminal commands and file changes are refused there by design and happen only in CyberCursor Remote, the installed Windows, macOS or Linux controller, over a signed channel that a browser cannot imitate. Teams get a clear answer to “where did that action come from”, and a compromised browser session cannot become a remote-control session.
Read the architecture pageWhen an operator connects, the endpoint displays a session notification and keeps a privacy bar visible for as long as the screen is shared. There is no setting that turns it off. Unattended access follows the owner’s initial setup and saved grants, so routine desktop support needs no approval prompt, yet the person at the computer always knows a session is open. On Android, the device user must accept every session and can stop sharing at any time. Two of the four competitors reviewed document an indicator that is absent or off by default in some modes; CyberCursor’s is unconditional.
Remote sessions in detailAn endpoint is enrolled with a client or group license key and an agent name, entered once in the installer or supplied as a protected file by a deployment system. The server chooses the tenant, organization and group; a signed, short-lived setup profile and a per-machine single-use grant complete enrollment, and the record appears in the intended workspace automatically. Revoking a key stops future installations without disconnecting enrolled computers. There is no operator-side ID-and-password pairing step to copy around.
How license-key enrollment worksA client administrator owns the workspace. Management users receive assigned endpoints and groups for ongoing work, with scope recomputed on every request. Guests are named people with specific endpoints, a view or control mode and a mandatory expiry of between one minute and thirty days; the server caps their sessions at that expiry and closes a live relay within a second of revocation. Every operator signs in with an authenticator, and the platform owner cannot open sessions at all.
Guest access in detail Access and audit contextPricing is on this site: $5 per endpoint per month up to 100 endpoints, $3 from 101 to 1,000, and $1 from 1,001, with the selected rate applied to every endpoint and billed month to month. There is no annual contract, no committed minimum quantity and no request-a-quote form. The comparison pages say plainly where a competitor is cheaper and where CyberCursor is, with the published rates and their sources beside the arithmetic.
Open the calculator Published competitor pricesA pilot is a pilot. These are the boundaries an evaluator should hold us to.
Not a security product. CyberCursor is not an endpoint detection or managed detection service. Vulnerability and file-event monitoring depend on a planned provider rollout.
No certifications. No SOC 2, ISO 27001 or sector compliance is claimed. The trust page states what evidence exists and what does not.
Evaluation builds. Only the Mac controller carries a Developer ID signature, and it is not yet notarized; the other desktop installers are unsigned and the Android APK uses the debug certificate. Physical-endpoint screen and input acceptance in production is a continuing release gate.
Limited platform testing. Linux is tested on Ubuntu 24.04 arm64 with X11 only, and Android on the Android 16 emulator only, with attended sessions and no unattended mode. Automation and patching are in preview with bounded foundations.
A channel boundary, not attestation. The signed controller channel stops a browser from imitating the app; it does not prove a managed device.
No customer stories. Solution pages are evaluation guides with fictional example data, not case studies.
The rows are shipped capabilities; competitors keep their ticks wherever their documentation shows the feature.
Swipe or scroll to compare all platforms →
Pilot, preview and planned, honestly staged.
Windows, macOS and Linux software, identity, groups, inventory, performance views and installed-app interactive workflows, plus attended Android sessions in evaluation.
Bounded job foundations and rollout design. Fleet-wide schedules, package coverage and production acceptance need separate validation.
Vulnerability and file-event foundations under evaluation. Production SOC coverage and independent assurance remain pending.
Start with a conversation about your fleet, your workflows, and a controlled pilot.
