What you are signing up for.
Beside, not instead — at first
≤ 100 devices next to the incumbent. The old tool stays until you say otherwise.
21 to 30 days
Long enough for a disk to trend, a site to flap, and a slow morning to happen. Short enough that it is a project, not a habit.
A forced ending
Cutover commit or stop. No quiet extension that turns us into a sidecar investigator.
the weeksFive steps, then one of two outcomes.
01Qualify and pick the set
A short call. If you fit, we agree the shadow: up to 100 devices that represent the estate — Windows endpoints, servers, and the site kit (firewall, router, NAS) at more than one site.
02Install beside the incumbent
One outbound agent per machine. No inbound port, no VPN, no rip-and-replace. The old RMM keeps doing what it does.
0321 to 30 days, read-only
Same alerts, same investigations, named approvals if you choose to act in BE Hub. We do not ask you to switch on-call on day one.
04Deliverables, then a decision
Weekly findings, a side-by-side on the cases that matter, a written cutover plan. You commit to cutover or we stop.
05Cut over, or walk away
Acceptance criteria, a rollback window, overlap credit after a cutover commit. The Exit ends with their RMM out or BE Hub out.
Their RMM out
On-call points at BE Hub. Agents on the rest of the estate. Incumbent licences drain on a date you set. Overlap credit applies after the commit.
BE Hub out
Uninstall. You keep the written findings. We do not linger as an add-on.
Overlap credit
Quoted per Exit after you commit to cutover — not a published rate, not available on the self-serve trial. Hosted after cutover pays the per-technician table.
what we hand youDeliverables, not a vibe.
Weekly shadow notes
What BE Hub saw, what the incumbent also saw, and what only one of them explained.
Ops-loop evidence
Finding → evidence → exact command → named approve or reject → verify. On your machines, with your names.
Cutover plan
How the remaining estate enrols, how notifications move, which scripts and checks to recreate, who is on-call on the day.
Acceptance and rollback
What 'good' means on paper before cutover day, and how to put the incumbent back in front if the first week is wrong.
migration, when you commitThe rest of the estate is a project with a date.
Agents beside agents
Same install link you already used on the shadow set. Outbound only. Forget a machine in the old tool when you are ready, not before.
Sites as companies or tags
Map the way you already think about the estate. Isolation is enforced on the hub if you want site A unable to see site B.
On-call cut
Notification rules first, then you stop paging out of the old tool. Rollback is the reverse of that step.
qualifyAn Exit is a fit, or it is not.
a fit- ✓internal IT, or a sovereignty-led provider
- ✓Windows-heavy hybrid estate, more than one site
- ✓roughly 250 to 2,000 assets (shadow on ≤ 100)
- ✓someone named who can approve or reject during the shadow
- ✓willing to pick a winner in 30 days
- ✗you want the AI to remediate unattended
- ✗you want an investigator beside an RMM you intend to keep
- ✗there is no named approver
- ✗you need a named-competitor bake-off we have not published
On the contact form, choose RMM Exit / replacement. A person replies, usually within a working day.
questions