Smart groups are the unit of automation
Define a group by any fact (OS, version, tag, customer, location). Automations target groups; new matches auto-enroll.
Smart groups target every device that matches a fact. Scripts run on one device or 10,000 with per-device status. Scheduled jobs, event triggers, and approval workflows — built in.
Define a group by any fact (OS, version, tag, customer, location). Automations target groups; new matches auto-enroll.
Push a script across thousands of devices in one click. Per-device exit codes, stdout, and timing streamed back as it runs.
Alerts, ticket transitions, schedule windows, and webhooks all trigger automations with audit-logged actions.
Dynamic device groups by any fact. New matches auto-enroll; removed matches auto-leave.
Push a script across thousands of devices. Per-device exit codes and output streamed back.
Cron-like scheduling per group or per device. Maintenance window aware.
Alerts, ticket events, webhooks, and schedule windows trigger automations.
Require approval before destructive actions. Gates by customer, action, or asset class.
Every automation run, every action, every approver — captured.
One Go-native agent for Windows, macOS, and Linux. Zero dependencies, signed, runs as SYSTEM.
See RMMMSI-first delivery with Chocolatey bootstrap. winget supported but not preferred — for reasons.
See Patch ManagementModern ticketing with custom workflows, saved views, and a white-label client portal.
See HelpdeskPowerShell on Windows, bash/zsh on macOS and Linux, plus Python where the agent finds it.
Yes — a single automation can have OS-specific payloads. The agent picks the right one for each device.
Where the agent has a rollback hook (catalog installs, policy applications), yes. Free-form scripts are reversible only if you script the rollback.
Deploy your first agent in minutes. See the platform in action — book a walkthrough or kick the tires on a free trial.