Marketplace billing in review

How IT Teams Let AI Touch Endpoints Without Risking the Farm.

FlowRMM is the safe execution plane for agentic endpoint operations. Connect your AI over native MCP to diagnose issues and stage remediations. A human approves every consequential command. Deployed 100% inside your own Azure subscription with zero vendor key custody.

LIVE SESSIONOperator: operator session
CPU / PlatformWindows workstation
Memory / QueueLive desktop stream
MCP ProtocolConnected · browser remote
GovernanceObserve or take control
Staged Action: Start viewing · Windows desktop
Awaiting Human ApprovalReview & Approve
Remote Console (Windows): live in-browser desktop, session list, and operator controls on an enrolled workstation.

Enterprise Architecture & Ecosystem Integration

Azure MarketplaceBicep deployment; billing in review
Microsoft Entra IDAzure AD & Conditional Access
Microsoft SentinelNative SIEM Forwarding
Azure Key VaultCustomer-Governed Secrets
Cross-PlatformWindows, macOS, Linux

The Architectural Shift

The Old Way vs. The FlowRMM Way

Why legacy RMMs (NinjaOne, ConnectWise, Kaseya) cannot safely operate in the AI era.

The Old Way

Legacy RMM Architecture

Manual Labor Bottleneck

Techs clicking buttons across hundreds of repetitive tickets. Tier 1 triage queues stay backed up for days while engineers handle mundane restarts and uninstalls.

Multi-Tenant Vendor Risk

Vendor cloud holds master credentials and remote keys across all customer accounts. A single breach of the vendor cloud compromises your entire client fleet.

Unchecked Privilege & Bolted-On "AI"

Scripts execute with raw admin privileges without four-eyes review, or marketing-deck chatbot "AI" that has no live endpoint access and cannot touch machines.

Opaque Billing & Multi-Year Lock-In

Multi-year contracts, predatory auto-renew clauses, punitive minimum seat sizes, and painful vendor churn cycles.

The FlowRMM Way

Safe Agentic Execution Plane

10x Ticket Velocity

AI models inspect endpoints via native Model Context Protocol (MCP) and stage remediations in seconds. Routine tickets are resolved in clicks instead of hours.

Zero Vendor Key Custody

Deployed 100% in your private Azure subscription. Remote streams, encryption keys, and audit logs stay strictly in your tenant under your own Sentinel and Key Vault.

Hard Governance (HITL)

Four-eyes approval default. Consequential work cannot run without human sign-off. Models diagnose and stage; humans govern and approve.

Predictable Margin

FlowRMM Business starts at $100/month with 100 endpoint-months included. Marketplace billing opens after publication.

Native Model Context Protocol

The Safe Bridge Between Models and Machines.

Connect Claude, ChatGPT, Codex, or local SLMs directly to your FlowRMM instance over native MCP (/api/v1/mcp). Models get read access to endpoint telemetry and can stage targeted remediations, but have zero autonomous execution rights without human approval.

1
Native MCP Server:

Compatible with standard MCP clients and desktop AI assistants.

2
Structured Tool Schema:

Strict typing for inspect_endpoint, get_process_tree, and stage_action.

3
Air-Gapped Execution Gate:

Staged actions require cryptographic human approval before the endpoint agent runs them.

MCP Request / Response StreamJSON-RPC 2.0
// 1. AI model stages remediation for acme-wks-01
{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "name": "stage_action",
    "arguments": {
      "target": "acme-wks-01",
      "kind": "powershell",
      "payload": "Restart-Service -Name Spooler -Force"
    }
  }
}
// 2. FlowRMM Governance Engine enforces HITL
{
  "status": "staged",
  "action_id": "act_acme_89bf21",
  "target": "acme-wks-01",
  "execution": "blocked_pending_approval",
  "policy": "four_eyes_mandatory",
  "assigned_operator": "alex@acme-msp.example"
}
  • Remote Console V1Windows and macOS view/control; Linux console and commands
  • Human gateFour-eyes by default for consequential actions
  • Azure MarketplaceDeploy into your tenant; credentials and audit stay in your Azure
  • Honest scopeMonitoring and fleet patching are not Cohort 01 claims

Live product stage

The same path, in the portal.Not a mockup.

Remote Console on a real enrolled endpoint. Get on the machine, queue a named action, keep the trail.

LIVEportal.example.com / home
Home: 12 enrolled endpoints, 9 healthy, empty approval queue, and one-click remote. Click to expand.
Shipping today · In scope

