Concept
CSP-Provisioned Tenant SHA
How a CSP provisions and operates a dedicated single-tenant Sendense appliance for each customer, with structural isolation and a tenant portal.
Relationship
In the CSP edition the provider provisions and operates a dedicated single-tenant appliance for each tenant, and runs those appliances together as a multi-tenant platform. Each tenant SHA remains the hub appliance for that tenant's deployment.
CSP operating model
The SCA provisions and operates each tenant's appliance as a provider platform layer, and each tenant reaches its own appliance through the SCA.
Provider-led provisioning
The CSP provisions and operates each tenant's dedicated appliance as part of the provider platform layer, and continues to manage licensing for it.
Tenant access through the front door
Each tenant reaches its own dedicated appliance through the SCA front door. The provider decides whether a tenant receives the full GUI, selected capabilities, or API-only access.
Provider Platform Layer
The CSP operates the SCA as the provider platform layer above the tenant appliances. It provides:
- The tenant front door, where each tenant authenticates and is taken into its own appliance.
- Provisioning and onboarding of tenant appliances into the tenant's cloud account.
- Centralized storage offerings the provider can assign to tenants.
- Licensing quota that governs how much protected capacity each tenant may consume.
- Metering and billing across tenants.
- The provider API for platform-level automation.
Dedicated Single-Tenant Appliance
Each tenant runs on its own dedicated single-tenant appliance, with its own database and its own authentication realm. The appliance belongs to one tenant only.
A tenant's single appliance still spans that tenant's whole estate. It coordinates every source agent and site that belongs to the tenant, so a dedicated appliance is a per-tenant boundary, not a per-site or per-workload one.
Isolation is structural
One tenant's appliance has no access to another tenant's appliance, database, or credentials, so cross-tenant data leakage cannot occur. Separation comes from running each tenant on its own appliance, not from row-level rules inside a shared system.
Provider-Led Provisioning
The CSP provisions each tenant appliance into the tenant's own cloud account, with the correct networks, templates, storage offerings, and quotas already in place.
This is an optional zero-touch onboarding capability that automates provisioning almost end-to-end for provider-owned appliances, with a small number of residual manual steps.
The optional automation layer applies to provider-owned appliances only. The manual enroll-and-consent path is unchanged for customer-administered appliances, and destroying a never-enrolled appliance left behind by a failed provision remains a manual provider step.
Tenant Access
Tenants authenticate at the SCA front door and are taken into their own appliance's GUI and API. They reach their dedicated appliance through the provider rather than by connecting to it directly.
The provider chooses how much of the appliance each tenant sees: the full GUI, a selected set of capabilities, or API-only access. The provider can also enable or disable sellable add-on features per tenant.
CSP Versus MSP
The CSP tenant model and the MSP delegated model are different arrangements and should not be conflated:
Related Docs