Service Framework
Service boundaries must be agreed, not implied.
A non-binding website overview of the subjects an approved NDC service order and operating runbook must address.
Public framework
Supported website checkout may be enabled for approved NDC Protect offers.
This public framework does not by itself create a recovery right or SLA. When an approved NDC Protect offer is enabled for ordering, the supported customer journey may create a native customer account, issue an order and service entitlement, process payment only through an authorized gateway, and initiate provisioning only after the applicable acceptance controls pass. Every engagement remains subject to the selected product scope, applicable order terms, and authorized customer acceptance.
- Qualified workload, data volume, source health, dependencies, and customer authority
- Scope, exclusions, retention, monitoring, support window, escalation, and responsibilities
- Recovery-verification authorization, destination, limits, evidence, and completion criteria
- Quote, taxes, term, cancellation, privacy, security, liability, and change control
- Credentials, onboarding, offboarding, data return or deletion, and incident communication
Human review
Product scope and recovery authorization remain explicit.
Qualification remains mandatory where the selected product or requested scope requires it. When an approved offer is enabled, the supported customer journey may provide account creation, authorized payment processing, and controlled provisioning; it does not authorize recovery work, bypass manual acceptance where required, or expand the purchased entitlement.