Backups are the unglamorous part of an MSP that becomes the only thing that matters once a week. Most shops run a mix of vendors — a Datto appliance at one site, NinjaOne native backup at another, Datto SaaS for Microsoft 365, maybe Veeam for the enterprise customer who already had it. Each tool has its own dashboard. Each dashboard is its own login. Each login is the one you forgot to check on the Tuesday a chain dropped.
Morton Command Center pulls every vendor's backup job state into one model and surfaces it on one page — Failed, Stale, Healthy. Per company. Per vendor. With a dashboard ring widget for the quick "are we okay?" glance. The platform was built vendor-agnostic from day one: whatever your backup stack looks like today (or two years from now), the adapter pattern handles it. If your tool has an API, we connect to it during your build. This is a monitoring and visibility layer — Command Center reads job status from your backup tools; it does not run, restore, or configure backups, and your tools stay the source of truth. No migrating backup data, no replacing anything your team already knows. Cancel and your backup vendor's portal looks exactly like it did before.
What gets surfaced
- Compact dashboard view — health ring (% of jobs healthy), per-vendor breakdown (jobs healthy / stale / failed for Datto, Ninja, Veeam, etc.), failing-companies alert table, M365 / Cloud row, on-prem Healthy summary.
- Per-company drill-in — every company's Backup tab shows their jobs grouped by vendor, last-success time, last-failure time, age-of-last-success in days, deviceType (server vs workstation), and recent run entries.
- Health classification per job — Failed (latest run was a failure), Stale (last success older than tenant threshold), Healthy (success within window).
- Per-tenant staleness thresholds — default 3 days for servers, 7 days for workstations + other. Configurable per tenant in Settings → General → Backup.
- M365 / cloud sync rollup — your SaaS-backup tool (Datto SaaS, Veeam, or any cloud-backup product with an API gets the integration built for your stack) gives % of seats backed up; the dashboard ring shows the cloud number alongside the on-prem ring when both are wired.
- Dashboard widgets — "Backup Health Ring" + "Backups Needing Attention" widgets in the customizable dashboard. Drop them on the page next to ticket KPIs to make backup state a one-glance check, not a tab you have to remember to open.
Integrations we build for your stack
Every backup integration is custom-built for your engagement — wired to fit your exact tools and thresholds rather than forcing you onto a fixed menu. If your tool has an API, we build the integration custom to your stack. The vendors below are examples of what that looks like; your stack shapes the actual integration list. The health ring, per-company drill-in, and email-ingest pipeline are native Command Center features — included and live from day one — and your vendor API connections are built on top of them as part of your build.
- Datto BCDR — on-prem appliances. Pulls per-agent backup, recovery point, screenshot verification status. Per-device staleness against tenant rules.
- Datto SaaS Protection — Microsoft 365 cloud backup. Pulls per-seat / per-service backup percentage; surfaces tenants below the healthy and stale percentage thresholds (default 99% healthy, 90% stale).
- NinjaOne — native NinjaOne backup jobs (image + file). Pulls per-device job state + last-success / last-failure timestamps.
- Veeam — via email-ingest (nightly job emails parsed into the same Failed / Stale / Healthy model) or a direct API integration built for your stack if it warrants it.
- Acronis · Barracuda · Synology — via email-ingest, or API integrations built to fit your stack as part of your engagement.
- Email-ingest fallback — for backup tools that don't expose an API, we ingest their nightly success/failure emails and normalize them into the same Failed / Stale / Healthy model.
- Your vendor not listed? If it has an API, we build the integration custom to your stack — same model, same dashboard, same one-page rollup. This is a one-of-one build: your stack shapes the integration list, not the other way around. That's the advantage over rigid all-in-one suites — you connect the tools you already run instead of being forced onto theirs.
Status logic
One job at a time:
- If last failure is after last success → Failed.
- If last success is older than the tenant's deviceType threshold → Stale.
- Otherwise → Healthy.
One company at a time:
- If any job is Failed → company is Failed.
- Else if any job is Stale → company is Stale.
- Else → Healthy.
Why this matters
Backups fail quietly. The customer doesn't notice. The vendor's dashboard does — but you have to look at it. The shop that catches a stale agent on Tuesday is the shop that doesn't have a four-day-old restore on Friday. Putting the health ring on the dashboard means anyone glancing at the page sees the number every morning. The shop that gets paged because an internal monitoring rule fired on the rollup is the shop that already booked the call.
Pricing
Flat monthly pricing — no per-seat fees, no per-vendor surcharge. See current pricing on the homepage →
Ready to talk?
The first call is a 30-minute discovery — we map which backup vendors you run (whatever they are — if they have an API, they fit), what your staleness threshold should be per device class, and whether a cloud-backup rollup (Datto SaaS or any equivalent M365 backup tool) matters to you. No commitment, no sales pressure.
Questions first? Email [email protected] or read the FAQ.