Sendense Documentation

Licensing And Editions

What each Sendense edition includes, how same-hypervisor and cross-hypervisor recovery differ, and what a licence still permits once its term ends.

Documents Home

Concept

Licensing And Editions

What each Sendense edition includes, how same-hypervisor and cross-hypervisor recovery differ, and what a licence still permits once its term ends.

ReadyCurrentlicensingeditionsentitlementmigrationlifecycle

What A Licence Controls

A Sendense licence sets two things: how many VMs may be protected, and which recovery paths are permitted. The rest of the product does not change between editions — the same repository format, transport, scheduling, retention and recovery evidence are present in all of them.

Editions are sold either as a subscription or as a one-time project licence. Each edition's commercial model, pack size and protected-VM ceiling is listed below.

The entitlements on this page are generated from the same capability matrix the appliance enforces, so what is documented here is what the licence gates actually apply.

Same Hypervisor And Different Hypervisor

Most of the licensing model turns on a single axis: whether an operation lands back on the hypervisor family a workload was protected from, or on a different one. Restore, replication and failover each appear twice in the matrix for that reason.

Backup does not sit on that axis at all. A backup has no destination platform, so no edition scopes it by hypervisor; the axis only starts to matter at the point of recovery.

Same hypervisor
Restore, replication or failover back onto the hypervisor family the workload was protected from — VMware to VMware, or CloudStack to CloudStack.
Different hypervisor
The same operations landing on another hypervisor family, for example a VMware workload recovered or replicated into CloudStack.

Backup is not scoped by hypervisor

Scheduled and on-demand backups to an EBA repository. Backup has no destination platform, so it is not scoped by hypervisor.

What Each Edition Includes

Each edition below lists its commercial model, its protected-VM ceiling, and the operations it permits. Where an edition permits an operation only inside a specific workflow, that scope is shown in brackets rather than as a plain inclusion.

Essentials
A subscription, sold in 5-VM packs. Maximum protected VMs: 30. Includes VM backup, restore to the same hypervisor, replication to the same hypervisor, test and live failover on the same hypervisor and same-hypervisor restore after expiry. Does not include restore to a different hypervisor, replication to a different hypervisor, cross-platform test failover, cross-platform failover, reverse replication and failback, cross-platform migration and cross-hypervisor restore after expiry.
Standard
A subscription, sold in 10-VM packs. Maximum protected VMs: no ceiling. Includes VM backup, restore to the same hypervisor, replication to the same hypervisor, test and live failover on the same hypervisor and same-hypervisor restore after expiry. Does not include restore to a different hypervisor, replication to a different hypervisor, cross-platform test failover, cross-platform failover, reverse replication and failback, cross-platform migration and cross-hypervisor restore after expiry.
Enterprise
A subscription, sold in 10-VM packs. Maximum protected VMs: no ceiling. Includes VM backup, restore to the same hypervisor, restore to a different hypervisor, replication to the same hypervisor, test and live failover on the same hypervisor, cross-platform migration, same-hypervisor restore after expiry and cross-hypervisor restore after expiry. Does not include replication to a different hypervisor, cross-platform test failover, cross-platform failover and reverse replication and failback.
Enterprise Plus
A subscription, sold in 10-VM packs, priced on a quote rather than a published price. Maximum protected VMs: no ceiling. Includes VM backup, restore to the same hypervisor, restore to a different hypervisor, replication to the same hypervisor, replication to a different hypervisor, test and live failover on the same hypervisor, cross-platform test failover, cross-platform failover, reverse replication and failback, cross-platform migration, same-hypervisor restore after expiry and cross-hypervisor restore after expiry.
Migration
A one-time licence, sold in units of 10. Maximum protected VMs: one named VM per unit. Scoped: restore to the same hypervisor (migration workflow only), restore to a different hypervisor (migration workflow only), replication to the same hypervisor (migration workflow only), replication to a different hypervisor (migration workflow only), test and live failover on the same hypervisor (migration workflow only), cross-platform test failover (migration workflow only), cross-platform failover (migration workflow only) and cross-platform migration (migration workflow only). Does not include VM backup, reverse replication and failback, same-hypervisor restore after expiry and cross-hypervisor restore after expiry.

Capability By Capability

The same entitlements read the other way round: what each capability means, and which editions hold it.