What you can actually run

  • Browser-native remote desktop & terminal sessions
  • Named actions on one computer (winget, PowerShell, shell)
  • Approval policy: four-eyes on high-risk work, auto-run only on low-impact scripts you choose
  • Native MCP so an agent can inspect and queue: a person still approves
  • Mobile-friendly triage from any modern browser
  • A book of companies: client, site, and the computers at each
Customer-owned Azure deployment

Your Azure. Your keys. Your approval.

  • Runs in your Azure: Deploy directly from Azure Marketplace or automated Bicep inside the tenant you already govern: VNet isolation, Microsoft Entra ID, Azure Key Vault, and Conditional Access.
  • Bring your LLM: ChatGPT, Claude, or a local SLM: if it speaks MCP, it can inspect endpoints and queue a named action. Nothing consequential runs until someone approves it.
  • Triage from a browser: Approve, inspect fleet state, and open a session from a phone. No operator desktop client.
FlowRMM sovereign single-tenant control plane running inside customer Azure subscription.
Azure VNet Isolation · Zero Master KeysTenant Custody

Flow Personal

Your computers. One simple place.

Create a passkey account, add a computer you own, then connect from your browser or phone. Your phone is a viewer and uses no computer slot.

Personal Free · $0

Two owned computers, indefinitely. No payment card required.

Personal Plus · $5/month

Ten computers total, in USD before applicable tax. Upgrade in your account when you need more computers.

Both plans include passkeys and the same available remote-control capabilities. No connection, minute, or session-duration charges. Available capabilities depend on your computer, permissions, and desktop session. Plus renews monthly until canceled; access continues through the paid period.

For adults in the United States using their own U.S. computers. Terms · Privacy and support

Connect your AI

Your AI. The right connection.

MCP connects a compatible AI app to FlowRMM. The Agent Plugin adds our operating instructions and the connection URL. You still sign in and review the requested access.

Flow Personal

Connect to your own computers with your Personal passkey. Your AI can inspect their status, request commands, capture screenshots, and request desktop input. Commands and input wait for your approval by default.

https://personal.flowrmm.com/api/v1/mcpDownload Personal Agent Plugin

Or paste the MCP URL into your AI app. Sign in and approve the connection; screenshots are included in that consent. Your Free or Plus computer limits still apply.

FlowRMM Business

Business connects to your organization’s own portal. Ask your administrator for its URL, then add /api/v1/mcp.

https://<your-business-portal>/api/v1/mcp

Download the Agent Plugin from that portal’s Installers page for a package with the correct URL. Sign in with your organization’s account. Its roles, licensed tools, and approval policies determine what your AI can do.

Each Business deployment has its own connection. The Personal URL reaches your Personal computers only.

Plugin downloads contain no credentials and grant no extra access. Availability depends on your AI app’s MCP or Agent Plugin support.

Architecture & security

No vendor-side broker holds your keys.

Hosting FlowRMM in your own Azure tenant keeps endpoint credentials, session streams, and audit logs inside the perimeter your team already governs.

  • Your perimeter

    Credentials, streams, and logs stay in tenant, behind your existing network and identity controls.

  • Microsoft Sentinel

    Forward session, control, and action events into the SIEM your SOC already watches.

  • Azure Key Vault

    Secret custody and rotation stay under your own vault policy, not ours.

Operator path

See it. Decide. Prove it.

Intelligence is cheap. Permission, execution, and proof are the product.

01 / 03

See it

session.live

The person at the keyboard reports it, or you open Remote Console from the browser and look yourself.

02 / 03

Decide if it runs

action.queued

A named action is staged. Policy says whether Alex can approve it, or whether a second person has to.

03 / 03

Prove it

audit.written

The box goes green and the person confirms. Session and action history stay with the team.

Environment: enrolled inventory, check-ins, and client / site context before you connect.
Actions: completed screenshot capture with request → approve → dispatch → exit 0 on the same record.

Product tour · Acme demo tenant

See the console in action.

Real operator-portal screenshots. Click any shot to expand it.

Slide 1 of 5
01 / Live Desktop & Terminal•
WindowsmacOSLinux (console)

In-Browser Remote Console for Windows, macOS, and Linux

“Connect to a user session or a background shell without installing a desktop client.”

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. Linux endpoints run the same agent for console and command work; remote view depends on the desktop session available.

  • Zero client downloads for operators: the full console runs in a standard web browser.
  • Multi-monitor displays, full-color rendering, and responsive keyboard and mouse input.
  • A session timeline records who connected, when, how long the session ran, and how it ended.
Console view:
LIVEacme / remote-console
Remote Console (macOS): live desktop in the browser, with Terminal, Xcode, and the dock.

Principle

