Remote monitoring and management for MSPs
Monitor every endpoint across every client, get alerted before users notice, and resolve issues at scale with remote scripting, all from one multi-tenant console.
Overview
- Domain controller unreachableACME-DC01 · Acme Legal
- Disk C: above 90%NWD-WS-114 · Northwind
- Print Spooler stoppedCTS-FS01 · Contoso
- CPU above 95% for 10 minACME-SQL02 · Acme Legal
| Device | Client | OS | CPU | Disk | Status | Last seen |
|---|---|---|---|---|---|---|
| ACME-DC01 | Acme Legal | Server 2022 | 96% | 48% | Critical | 2 min ago |
| NWD-WS-114 | Northwind | Windows 11 | 31% | 91% | Warning | Just now |
| CTS-SQL02 | Contoso | Server 2019 | 42% | 63% | Healthy | Just now |
The core toolkit for running a managed services practice
Ops RMM focuses on the work technicians do every day: knowing what is wrong, and fixing it quickly across many clients.
Real-time monitoring
CPU, memory, disk, services and event logs from every endpoint, refreshed continuously.
Alert policies
Threshold and condition rules per client or site, routed to email, webhooks or your PSA.
Remote scripting
Run PowerShell on one device or an entire client, on demand or on a schedule.
Multi-tenant hierarchy
Clients, sites and devices are isolated, each with their own policies and access.
Asset inventory
Hardware, installed software and OS details collected automatically by the agent.
Telegram security bot
Every sign-in sent to your phone, with one-tap sign-out, IP blocking, device search and status.
Two-step sign-in
Google Authenticator or Telegram codes, with secure password recovery and no SMS.
IP access rules
Allow-list your offices and block suspicious addresses, from the console or the bot.
Scheduled automation
Run scripts daily, weekly or once, in your workspace time zone, across any target.
Complete audit trail
Who signed in, what changed and which script ran where, recorded and searchable.
16 languages
The console speaks your team's language, including right-to-left layouts, with 12 themes to choose from.
Patch managementPlanned
Approve and deploy Windows updates by policy, with compliance reporting per client.
Find problems before your clients call
Define alert policies once and apply them across clients. Every alert carries the device, client and context a technician needs to act.
- Thresholds for CPU, memory, disk and services
- Severity levels with acknowledgement and escalation
- Per-client overrides without duplicating policies
Resolve issues across a fleet in one run
Target a single device, a site or a whole client. Output and exit codes return per endpoint, and every run is recorded.
- Shared, versioned script library
- Run on demand, on a schedule, or from an alert
- Full audit trail of who ran what, and where
# Remove temporary files older than 7 days $cutoff = (Get-Date).AddDays(-7) $paths = "$env:TEMP", "C:\Windows\Temp" foreach ($p in $paths) { Get-ChildItem $p -Recurse -File -ErrorAction SilentlyContinue | Where-Object { $_.LastWriteTime -lt $cutoff } | Remove-Item -Force -ErrorAction SilentlyContinue }
One console for every client you manage
Work across all clients at once or focus on one. Technician permissions follow the structure of your business.
- Client, site and device hierarchy
- Role-based access per client
- Client-level reporting
Everything in one console
Built for technicians who manage many clients, and for owners who need to know it is locked down.
Devices
- Online and offline status per client
- Hardware, software and service inventory
- Search by name, IP, user or serial
- Move devices between clients and sites
- Maintenance mode to silence alerts
Automation
- Script library in 12 languages
- Run on one device or a whole client
- Schedules in your time zone
- Output and exit code per device
- Restart, shut down and send messages
Alerts and reporting
- CPU, memory, disk and service alerts
- Acknowledge and resolve with history
- Device online/offline messages in Telegram
- Per-client health at a glance
- CSV export of clients and devices
Workspace
- Clients with their own logo and sites
- Roles and permissions per technician
- 12 themes and 13 accent colours
- Custom sign-in wallpaper
- 16 languages, including right-to-left
Designed for the access an RMM holds
An RMM can reach every machine you manage. Ops RMM treats that access as the primary risk to engineer against.
Encrypted, outbound-only agent
Agents connect out over HTTPS. No inbound ports are opened on client networks.
Pinned server certificate
Agents trust only your server's own certificate, so traffic cannot be redirected to an impostor.
Two-step verification
A code from Google Authenticator or Telegram at every sign-in. Changing one method needs the other.
Sign-in alerts
Each sign-in reaches your Telegram with the address and device, and a button to end that session.
Encrypted secrets
Bot tokens, authenticator keys and enrollment keys are encrypted on the server and never shown again.
Role-based access control
Grant technicians access per client, with separate rights for viewing, scripting and administration.
IP access rules
Allow only your offices, block suspicious addresses, and end their sessions at once.
Complete audit log
Every sign-in, configuration change and script run is recorded with user, time and target.
Your clients, secured and in view
Sign in to your Ops RMM console to monitor devices, run automation and keep every client safe.