Does the agent need admin rights?

Yes. Like every RMM agent. It runs as SYSTEM on Windows, root on Linux, root on macOS. Without that, you cannot patch, cannot run scripts, cannot read everything telemetry needs.

What about Apple Silicon?

Intel macOS is shipping today. Apple Silicon build is in CI; signed/notarised distribution path is the gating step.

How does self-update work?

Server publishes a target version. Agent downloads, verifies, atomic-swaps, restarts via SCM (Windows) / systemd (Linux), runs a self-test, reports success. Failure rolls back and publishes a telemetry event.

Can I uninstall cleanly?

Yes. The installer ships an uninstaller. For Windows, the MSI handles add/remove cleanly. For Linux, the package manager removes the service unit and binary.

Does the agent work behind a proxy?

Outbound TLS supports HTTP CONNECT proxy. We document the env vars needed in the install guide.

Does it work on locked-down workstations?

Yes. We have deployed on AppLocker-restricted Windows endpoints with code-signing verification enabled.

The agent

One binary. Three OSes. Stays up across reboots.

A native RMM agent for Windows, macOS and Linux. Real-time bidirectional comms. Self-updating. Low memory footprint. Designed to keep running while Patch Tuesday breaks the world around it.

Apply for closed beta

Cross-platform
Windows, macOS and Linux from one native codebase. No runtime dependency on Python / .NET / Node.
Real-time
Always-connected bidirectional comms. Server can ask, agent can push. Events publish to the SPA the moment they happen.
Stays up
Watchdog service on Windows, systemd on Linux, launchd on macOS. Self-update with self-test before declaring success.

Agents reporting from Windows, macOS and Linux endpoints across twelve clients.

What it ships with

Telemetry, control, and not much else.

System telemetry — CPU, RAM, disk, uptime, services, processes, software inventory
Real-time event streaming — events publish to the SPA the moment they happen
Bidirectional comms — server can ask the agent for live data; agent can push events at will
Script execution — PowerShell on Windows, Bash on Linux, Python where installed
Patch execution — Windows Update API on Windows, package manager on Linux
Remote access — secure remote desktop via OpsMerge Connect, launched on demand from the console
Self-update — staged binary swap with SCM-aware service restart on Windows, ProtectSystem-aware swap on Linux

How it stays up

Boring reliability choices.

Single static native binary. No runtime dependency on Python / .NET / Node.
Watchdog service on Windows; systemd on Linux; launchd on macOS. If the agent dies, the OS restarts it.
Self-update process is split: download + verify + atomic swap + restart + self-test + rollback on failure.
Update failure publishes a telemetry event. No silent failures. No I-told-you-it-succeeded bugs.

Resource footprint

Low. Measured.

Single-digit MB resident memory under steady-state telemetry.
Single-digit percent CPU under heavy work (script execution, patch run).
Optimised for user laptops, not data-centre racks. If your sales reps notice the agent on their MacBook, we have failed.

Pairs well with

Other things in the platform

Asset management

Your live agent fleet doubles as the billable asset register. No second database.

Learn more

Patch management

Windows Update, Linux package manager, third-party software. Policy-driven. Audited.

Learn more

OpsMerge vs NinjaOne

Where each one wins, where each one doesn't.

Common questions

Does the agent need admin rights?
Yes. Like every RMM agent. It runs as SYSTEM on Windows, root on Linux, root on macOS. Without that, you cannot patch, cannot run scripts, cannot read everything telemetry needs.
What about Apple Silicon?
Intel macOS is shipping today. Apple Silicon build is in CI; signed/notarised distribution path is the gating step.
How does self-update work?
Server publishes a target version. Agent downloads, verifies, atomic-swaps, restarts via SCM (Windows) / systemd (Linux), runs a self-test, reports success. Failure rolls back and publishes a telemetry event.
Can I uninstall cleanly?
Yes. The installer ships an uninstaller. For Windows, the MSI handles add/remove cleanly. For Linux, the package manager removes the service unit and binary.
Does the agent work behind a proxy?
Outbound TLS supports HTTP CONNECT proxy. We document the env vars needed in the install guide.
Does it work on locked-down workstations?
Yes. We have deployed on AppLocker-restricted Windows endpoints with code-signing verification enabled.

See the agent in your fleet

Beta applicants get install access for up to 300 assets during the cohort window — enough to test it in a real environment.

Apply for closed beta