Cohort01 / open

Regionglobal

Cohort 01 · Applications Open

FlowRMM

Browser-based Remote Console for Windows, macOS & Linux.

Direct endpoint access, targeted operator actions, human-in-the-loop approvals, and a clear audit log — built for MSPs, internal IT, and small operators who act as responsible caretakers for their fleet.

Book a Demo 📸 Feature Deck & Screenshots ↓Apply for Cohort 01

LIVE

Live Console Preview

Remote desktop session on macOS & Windows endpoints

Click to open the 5-slide Feature Deck ↓

Scroll to explore screenshots & product deck ↓

● remote consoleendpoint access● human approvalssigned actions● audit trailwindows · macos · linuxmsp cohort 01● live pilot

✓ What FlowRMM Cohort 01 Is

Responsible fleet stewardship for operators

•Browser-native Remote Desktop & Terminal session streams
•Targeted script & command execution (winget, PowerShell, shell)
•Four-eyes Human-in-the-Loop (HITL) approval guardrails
•Multi-tenant client/site endpoint check-in timeline

🚫 What FlowRMM Is Not (Yet)

No bloated unattended black-box automation

•Not overselling full unattended auto-remediation on day one
•No unvetted scripts running in secret behind your back
•Not a complex Intune/MDM replacement project
•No lock-in — straightforward pilot access for real technicians

Interactive Product Deck · Acme Demo Tenant

See the console in action.

Explore actual interface screenshots from our Acme operator portal. Click any screenshot to open in full HD view.

Slide 1 of 5

01 / Live Desktop & Terminal•

WindowsmacOSLinux

In-Browser Remote Console for Windows, macOS & Linux

“Connect directly to user sessions or terminal background without installing bulky desktop apps.”

FlowRMM provides browser-native remote desktop and terminal sessions on enrolled endpoints. Operators can view display streams, take keyboard/mouse control, or launch elevated diagnostic consoles on demand.

✓Zero client downloads for operators — full console inside your standard web browser.
✓Supports multi-monitor displays, crisp color rendering, and low-latency input streaming.
✓Unified session timeline logs exactly when an operator connected, active duration, and session termination.

Console view:

Book a Demo with this View Apply for Cohort 01 access →

portal.flowrmm.com / demo / acme / remote-console

FlowRMM Remote Console session on an Acme macOS endpoint showing live desktop stream and operator controls. — Remote Console (macOS): In-browser screen control, input stream, and session diagnostics on Acme HQ workstation.

“The point isn’t automation for its own sake. It’s responsible fleet caretaking — giving operators a remote workspace where they can move fast, hand off cleanly, and protect endpoints, on the record.”

— the FlowRMM operating principle

Inside the console

The Acme pilot surface, live Remote Console, not a mockup.

Screens below are from the FlowRMM operator portal used in our Acme demo tenant.

portal.flowrmm.com / endpoints / acme-mac-01 / remote console

FlowRMM Remote Console session on an Acme macOS endpoint with live desktop stream, session controls, and operator diagnostics. — Remote Console (macOS): browser remote desktop, console, and handoff status on an enrolled endpoint. Click to expand.

Cohort scope

What you can actually try in the first pilot.

FlowRMM isn’t pitching a cold script bot on day one. Cohort 01 is built for the human caretakers responsible for the day-to-day maintenance, security, and health of user endpoints.

01 / 03

Get on the machine

session.live

Open a remote session from the browser, use the interactive console, and move files while you’re helping the customer.

02 / 03

Dispatch the work

action.queued

Prepare targeted actions and require a person to approve them when the action, or your policy, says they should.

03 / 03

Leave a trail

audit.written

Session, control, and action history stay with the team so the next person isn’t starting from scratch.

FlowRMM Endpoints inventory showing enrolled Acme devices, online status, and client or site assignment. — Endpoints: enrolled inventory, check-ins, and client / site context before you connect.

FlowRMM Actions showing a completed winget uninstall of Google Chrome on Windows endpoint CAKE-PC with exit 0 output. — Actions: MCP-queued winget uninstall of Google Chrome on Windows (CAKE-PC), approved, executed, exit 0.

Governance & HITL

Humans stay in the loop before consequential work runs.

Governance sets who can approve what: four-eyes by default, optional self-elevate by client environment, and action autonomy that can auto-approve only low-impact kinds. High-risk actions stay human-gated.

More detail on the Security approach page, or the HITL operator guide.

Flow · HITLreq_9a3f · 00:14

t+00 requestedt+04 approvedt+09 exit 0

FlowRMM Governance HITL self-elevate settings with four-eyes default and client environment allowlist. — HITL self-elevate: four-eyes stays default; allow-listed environments when an operator may approve their own request.

FlowRMM Governance Action autonomy controls for selecting low-impact action types that can auto-approve. — Action autonomy: pick low-impact action kinds and environments; high-risk work still needs a person.

Example path

How Acme removes Chrome on a Windows endpoint.

In the Acme example, an operator queues a winget uninstall for an Acme Corp workstation, a human Approves & runs on Actions, the Windows agent executes, and the timeline keeps the handoff.

Read the walkthrough Remote Console docs

Public docs

Operator guides for the Cohort 01 path.

Enroll an Acme-style endpoint, open Remote Console, and practice Approve & run, the same narrative as the marketing pages, written for operators.

Browse docs Get started

Out of scope for now

We won’t sell you a roadmap as a product.

Monitoring, alerting, patching at scale, Intune orchestration, and broad unattended automation are later product work, not Cohort 01 commitments. HITL approvals and the Governance controls above are part of the remote-console evaluation path.

Windows, macOS, and Linux are in the agent footprint. How remote control feels depends on the OS, the desktop session, and permissions. We’ll sort that fit with each cohort team instead of papering over it.

Launch partners

Bring a real ticket queue. We’ll build with you.

01Fit
We look at your environment, the workflow you care about, and whether Cohort 01 is the right test.
02Pilot
You run the remote-console path with direct access to the people shipping the product.
03Feedback
What breaks in your shop shapes what we harden next, not a survey nobody reads.

Cohort 01

Tell us who you are.

We’ll use this to check fit and plan a sensible pilot. Cohort pricing is by conversation; public plans come later.