Skip to content
AI Operator · Built into every Breeze deployment

An RMM with an
AI operator built in.

Breeze isn't a dashboard you operate — it's an RMM with an AI operator built in that works the fleet for you. The operator triages alerts, patches fleets, writes scripts, and generates compliance reports using the same tools your techs use, governed by a 4-tier risk engine you control so it can never run amok.

Free and open source. BYOK with your Anthropic key. Optional managed mode via LanternOps Brain.

What the operator actually does

Four real conversations. Same tools your techs use.

Every action is classified, logged, and reversible. The operator proposes — your risk engine decides.

Triage Operator online
YOU
Why is ACME-LAPTOP-04 slow today?
OPERATOR
Disk at 96% capacity. Top consumers: Chrome cache (12GB), old Windows update files (8GB). I can clear the cache and run cleanmgr — this is a Tier 2 action, auto-approved. Proceed?
Patch ops Operator online
YOU
Patch all Windows servers for client BlueRidge tonight at 2am.
OPERATOR
Found 14 servers. 11 are in maintenance window 02:00–04:00 (auto-approve). 3 are domain controllers (Tier 3 — approval required). Drafting approval request now.
Security Operator online
YOU
Which devices are missing endpoint protection?
OPERATOR
7 devices across 3 tenants. 4 missing Microsoft Defender real-time scanning, 3 have SentinelOne agent uninstalled. Want me to redeploy the SentinelOne agent or open a ticket?
Reports Operator online
YOU
Generate a CIS compliance report for Q1 for client Northwind.
OPERATOR
Pulled audit logs, control coverage, and exceptions for Jan 1 – Mar 31. 13 of 18 CIS Controls fully automated. Report saved to /reports/northwind-q1-2026.pdf — preview attached.

Examples are representative. The operator's exact responses depend on your fleet state, policies, and risk classifications.

Click through the live UI

Watch the operator investigate a real device issue.

Interactive Demo

Tool catalog

The operator uses the same APIs your techs use.

Every RMM capability is exposed to the operator as a standardized tool. Each tool has a risk tier. The same reboot is Tier 2 inside a maintenance window and Tier 3 outside one — context drives policy automatically.

Device Tools

List devices, get details, query fleet state

Alert Tools

Retrieve, update status, link to tickets

Action Tools

Reboot, shutdown, lock, isolate, install, uninstall

Patch Tools

Status, schedule, deploy with maintenance windows

Script Tools

PowerShell, Bash, or Python with result retrieval

Report Tools

Compliance, security, inventory, executive reports

Risk Engine, always on: Tier 1 reads run free. Tier 2 mutations auto-execute and audit log. Tier 3 actions wait for human approval. Tier 4 is blocked. You set the policy — the operator follows it.

Run the operator in your own RMM tonight.

Self-host Breeze, drop in your Anthropic API key, start asking questions.

Two ways to run the operator

Same tools. Same guardrails. Pick where the reasoning runs.

BYOK Mode

Bring Your Own Key · Free

Included with every Breeze deployment

  • Your Anthropic API key
  • Single-agent reactive loop
  • Tools call local functions directly
  • Basic risk classification

Good enough to be useful. Limited enough to upgrade.

LanternOps Brain

Managed AI · Per-endpoint pricing

Everything BYOK can't do

  • Multi-agent orchestration (triage → remediation → compliance)
  • Persistent memory per tenant
  • Cross-tenant intelligence (anonymized patterns across all managed tenants)
  • Automated playbook library
  • Compliance evidence generation (NIST, CIS, SOC 2, HIPAA)
  • Proactive anomaly detection

Same tools. Smarter brain. Zero migration.

Upgrade path: Deploy free → add your API key → one-click connect to LanternOps when ready. No migration, no data moves.

Your RMM is always the final authority

LanternOps can request actions. Your Breeze instance decides whether to allow them. Risk classification is enforced at the RMM level — not the operator level. Double validation: LanternOps pre-validates with its intelligence layer, then your RMM re-validates with its risk engine. Belt and suspenders.

Every action is auditable. Every tool call is logged. Every approval decision is recorded.

FAQ

Common questions about the AI operator

What is the Breeze AI operator?

The AI operator is the autonomous layer built into every Breeze RMM deployment — it works the fleet for you instead of waiting to be operated. It uses the same tools and APIs your technicians use — listing devices, querying alerts, running scripts, scheduling patches, generating reports — and it operates under a 4-tier risk engine that classifies every action before execution. You ask in plain English; the operator proposes; your risk engine decides whether the action runs automatically, requires approval, or is blocked. The reasoning engine behind it is called Breeze Brain.

Do I need an AI API key to use the operator?

Yes for BYOK (Bring Your Own Key) mode, which is included free with every Breeze deployment. You provide your own Anthropic API key in settings and the operator runs locally inside your RMM. LanternOps Brain is an optional managed mode where LanternOps hosts the reasoning engine for you and adds persistent memory, cross-tenant intelligence, and automated playbooks — no key required from you.

Can the operator take destructive actions on my fleet?

Only within the limits your risk engine defines. Tier 1 (reads) runs freely. Tier 2 (low-risk mutations like cache clears) auto-executes and is audit-logged. Tier 3 (impactful actions like reboots, domain controller patches, agent uninstalls) requires human approval. Tier 4 is blocked outright. Context shifts tiers — a reboot inside a maintenance window is Tier 2; outside one it is Tier 3. The risk engine is enforced at the RMM level, not the operator level.

How is the Breeze operator different from generic AI like ChatGPT?

ChatGPT and similar chat tools have no access to your fleet, no concept of devices or alerts, and no execution authority. The Breeze operator is wired into your RMM's tool catalog — device tools, alert tools, action tools, patch tools, script tools, report tools — and every call it makes is governed, logged, and reversible. It can investigate a slow laptop, deploy a patch, or generate a compliance report end-to-end, not just describe how you would do it.

What is the difference between BYOK Brain and LanternOps Brain?

BYOK Brain is free, runs locally with your Anthropic API key, and reacts to one event at a time with no memory across sessions. LanternOps Brain is managed, includes persistent per-tenant memory, anonymized cross-tenant intelligence, an automated playbook library, multi-agent orchestration, and compliance evidence generation for NIST, CIS, SOC 2, and HIPAA. Both drive the same operator — the same tool catalog and the same risk engine. Only the reasoning layer changes.

Can I upgrade from BYOK to LanternOps Brain later?

Yes. The upgrade is one click — Settings → AI Brain → LanternOps → Connect, then authorize via OAuth. Your Breeze instance does not change. Same tools, same risk engine, same data. LanternOps Brain connects remotely through the Brain Connector API. No migration, no data movement, no downtime.

Stop alt-tabbing through 12 dashboards.

The operator investigates, acts, and documents — inside your RMM, governed by your policies. Free and open-source. No vendor lock-in.