VM backup
Scheduled and on-demand backups to an EBA repository. Backup has no destination platform, so it is not scoped by hypervisor. Included in Essentials, Standard, Enterprise and Enterprise Plus. Not included in Migration.
Restore to the same hypervisor
Full VM, disk and file-level restore back to the platform the workload was protected from. Included in Essentials, Standard, Enterprise and Enterprise Plus. Migration: migration workflow only.
Restore to a different hypervisor
Recovering a backup onto a different hypervisor family, for example VMware to CloudStack. Included in Enterprise and Enterprise Plus. Migration: migration workflow only. Not included in Essentials and Standard.
Replication to the same hypervisor
Ongoing replica maintained on the same hypervisor family as the source. Included in Essentials, Standard, Enterprise and Enterprise Plus. Migration: migration workflow only.
Replication to a different hypervisor
Ongoing cross-platform replica, for example a VMware workload replicated into CloudStack. Included in Enterprise Plus. Migration: migration workflow only. Not included in Essentials, Standard and Enterprise.
Test and live failover on the same hypervisor
Rehearsing and running failover from a replica held on the same hypervisor family as the source. Included in Essentials, Standard, Enterprise and Enterprise Plus. Migration: migration workflow only.
Cross-platform test failover
Booting a cross-platform replica for a rehearsal without committing it. Included in Enterprise Plus. Migration: migration workflow only. Not included in Essentials, Standard and Enterprise.
Cross-platform failover
Starting production workloads from a cross-platform replica. Included in Enterprise Plus. Migration: migration workflow only. Not included in Essentials, Standard and Enterprise.
Reverse replication and failback
Replicating back from the failed-over workload and returning it to its original platform. Included in Enterprise Plus. Not included in Essentials, Standard, Enterprise and Migration.
Cross-platform migration
Permanently promoting a workload onto a different hypervisor, through a committed restore or a committed failover. Included in Enterprise and Enterprise Plus. Migration: migration workflow only. Not included in Essentials and Standard.
Same-hypervisor restore after expiry
Recovery of data already protected, once the subscription term and its grace period have both ended. Included in Essentials, Standard, Enterprise and Enterprise Plus. Not included in Migration.
Cross-hypervisor restore after expiry
Cross-platform recovery of data already protected, once the term and grace period have both ended. Included in Enterprise and Enterprise Plus. Not included in Essentials, Standard and Migration.
Maximum protected VMs
The largest protected estate the edition may be licensed for. Essentials: 30, Standard: no ceiling, Enterprise: no ceiling, Enterprise Plus: no ceiling and Migration: one named VM per unit.

When A Term Ends

A subscription term does not end in a cliff. A licence moves through three states, and the appliance shows which one it is in.

Restore only is a floor rather than a lock. Data that was already protected stays recoverable for as long as the repository holds it, but nothing new is protected and no replica moves forward.

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.
  • Still available in restore only: Restore from existing backups, according to the edition.
  • Still available in restore only: Browse and export existing backup data.
  • Still available in restore only: Start a VM from an existing replica.
  • Still available in restore only: Retention and storage cleanup.
  • Still available in restore only: Renewing the licence.
  • Stopped in restore only: New backups, including scheduled and incremental.
  • Stopped in restore only: New or updated replication.
  • Stopped in restore only: Adding workloads to protection.

Restore only follows the edition

An edition that never permitted recovery onto a different hypervisor does not gain it in restore only, and an edition that did permit it keeps it. The state changes what may run, not what the edition was entitled to.

The One-Time Migration Licence

A one-time migration licence is a project licence rather than a tier. It pays for the move itself, and for nothing after it.

A unit binds to one named VM and is permanently consumed when that migration is committed. It is not released back into a pool afterwards and cannot be re-pointed at another workload.

Ongoing protection is a separate purchase. Once the workload is running on its destination platform, protecting it needs a subscription licence sized for that estate.

  • Maximum protected VMs: one named VM per unit.
  • Every replication, failover and restore entitlement this licence carries is recorded in the capability matrix as "migration workflow only".
  • It does not carry ongoing backup, and it does not carry reverse replication or failback.

A committed migration consumes the unit

The consumption point is the commit: a committed restore or a committed failover that promotes the workload onto its destination platform. Once that happens the unit is spent and is not returned.

Packs, Ceilings And Quotes

Subscription capacity is sold in packs, and each edition's pack size is listed with it above. A protected-VM ceiling, where an edition has one, is the largest estate that edition may be licensed for; the entry edition is the only one that carries a ceiling.

Enterprise Plus is priced on a quote rather than a published price, and is scoped with the sales team. Current published prices for the other editions are on the Sendense pricing page.

Related Docs