The agent sits beside what you run today.
Coexistence is how the one agent of The One Stack, the platform MSPs run their whole business on, runs on a device beside the RMM, EDR and antivirus an MSP already has. The agent does not stop, hook or fight another vendor’s agent. It reports what it found, leaves patching and antivirus alone until you take them over, and lets you move one client at a time.
What coexistence means
The agent is built to leave the tools that are already there alone.
It leaves other agents alone
The agent does not stop, remove or tamper with another vendor’s agent. Removing an old agent is a separate, deliberate step you choose.
It tells you what it found
The device page names the monitoring, antivirus and detection tools already on the device.
Patching waits for you
When another tool manages operating system updates, the device shows as managed elsewhere. The platform leaves it alone until you take over patching, and taking over is recorded.
Antivirus stays as it is
Where another antivirus is the active product, the platform does not switch the built-in one on. Its own antivirus settings apply only where it manages antivirus.
Capabilities switch on one at a time
One install carries monitoring, patching, remote control, security, DNS filtering and backup. Each is switched on per client when you are ready, without another rollout.
Exclusions and disclosure
Two tools on one device notice each other. This is how you keep the overlap tidy and in the open.
Expect both tools to alert
During the overlap, two tools can alert on the same thing. Mute the old tool’s alerts for that device in the tool you run today, not in One.
Exclusions with a reason and an end date
In detection and response (Defend), an exclusion names a file path, a folder or a process, applies to one client or to all of them, and carries a note saying why. It ends on a date, and its removal is recorded.
What the person at the device sees
On an attended device, a remote session waits for the person to approve it. While it runs, an icon names who is connected and lets them end the session.
Documents for your rollout
Published exclusion list
The agent’s install paths, services and processes to add to your current security tools, as a published list. Engineering supplies the list and where it is published.
Client notice
A notice an MSP sends its clients before the agent is installed beside their current tools: what it is, what it collects and who to ask. The owner supplies the approved text.
A rollout plan
Pilot, client by client, then the rest. The old tools keep running until you turn them off.
- 01
Pilot
Install the agent on a small group of devices, at one client or in your own shop. Keep the old tools running.
- 02
Read what it found
Open each device and read which other tools the agent found. Review the devices marked managed elsewhere before you take anything over.
- 03
Switch on one capability at a time
Start with monitoring. Add patching, remote control, security and backup once each has run on the pilot devices.
- 04
Move client by client
Roll the agent out to the next client, then the next. Each client moves on its own date.
- 05
Then the rest, and retire
When the agent has reported healthy on a client’s devices, take over patching and remove the old agent as a separate step.
Questions
Questions MSPs ask
Can I run the agent beside my current RMM?
Yes. The agent installs beside your current RMM and does not stop, remove or tamper with it. You move one client at a time and remove the old agent when you choose.
Can I run it beside my current EDR or antivirus?
Yes, during the move. Where another antivirus is the active product, the platform leaves it in place and does not switch the built-in one on. Detection and response is switched on per client when you are ready. It includes its own EDR sensor, which takes over from the old EDR, and you remove the old product when you choose.
Do two patching tools fight over updates?
No. When another tool manages updates, the device shows as managed elsewhere, and the platform leaves it alone until you take over patching.
Does the agent uninstall my old tools?
No. Removing an old agent is a separate, deliberate step you choose. The platform does not target another vendor’s agent.
Do I need a second install to add security or backup later?
No. One install carries every capability, and each one is switched on per client.
Related
Keep going
Start
Run on One.
Start a trial and bring one client across, or book a walkthrough and follow a call down the line with us.