Sendense Docs
Architecture Overview
Which components connect to the SHA hub, which paths stay local, and how CloudStack recovery estates participate.
Platform Topology
Three Zones. Clear Responsibility Boundaries.
Sendense separates source protection, hub orchestration and CloudStack recovery while keeping the primary control paths outbound to the SHA. Detailed sizing and the full port table are covered in deployment guidance.
Sendense Architecture Overview
Control, repository and recovery roles across source and recovery estates.
Direct site-to-site replication runs between source and recovery SNAs when policy requires it.
01
Source Estate
The environment where workloads are protected.
SNA
Site node appliance
Controller VMs
Deployed from the Sendense Controller Template when replication requires target-side intake.
Source Platform
VMware, CloudStack or another supported protected estate.
Source SNA To SHA
Outbound 443
02
Sendense Hub
The control point for policy, recovery coordination and repository governance.
SHA
UI, API, orchestration, policy and recovery evidence.
Repository Governance
EBA Repository
Repository services for efficient, encrypted and governed recovery points.
CloudStack SNA To SHA
Outbound 443
SNAgent To SHA
Outbound 443
03
CloudStack Recovery Estate
The recovery, migration or service provider target environment.
CloudStack SNA
Coordinates CloudStack protection and recovery workflows.
Controller VMs
Receive and coordinate replication traffic for recovery-side workflows.
KVM Hosts With SNAgent
Host-aware CloudStack integration for non-NFS and mixed storage estates.
Outbound 443
SNAs and hosts running SNAgent initiate control connectivity to the SHA hub.
Replication
Source and recovery SNAs coordinate direct site-to-site replication when policy requires it.
Local Controller
Controller VMs support replication intake and recovery-side coordination inside each estate.
Host Integration
SNAgent gives CloudStack KVM hosts the local integration needed for storage-aware protection.
Operating Model
Separation Of Roles Keeps Recovery Manageable.
Site appliances, hub services, repository services and CloudStack host integration each have a distinct role. That separation keeps the recovery path easier to reason about and operate.
Site-Led Connectivity
Protected sites initiate the control path.
SNAs and hosts running SNAgent connect outbound to the SHA over 443, avoiding broad inbound management exposure.
Hub Governance
The SHA coordinates policy, evidence and recovery.
Orchestration, inventory context, recovery evidence and repository governance stay together in the hub.
Repository Layer
EBA keeps retention attached to the recovery point.
Enterprise Block Archive provides the repository layer for governed recovery points across local, remote or S3-compatible targets.
CloudStack Native
SNAgent makes KVM storage part of the model.
CloudStack KVM hosts can participate in backup and recovery without forcing every deployment into an NFS-only design.
Next: Component Reference
Use the component reference for concise definitions of SHA, SNA, SNAgent, EBA and the Sendense Controller Template.