Sendense pricing
Licensing built around how you use Sendense.
Public Sendense pricing is scoped by licensing route. The edition matrix below is the capability authority. Quotes follow the route, the operator and the named estate or opportunity.
Infrastructure customer
Infrastructure Licensing
Licence Sendense to protect your own estate. Editions are sold on a per-protected-VM principle where that model applies, with a defined term and pack size. Capability differences come from the edition matrix below. Essentials remains available as an evaluation route, and broader estates are scoped before a quote is issued.
Get a scoped quoteCloud Service Provider customer
CSP Licensing
A Cloud Service Provider is a licensed Sendense customer. The provider operates Sendense to build BaaS, DRaaS, migration or hosted protection services. Deployment, tenancy and the service model have to be understood before a quote. Capacity or commitment principles are discussed in that scoping conversation. Wholesale prices are not published here.
Discuss CSP licensingSecondary journey: /use-cases/service-providers
MSP reseller / solution partner
MSP Reseller Licensing
Resell Sendense for a named customer, or deliver a customer migration or infrastructure project. The licence holder and operator must be stated for that opportunity. Pricing is route-specific and quoted against the named opportunity rather than a public catalogue.
Price a customer opportunityMigration project
Migration Licensing
A one-time migration licence covers a permanent move of one named workload. It is consumed when that move is committed and is not a substitute for ongoing protection editions.
Price a migration projectEssentials Evaluation
Use the first-five Essentials entitlement to evaluate Sendense in a real environment.
Use the existing first-five Essentials entitlement to evaluate Sendense in a real environment. This is not the default journey for CSP licensing, migration licensing, enterprise architecture or partner opportunity qualification.
- 01Deploy
- 02Discover the environment
- 03Protect the first VM
- 04Complete a backup
- 05Validate a recovery point
- 06Decide whether broader evaluation is justified
Edition capabilities
What each edition can do.
Pack sizes, protected-VM ceilings and capability facts come from the licensing manifest. They are not a public price list.
Essentials
Sold in 5-VM packs
Maximum protected VMs: 30
- Scheduled and on-demand VM backup into an EBA repository
- Full VM, disk and file-level restore back to the source platform
- Replication to a replica held on the same hypervisor family
- Test and live failover from that same-platform replica
- Same-platform restore of protected data stays available after the term ends
- Recovery onto a different hypervisor is not included; that starts at Enterprise
- Replication to a different hypervisor is not included
Standard
Sold in 10-VM packs
Maximum protected VMs: no ceiling
- Everything in Essentials, plus:
- Estate size is not capped by the edition
- Recovery onto a different hypervisor is not included; that starts at Enterprise
- Replication to a different hypervisor is not included
Enterprise
Sold in 10-VM packs
Maximum protected VMs: no ceiling
- Everything in Standard, plus:
- Restore a backup onto a different hypervisor, for example VMware into CloudStack
- Permanently promote a workload onto a different hypervisor through a committed restore
- That cross-platform recovery path survives into restore-only, after the term and grace period end
- Replication to a different hypervisor is not included; an ongoing cross-platform replica needs Enterprise Plus
- Cross-platform failover is not included; recovery across platforms here is a restore, not a live replica
- Reverse replication and failback are not included
Enterprise Plus
Mobility and DR licensing through sales.
Enterprise Plus is the only edition that keeps a live replica on a different hypervisor and can fail over to it, and back again. It is sold in 10-VM packs and scoped with the sales team.
Maximum protected VMs: no ceiling
Get a scoped quote- Everything in Enterprise, plus:
- Ongoing replication to a different hypervisor, for example a VMware workload replicated into CloudStack
- Rehearse a cross-platform replica with test failover, without committing it
- Run production workloads from a cross-platform replica
- Reverse replication and failback to the original platform
Edition Comparison
What Each Edition Is Entitled To.
This table is generated from the same capability matrix the appliance enforces, so what you read here is what the licence permits. Same-platform means recovery back to the hypervisor family a workload was protected from; different-platform means recovery onto another one.
| Capability | EssentialsSubscription5-VM packs | StandardSubscription10-VM packs | EnterpriseSubscription10-VM packs | Enterprise PlusSubscriptionQuoted | MigrationOne-time licenceUnits of 10 |
|---|---|---|---|---|---|
| VM backupScheduled and on-demand backups to an EBA repository. Backup has no destination platform, so it is not scoped by hypervisor. | Included | Included | Included | Included | Not included |
| Restore to the same hypervisorFull VM, disk and file-level restore back to the platform the workload was protected from. | Included | Included | Included | Included | migration workflow only |
| Restore to a different hypervisorRecovering a backup onto a different hypervisor family, for example VMware to CloudStack. | Not included | Not included | Included | Included | migration workflow only |
| Replication to the same hypervisorOngoing replica maintained on the same hypervisor family as the source. | Included | Included | Included | Included | migration workflow only |
| Replication to a different hypervisorOngoing cross-platform replica, for example a VMware workload replicated into CloudStack. | Not included | Not included | Not included | Included | migration workflow only |
| Test and live failover on the same hypervisorRehearsing and running failover from a replica held on the same hypervisor family as the source. | Included | Included | Included | Included | migration workflow only |
| Cross-platform test failoverBooting a cross-platform replica for a rehearsal without committing it. | Not included | Not included | Not included | Included | migration workflow only |
| Cross-platform failoverStarting production workloads from a cross-platform replica. | Not included | Not included | Not included | Included | migration workflow only |
| Reverse replication and failbackReplicating back from the failed-over workload and returning it to its original platform. | Not included | Not included | Not included | Included | Not included |
| Cross-platform migrationPermanently promoting a workload onto a different hypervisor, through a committed restore or a committed failover. | Not included | Not included | Included | Included | migration workflow only |
| Same-hypervisor restore after expiryRecovery of data already protected, once the subscription term and its grace period have both ended. | Included | Included | Included | Included | Not included |
| Cross-hypervisor restore after expiryCross-platform recovery of data already protected, once the term and grace period have both ended. | Not included | Not included | Included | Included | Not included |
| Maximum protected VMsThe largest protected estate the edition may be licensed for. | 30 | no ceiling | no ceiling | no ceiling | one named VM per unit |
The one-time column is a project licence rather than a tier: a unit binds to one named workload and is permanently consumed when the move is committed, so continued protection afterwards needs a subscription licence.
Licensing and editions documentationMigration Licensing
One-time named-workload licensing for a permanent move. A unit binds to one named workload and is permanently consumed when the move is committed. It is not ongoing protection.
Maximum protected VMs: one named VM per unit
- One committed move of one named VM onto a different hypervisor
- Replication, test failover and cutover, inside the migration workflow only
- No ongoing backup; a migrated workload needs a subscription licence for continued protection
- No reverse replication or failback once the move is committed
Provider and partner licensing is scoped, not catalogued.
CSP customer licensing and MSP reseller opportunities use different licence-holder and operator models. Neither is a public wholesale or discount list.
When a term ends
Your data stays recoverable.
- Active
- The subscription term is current. Every entitlement the edition includes is available.
- Grace period
- The term has ended but the grace period has not. Protection continues unchanged, and the exact date protection will stop is shown in the appliance.
- Restore only
- The term and the grace period have both ended. Data already protected stays recoverable; nothing new is protected.
Evaluation stays optional
Essentials evaluation is available. It does not replace scoped quotes for CSP, migration or enterprise work.
Capabilities, not a price book
The comparison table is the edition capability matrix. Sendense pricing for a route is quoted after scope is understood.
Licence holder and operator
Infrastructure, CSP, reseller and managed-service models keep those roles explicit. They are not one commercial audience. Retained managed-service operation is distinct from simple resale. Licence-holder classification for that operating model is still pending and is scoped with sales. No public price or extra commercial term is published here.