Remote Console V1

The essentials for accountable remote work.

Cohort 01 is centered on the support session, not a claim to replace every RMM category on day one. Windows, macOS, and Linux agents are in the footprint; the shot below is a live Windows remote session from our Acme demo tenant.

Acme demo tenant: Windows Remote Console (CAKE-PC) with live desktop stream, session controls, and operator handoff. Click to expand.

Cohort scope

What we are putting in customers’ hands now.

Endpoint inventory

Organize and inspect enrolled endpoints, clients, and sites before starting work.

Remote workspace

Use browser-based remote view/control, console, and file-copy workflows on Windows and macOS where the endpoint environment supports them.

Actions, HITL, and audit

Queue operator actions for Approve & run, keep four-eyes (or scoped self-elevate) in Governance, and retain session and action history for follow-up.

Approvals in the product

Actions queue and Governance HITL.

Restricted work lands in Actions for a human decision. Governance sets autonomy ceilings and when an operator may approve their own request.

Actions: real Windows package removal via winget on CAKE-PC (MCP request → approve → execute → audit).
Governance: HITL self-elevate and four-eyes defaults for the shared action plane.

Not a public promise today

Deliberately outside the first cohort’s product claim.

Monitoring and alerts

A future licensed RMM module, not a Cohort 01 promise.

Patching at scale

Not part of the initial public offer.

Fleet compliance scorecards

Broader standards / exposure scorecard packaging is still hardening, beyond the HITL and action-autonomy controls available for cohort evaluation.

Operator docs

Read the matching public guides.