Customer-side encryption
Backup chunks and manifests are encrypted before they leave the customer network. Recovery keys are not silently escrowed as plaintext at ZCHPC.
Enterprise backup & disaster recovery
Your organisation’s recovery plan, off-site and under control.
Protect servers, files, databases and branch workloads through encrypted outbound connections to ZCHPC. Customer recovery keys remain customer-side, while the managed recovery service stays private behind the service edge.
Client-side encryptionOrganisation-isolated recovery storageAuditable recovery
Customer location
Production systemsServers · NAS · databases
↓
ZCHPC Backup AgentEncrypts locally · outbound only
HTTPS / mTLS
ZCHPC service edge
Secure service edgeSigned authorization · exact accounting
↓
Managed recovery servicePrivate, resilient recovery storage
Checking recovery service state…
Built for organisations that cannot afford to discover their backup problem during an incident.
Encrypted before transferOutbound customer connectivityExplicit recovery authorizationServer-side organisation isolation
A practical protection model
No stretched VLAN. No public storage nodes. No inbound customer firewall rule.
ZCHPC Backup uses a location gateway or host Backup Agent inside the customer network. It reaches the service over an outbound encrypted connection, receives short-lived protection authorization and sends ciphertext only.
- 01Enroll the location
A one-time bootstrap token is exchanged for an organisation-and-location-bound device certificate.
- 02Bind local sources
Source paths stay on the Backup Agent. The central service only needs the protected system identity.
- 03Protect automatically
Protection Settings schedule unattended encrypted backups when the recovery service is genuinely ready.
- 04Recover with evidence
Portal authorization is followed by Backup Agent recovery execution and terminal proof.
Security is in the architecture
Control-plane convenience without custody shortcuts.
Certificate-bound Backup Agents
Short-lived enrollment tokens bootstrap device identity; routine protection traffic uses mTLS-bound certificates rather than permanent shared passwords.
Signed service authority
The portal signs protection authorization. The protected-data service independently signs receipts. Neither authority can impersonate the other.
Fail-closed service readiness
If recovery-service readiness is not proven, production protection movement remains blocked instead of accepting customer data optimistically.
Recovery is the product
A backup is only useful when the recovery path is explicit.
Every recovery point belongs to one organisation, location and protected system. Recovery requests name an approved target, are claimed by the correct Backup Agent and remain “running” until execution reports a terminal result.
✓ Portal-authorized recovery request✓ Location-bound Backup Agent execution✓ Protected data retrieved from managed recovery storage✓ Customer-side decryption✓ Auditable completion or failure
ZCHPC Backup
Build recovery readiness before the incident.
Activate the service for operator setup, or sign in to manage an existing organisation.