Your LLM can know the fix. A person decides if it runs. The trail shows who approved it.

The FlowRMM operating principle

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 on the Security approach or the HITL operator guide.

Evaluating FlowRMM for a federal, state, local, tribal, or education environment? Review our public-sector readiness and certification path.

Flow · HITLreq_9a3f · 00:14
REQUESToperatorAPPROVEfour-eyesEXECUTEendpoint
t+00 requestedt+04 approvedt+09 exit 0
AI & HITL: four-eyes, self-elevate by environment, and kinds that always wait for a person.
Action autonomy: pick low-impact action kinds and environments; high-risk work still needs a person.

Example path

How Acme captures a screenshot with a human still in the seat.

One ticket, four handoffs: queue, approve, execute, record.

  1. 01Queue

    An MCP client queues a screenshot capture on an Acme Corp Mac.

  2. 02Approve

    A human Approves & runs the action, with four-eyes when policy says so.

  3. 03Execute

    The agent runs the approved capture and returns the image plus exit 0.

  4. 04Record

    The timeline keeps the handoff for the next operator on the ticket.

Public docs

Operator guides for the Cohort 01 path.

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

Closed pilot · Limited seats

Bring a real ticket queue. We will build with you.

Cohort 01 is not a webinar funnel. It is a fit-checked pilot with the people shipping the product.

  1. 01Fit

    We look at your environment, the workflow you care about, and whether Cohort 01 is the right test.

  2. 02Pilot

    You run the remote-console path with direct access to the people shipping the product.

  3. 03Feedback

    What breaks in your shop shapes what we harden next, not a survey nobody reads.

Frequently asked questions

Straight answers on architecture, Azure, and approvals.

Clear technical and operational details for MSPs, enterprise IT, and operators evaluating FlowRMM Cohort 01.

What is FlowRMM Cohort 01?+
FlowRMM Cohort 01 is an early-access, focused Remote Console for IT operators, MSPs, and internal IT teams. It provides browser-based remote desktop and terminal access, human-in-the-loop (HITL) approvals for consequential actions, immutable audit history, and native Model Context Protocol (MCP) integration. It is not a claim to replace every legacy RMM suite category on day one.
How does FlowRMM deploy to Microsoft Azure, and is it in the Azure Marketplace?+
FlowRMM deploys into your organization's own Azure subscription through its Azure Application listing or Bicep templates. The new Microsoft Marketplace billing offer is in review. Endpoints connect to your isolated instance, where keys and audit logs remain under your tenant governance.
How do AI agents connect to FlowRMM via Model Context Protocol (MCP)?+
FlowRMM includes a native Model Context Protocol (MCP) server endpoint (/api/v1/mcp). Compatible AI clients (such as Claude, ChatGPT, Codex, or local SLMs) can query live endpoint vitals and stage operational tasks. However, every mutating command is gated by human approval before it can execute.
What is Human-in-the-Loop (HITL) and four-eyes approval?+
By default, FlowRMM enforces the four-eyes principle: the person or agent proposing an action cannot approve it. Operators review the command payload, target machine, and risk level in the Actions queue. Once approved, the agent executes the task and returns exit codes and stdout.
What is the pricing model for FlowRMM Business?+
FlowRMM Business is $100 per month with 100 endpoint-months included, then $1 per additional endpoint-month. The FlowRMM + FlowPSA bundle is $150 per month with 100 included, then $1.50 each. New Business billing through Microsoft Marketplace opens after publication.
Which endpoint operating systems are supported?+
FlowRMM provides lightweight agents for Windows, macOS, and Linux endpoints. Supported capabilities include browser-native remote desktop view and control on Windows and macOS, and interactive terminal consoles and file copy across platforms.
Why choose customer-hosted Azure deployment over multi-tenant SaaS?+
Multi-tenant SaaS RMMs concentrate privileged endpoint credentials and remote keys on third-party vendor servers, making them prime targets for supply-chain attacks. FlowRMM eliminates vendor key custody by deploying into your own Azure subscription behind your Entra ID and Conditional Access policies.

Next step

See it on a live endpoint.

Book a 30-minute walkthrough of the path you just watched: get on the machine, stage a named action, decide if it runs. FlowRMM Business is $100 per month with 100 endpoint-months included, then $1 each. The call is the product, not a deck.

Fast path · 30 min

Book a Demo

Live product walkthrough for your workflow.

Not ready for a call? Apply in the form. Want to hang out first? Discord is open.

Cohort 01 · if a call is the wrong next step

By submitting, you’re asking us to contact you about Cohort 01. This is an early-access application, not a purchase or contract.