Endpoints, servers, and SaaS
Backup
Backup and recovery products from public pages. No thread in this set is a backup-replacement ask.
Public pages, not a ranking
| Vendor | Group | What the public page supports | Price signal |
|---|---|---|---|
| Axcient | Public product page | Homepage describes business continuity and disaster recovery, including x360Recover for servers and endpoints and x360Cloud for Microsoft 365 and Google Workspace. It states an RTO under 1 hour and an RPO of 15 minutes as product claims. Checked 2026-10-15. No dollar amount on that page. | Omitted. No dollar amount on the page we checked. |
| NinjaOne | Public product page | Homepage says the same platform includes endpoint, server, and SaaS backup for Microsoft 365 and Google Workspace. NinjaOne is also on the RMM board. Homepage checked 2026-10-15. No dollar amount on that page. | Omitted. No dollar amount on the page we checked. |
| Veeam | Public product page | Homepage describes a data resilience platform for backup and recovery across cloud, SaaS, and on-premises workloads, including Microsoft 365. Checked 2026-10-15. No MSP price on that page. | Omitted. No dollar amount on the page we checked. |
Switch triggers
The general triggers this desk watches are a price change, a sour account-management relationship, and distributor or marketplace fees. Those are themes from public MSP discussions. A theme is attached to a named product only when a linked thread title supports it.
No thread in the 15 October 2026 research set asks what should replace a named backup product. Rows are public product pages, alphabetical, with no rank.
Migration checklist stub
A starting list, not a vendor runbook. Confirm each step against your contract and the vendor’s own documentation.
- Export the client list, site list, and the count of agents or collectors you actually bill.
- Read the current agreement for notice, auto-renewal, and what you can export when you leave.
- Write down the alerts, scripts, and integrations that have to exist on day one.
- Pilot on one non-critical client before a fleet cutover.
- Leave the old agent or collector in place until the new one is reporting.
- Note whether you buy direct or through a distributor, and who owns that login.
- Write down retention, immutability, and which workloads are servers, endpoints, or Microsoft 365.
- Confirm you can restore once in the pilot before you cancel the current job.