XMPro Deployment Overview

XMPro platform deployment follows a three-phase responsibility model designed to leverage customer infrastructure expertise while ensuring successful application deployment. This approach separates infrastructure provisioning (customer responsibility) from application deployment and post-deployment configuration (XMPro/Implementation Partner responsibility), enabling efficient deployment across Azure and AWS.

Note

XMPro 5.0 deploys on Kubernetes. Start with the Azure Kubernetes (AKS) or AWS Kubernetes (EKS) deployment guide. A Windows installer / Windows Server 2022 deployment option is planned for 5.1.0.

Key Benefits:

• Clear Ownership: Defined responsibility boundaries prevent deployment delays
• Customer Control: Infrastructure remains under customer governance and compliance
• Expertise Alignment: Customers manage infrastructure, XMPro manages application deployment
• Flexibility: Supports Azure and AWS deployments. On-premises Windows Server is planned for 5.1.0

Deployment Responsibility Matrix

Customer Responsibilities	XMPro / Implementation Partner Responsibilities
Infrastructure Provisioning Provision all required infrastructure resources including compute, database, storage, and networking components as specified in the respective deployment documentation (Azure Kubernetes, AWS Kubernetes, Windows Server 2022)	Application Deployment Deploy XMPro applications using automated deployment scripts and configuration management
Platform Configuration Configure compute resources, networking, security groups, and ensure all prerequisites are met	Service Integration Configure inter-service communication, authentication flows, and application-specific settings
Database Setup Install and configure SQL Server, create required databases with proper security and network access	Data Migration Execute database schema migrations and populate configuration data during deployment
Security & Compliance Implement firewall rules, certificate management, and ensure compliance with organizational policies	Application Security Configure application-level security, encryption, and authentication between XMPro services
Network & Access Control Configure network access, load balancing, and provide secure access for deployment team	Operational Validation Perform end-to-end testing, health checks, and validate all XMPro functionality
Documentation & Handoff Provide access credentials, network topology, and infrastructure documentation to deployment team	Knowledge Transfer Deliver operational documentation, training, and ongoing support for XMPro platform

Getting the deployment assets

From 5.0 onward the Kubernetes deployment scripts, the container images, and the security artifacts (SBOMs and scan results) are delivered to each customer rather than published on public endpoints. There is no anonymous download.

Asset	How it is delivered	What you need
Terraform modules (AKS, EKS) and Helm charts	Pushed by XMPro into a repository on your organisation's own systems; updated when XMPro publishes changes	Read access to that repository
Container images	Registry location and credentials confirmed in your delivery package	The registry credentials from your delivery package
SBOMs, SAST/DAST and container scan results	Pushed by XMPro alongside the deployment repository	Read access to that repository

Important

How to get access. The deployment assets — Terraform modules, container images, and security artifacts — are delivered directly to your organisation's own systems by XMPro ahead of your deployment. Contact your XMPro Engagement Lead to arrange this. The repository URL and container image credentials used in the deployment guides are confirmed as part of your delivery package.

Delivery is a customer-side prerequisite: arrange it with your Engagement Lead before Phase 1 begins, because the infrastructure templates and the images are both part of it.

Three-Phase Deployment Model

XMPro deployments follow a three-phase approach: provision the infrastructure, deploy the applications onto it, then configure the platform for use:

Phase 1: Infrastructure Provisioning

Objective: Establish the foundational infrastructure required for XMPro applications

Customer Focus:

• Provision resources or infrastructure
• Configure networking, security, and database systems
• Ensure all prerequisites are met per specifications

XMPro / Implementation Partner Focus:

• Provide technical guidance and infrastructure requirements
• Validate that infrastructure meets application needs
• Approve readiness for application deployment

Phase 2: Application Deployment

Objective: Deploy and configure XMPro applications on the prepared infrastructure

Customer Focus:

• Provide access and coordinate with deployment team
• Review and approve go-live authorization

XMPro / Implementation Partner Focus:

• Execute application deployment using automated scripts
• Configure inter-service communication and security
• Perform end-to-end testing and validation

Phase 3: Post-Deployment Configuration

Objective: Make the deployed platform ready for its users and workloads

Customer Focus:

• Nominate the first company administrator and confirm licensing details
• Identify the data sources and integration components the first Data Streams need

XMPro / Implementation Partner Focus:

• Set up the first tenant company and user access
• Deploy Stream Hosts and upload agents and connectors
• Deliver knowledge transfer and documentation

Key Benefits of This Approach

• Clear Separation: Infrastructure, application, and configuration concerns are handled independently
• Expertise Alignment: Each party focuses on their area of expertise
• Risk Mitigation: Issues are identified and resolved at the appropriate phase
• Flexibility: Works with or without implementation partners

RACI Matrix

Activity	Customer	XMPro / Implementation Partner
Infrastructure Provisioning	A/R	C
Platform Configuration	A/R	C
Database Setup	A/R	C
Security & Compliance	A/R	C
Network & Access Control	A/R	C
Documentation & Handoff	A/R	I
Application Deployment	C	A/R
Service Integration	C	A/R
Data Migration	C	A/R
Application Security	C	A/R
Operational Validation	C	A/R
Post-Deployment Configuration	C	A/R
Knowledge Transfer	I	A/R

RACI Legend:

• R - Responsible (performs the work)
• A - Accountable (ensures completion and quality)
• C - Consulted (provides input and expertise)
• I - Informed (kept updated on progress)

Documentation Requirements

Customer Must Provide

Infrastructure Documentation:

• Network architecture and security configurations
• Access credentials and administrative permissions
• Environment specifications and resource details
• Compliance and security policy requirements

XMPro / Implementation Partner Will Provide

Deployment Documentation:

• Installation procedures and validation steps
• Configuration guides and operational manuals
• Architecture diagrams and technical specifications
• Troubleshooting guides and ongoing support documentation

Deployment Process Overview

Infrastructure and Application Deployment (Phases 1 and 2)

Deploy XMPro - Infrastructure provisioning and platform deployment using:

• Azure Kubernetes (AKS) - Kubernetes-native deployment on Azure
• AWS Kubernetes (EKS) - Kubernetes-native deployment on AWS
• Azure App Service - Container-based deployment for customers staying on the App Service architecture (v4.6 only)
• Windows Installer - Native IIS deployment for on-premises Windows Server environments. Planned for 5.1.0 and not available in 5.0.0
• Legacy Options - ARM templates for v4.4 and earlier versions

Post-Deployment Configuration (Phase 3)

Post-deployment - Complete the setup with:

• Tenant Configuration - Set up your first tenant company
• Stream Host Deployment - Add additional processing capacity as needed
• Agents & Connectors - Upload and configure integration components

---

This responsibility model ensures successful XMPro deployments while maintaining clear boundaries, leveraging respective expertise, and enabling scalable deployment processes across diverse customer environments.

---

Last modified: September 28, 2026