CyberCursor Remote 0.4.1 · Endpoint 0.3.2 · Easier desktop sign-inExplore the pilot builds
CyberCursor
EVALUATION HUB

Run a pilot that proves something.

Everything an evaluator needs in one place: the scope to agree, the checklist to follow, the evidence to keep and the guides behind each step. No sales call required to start.

Plan your evaluation Explore downloads
Pilot workflowCurrent availability
Angular monitors and laptops connected around a navy gateway cube
Original editorial illustration · Conceptual architecture
ON THIS PAGE01 / Five steps02 / What to record03 / Guides04 / Tools05 / Questions
THE CHECKLIST

Five steps, in order.

Each step produces an observation you can keep. Skipping one usually means a surprise later.

Pilot stepsFive stations: scope, enroll, observe, act, decide.01ScopeOwned Windows, Mac and Linuxcomputers or Android phones,their architectures, the02EnrollClient or group key and anagent name; confirm the recordlands in the right workspace03ObserveInventory, performance andreport freshness before anyinteractive work04ActView and control sessions,bounded files and terminalfrom the installed controller05DecideCompare observations with therecorded limits and the opengates, then widen or stopA PILOT IN WEEKS, NOT QUARTERS · EVERY STEP MAPS TO A GUIDE BELOW
Pilot stepsGuide-backed
01
Agree the scope

Computers, architectures, operator roles, locations and the workflows to evaluate.

02
Enroll a first group

Create keys, install the right build, finish local OS permissions, verify the record.

03
Read the context

Hardware, software, performance and the timestamp of each report; unavailable stays unavailable.

04
Act from the controller

Sessions with the endpoint notice, files within limits, single terminal commands.

05
Test the boundaries

Expired guests, revoked memberships, refused portal actions, offline endpoints.

06
Decide with evidence

Compare observations with the published limits and open gates before widening.

EVIDENCE

What to record.

An observation without its context is not evidence. Keep these together for every test.

BuildInstaller file name, version, architecture and SHA-256 from the downloads page
EndpointHostname, OS version, processor architecture, OS permissions granted
OperatorRole, scope, workspace, MFA state, controller version
NetworkConditions at the time: wired, wireless, proxy, VPN
OutcomeWhat changed on screen, what input landed, how the session ended, the audit entry
NegativesRefusals, expiries, revocations and partial failures, kept beside the successes
The evaluation guide in full
GUIDES

The guides behind each step.

Deployment, architecture, evaluation, operations and migration.

RESOURCESPILOT

Endpoint deployment guide

Prepare client ownership, groups, license keys, platform builds and acceptance checks for a controlled CyberCursor pilot.

Explore RESOURCESPILOT

CyberCursor platform architecture

Understand the roles of the web portal, installed controller, endpoint agent, identity controls and provider-connected reporting.

Explore RESOURCESPILOT

Endpoint platform evaluation checklist

Compare remote support, endpoint operations and security tools using workflow evidence, platform coverage and clear commercial assumptions.

Explore RESOURCESPILOT

Endpoint operations glossary

Understand endpoint agents, controllers, client scope, enrollment keys, freshness, canaries and verified outcomes.

Explore RESOURCESPILOT

Plan a controlled endpoint-tool migration

Map existing workflows, pilot CyberCursor alongside current tools and migrate only after platform-specific acceptance.

Explore
Choosing a platform Approved operations
TOOLS

Tools for the pilot.

Installers, checksums, availability and the comparison you can check.

01

Downloads. Windows, macOS and Linux controller and endpoint builds and the Android endpoint app, with checksums. Downloads

02

Status. Live readiness of the hosted service and the current availability labels. Service status

03

Pricing. The calculator and the whole-fleet rate curve. Pricing

04

Comparison. Shipped capabilities beside four vendors, every cell sourced. Compare

QUESTIONS

Questions evaluators ask.

From the guides.

What proves that a deployment is ready?

Verify client/group ownership, device identity, fresh reports and the actual required endpoint workflows. Installer completion alone is insufficient.

What is the most useful remote-access acceptance test?

Use an owned endpoint to verify actual screen and intended input behavior, current role scope, refusal after revocation and cleanup after the session.

Should a planned feature count as available in a comparison?

No. Keep planned, documented and independently tested capabilities distinct so the decision reflects current evidence.

Can I test using the offline demo devices?

Offline sample records cannot produce live monitoring or remote-control sessions. Enroll real owned test endpoints for actual acceptance.

Build your next endpoint workspace.

Start with a conversation about your fleet, your workflows, and a controlled pilot.

Talk to CyberCursorGet the desktop app