Sendense Documentation

Editions And Licensing

Sendense runs in CSP or MSP edition. The partner licence selects the edition; CSP records entitlement and allocates operational VM quotas without signing licences.

Documents Home

Concept

Editions And Licensing

Sendense runs in CSP or MSP edition. The partner licence selects the edition; CSP records entitlement and allocates operational VM quotas without signing licences.

ReadyCurrentscalicensingeditionsquotacsp

Overview

Sendense ships as one product in two editions, CSP and MSP. The edition a deployment runs is selected by the customer's own partner license, not by a separate purchase of the appliance.

The SCA (Sendense Central Appliance) is available only to MSP and CSP customers. It is not a separately-charged device; the customer's partner-tier license is what makes it available.

The Two Editions

The two editions differ in their commercial model rather than in the underlying product.

CSP edition
Supports multi-tenant resale and sub-allocation. The provider carves its VM pool across tenants, sets a resell price per tenant, and sub-allocates operational quota down to each tenant.
MSP edition
Licenses each customer SHA independently, with no resale pricing and no sub-allocation. Each customer is an independent organization with its own SHA rather than a tenant of the provider.

Edition Selection

The edition derives from the signed partner license: its partner sales channel combined with an SCA-capable product tier. The channel selects CSP or MSP, and the tier gates eligibility for the SCA.

Where no partner license is applied, or the applied license is not a partner license, the edition falls back to a configured value on the SCA.

Operational VM Quota

The operational-quota model applies to the CSP edition. In it, the provider holds a single VM-measured entitlement, recorded on the SCA as an operational pool, and carves that pool across its tenants. The MSP edition has no provider pool to carve.

  • Each tenant receives a per-tenant sub-allocation of the pool; the SCA enforces that the sum of the tenant sub-allocations does not exceed the pool quota.
  • Per-tenant utilization is measured as a 30-day high-water count of protected VMs.
  • The pool and its sub-allocations are operational quota, enforced by visibility and admission rather than by a signed entitlement on each tenant SHA.

What Licensing Does Not Do

The SCA requests entitlements but never signs them. License signing stays central: the central registry is the only signer, and an offline SCA can monitor entitlement but cannot mint or mutate it.

The SCA does not issue cryptographic or delegated per-tenant child licenses. Sub-allocation is operational quota only; signed per-tenant child licensing is a deferred hardening layer and is not part of the current model.

The SCA never signs licenses

It records and sub-allocates operational quota and requests entitlements from the central registry, which remains the only signer.

MSP Licensing

In the MSP edition, each customer SHA is licensed independently, with its entitlement assigned per appliance rather than carved from a provider pool.

There is no resale pricing and no sub-allocation in the MSP edition; the pool-carve and per-tenant quota model applies only to the CSP edition.

Related Docs