Deployment on customer-managed infrastructure allows products to run in an environment managed by your company. When considering this option, evaluate updates, support, monitoring and the responsibilities of both parties alongside data policy.
Key takeaways
- Justify the deployment choice with a business need or regulatory requirement.
- Use the same supported product release across all customers.
- Document customer and Retail Lab. responsibilities clearly.
Classify the requirement correctly
Determine whether the request for deployment on your own infrastructure is driven by data policy, internal security rules, regulation or connectivity requirements. This avoids creating an unnecessarily complex operating model.
Maintain a supported product release
Creating a separate product branch for every customer delays security updates and new features. Deployments on customer infrastructure should also follow the primary product releases supported by Retail Lab.
Validate deployment readiness together
Before deployment, assess requirements such as server capacity, network access, domain names, backup targets and internal account management against a shared checklist.
Plan updates and rollback
Plan the timing, prechecks, data-protection steps and rollback method for each update with the customer. This protects business continuity.
Document responsibilities clearly
The contract should state clearly which party is responsible for infrastructure operations, monitoring, incident notification, updates, data restoration and support access.