Overview
SCA Overview
Sendense Central Appliance for MSP telemetry, controlled remote access, and CSP provider automation.
Definition
SCA is the Sendense Central Appliance. It is the central appliance role for MSP and CSP Sendense deployments.
SCA runs in the provider or central Sendense management environment, above customer or tenant SHA deployments.
SCA And SHA
SHA remains the hub appliance for protection, recovery, EBA, SNA, snagent, and local operational orchestration.
SCA sits above SHAs for provider-level oversight, access, billing, API, provisioning, and license-management workflows, depending on edition and deployment model.
MSP Use
For MSP deployments, SCA provides central telemetry and controlled remote operations across customer SHAs. An MSP can use SCA to see customer estate health, review operational status, and perform agreed SHA operations where the customer or deployment model allows it.
Enrollment can be customer-led or MSP-led depending on the relationship between the MSP and the customer.
CSP Use
For CSP deployments, SCA provides the provider platform layer for multi-tenant billing, API access, provisioning, and license management.
CSP enrollment is provider-led and designed for automation as part of tenant provisioning. The CSP decides whether a tenant receives SHA GUI access, selected SHA capabilities, API access, or only workflows exposed through the CSP's own platform.
Deployment Shapes
SCA appears in two deployment shapes. A standalone customer SHA does not require SCA.
What SCA Is Not
- SCA is not SHA. SHA remains the hub appliance for the customer or tenant deployment.
- SCA is not SNA. SNA is the backup proxy virtual appliance.
- SCA is not snagent. snagent is the CloudStack KVM hypervisor host agent.
- SCA is not EBA and does not become the backup repository.
Related Docs