Nine rates, on the grounds that recovery is never a single activity.
A workstation, a hypervisor, a Microsoft tenant, and a QuickBooks company file fail in different ways and are recovered by different mechanisms. This program keeps them separate and prices them separately. N-able Cove covers machines and Microsoft 365, Dropsuite covers Google Workspace, QuickBooks Online, and Entra ID, and restore verification stands on its own line.
Program
06 of 06
Platform
N-able Cove and Dropsuite
Line items
9 priced separately
Unit basis
Machines, tenants, and company files counted apart
Billing
Card, monthly in advance, no term
How it works
The mechanism, not the brochure.
Three things worth understanding about this program before you price it, written for somebody who will be asked to defend the decision internally.
01
The copy lives outside what it protects
Protected data is held away from the systems it came from and outside the credentials that administer them. Ransomware that reaches a file server should not reach the only copy of what was on it, and an administrator account that has been taken over should not be able to delete the record of what existed before.
02
Tenant retention is not tenant backup
Microsoft 365, Google Workspace, and Entra ID all keep data for a policy window and then stop. That window is a setting, held inside the tenant, and adjustable by anybody holding the rights an attacker would target first. An independent copy is a different category of thing.
03
Verification, not assumption
Restore verification performs recoveries on a schedule and records the result. Whether your backup works stops being a matter of belief and becomes paper an assessor can read. It also surfaces the broken job during an uneventful week instead of a catastrophic one.
Line items
The 9 line items in this program.
Each control is priced against its own unit and can be bought without the others. Rates come live from the billing catalog. Anything added here is held in the schedule and checked out from the rate schedule.
Fortify-CDP-FF
Working File History
Continuous file history on a Windows workstation through N-able Cove. Working documents are captured as they change rather than once a night, which is the difference between losing a morning and losing a day when a file is overwritten, corrupted, or encrypted.
Loadingper Windows workstation published rate, per monthUnits
Fortify-CDP-WKSTN
Workstation Image Backup
Full image protection for a workstation. The whole machine is captured, so a recovery returns an operating system, its applications, and the data together instead of handing back files to a machine somebody still has to rebuild from scratch first.
Loadingper workstation published rate, per monthUnits
Fortify-CDP-SRVR
Physical Server Backup
Image protection for a physical server, including system state and the applications that make it the machine it is. Recovery can target the same hardware or different hardware, which is the distinction that matters most on the day the original is not available to restore onto.
Loadingper physical server published rate, per monthUnits
Fortify-CDP-VM
Virtual Server Image Backup
Image protection for a virtual server, taken with the hypervisor in mind so that a restore produces a bootable machine rather than a folder of disk files somebody has to reassemble correctly while everyone waits.
Loadingper virtual server published rate, per monthUnits
Fortify-CDP-M365
Microsoft 365 Protection
Microsoft 365 tenant protection through Cove, covering mail, OneDrive, SharePoint, and Teams content in a copy held independently of the tenant. Retention inside Microsoft 365 is a policy setting, not a backup, and it will not survive an administrator account that has been taken over by somebody holding the same rights.
Loadingper licensed user published rate, per monthUnits
Fortify-CDP-GWS
Google Workspace Protection
Dropsuite covering a licensed Google Workspace user across Gmail, Drive, Calendar, and Contacts. The principle is the one that governs the Microsoft line: the copy lives outside the tenant it exists to protect.
Loadingper licensed user published rate, per monthUnits
Fortify-CDP-QBO
QuickBooks Online Protection
Dropsuite protecting QuickBooks Online, with the count taken against the company file and not against seats. Accounting data changes continuously and is edited by people working to a deadline, which is the combination that produces the restore requests nobody had planned for.
Loadingper company file published rate, per monthUnits
Fortify-CDP-Entra
Entra ID Configuration Backup
Dropsuite keeping a copy of your Entra ID configuration: user objects, group objects, role assignments, and each policy object that settles who may do what. Directory damage is quiet and slow to notice, and rebuilding it by hand is reliably the longest part of any recovery it appears in.
Loadingper tenant published rate, per monthUnits
Fortify-CDP-Continuity
Restore Verification
Restore verification for a system already covered by a backup line. Recoveries are performed on a schedule and the outcome is recorded, so whether the backup works is answered by a test record you can hand to an assessor rather than by an assumption held until the day it fails.
Loadingper protected system published rate, per monthUnits
Where this program stops
What these line items do not do.
Backup is the category where optimistic assumptions do the most damage. These are the limits, in writing.
Backup is not archive.Retention runs for a defined window and then ages out. Indefinite preservation, legal hold, and journaling are different products with different obligations.
SaaS coverage stops at the vendor API.What can be protected in a tenant is bounded by what its provider exposes. No backup product gets further than the API does, ours included, and this seemed the honest place to say it.
There is always a gap at the end.Data created between the last completed pass and the incident is not recoverable. Shorter intervals narrow that window; nothing closes it.
Verification proves the restore, not the application.A verified recovery confirms the data came back and the system booted. It does not certify that a line-of-business application is functionally correct afterwards.
Recovery time depends on your side too.Restore duration is governed by data volume, available bandwidth, and target hardware. We will size it honestly with you, and no promise made here is independent of those facts.
It is not a standby site.Hardware replacement, warm standby infrastructure, and a contracted recovery time commitment are not part of these lines unless separately arranged in writing.
Every line in this program is bought against a bad day that has not happened yet. Restore verification is the one that tells you whether the rest of them will work when it does.
The other programs
What sits alongside this one.
Any program can be bought on its own. Most estates end up running several, and the reason they work well together is that one desk operates all of them.