Xoxoday deploys platform updates using continuous CI/CD pipelines and canary or blue-green deployment strategies, ensuring end users experience zero disruption during routine releases, with advance notification provided for any scheduled maintenance window that requires downtime.
Upgrade strategy built around continuity
Xoxoday treats system upgrades as a continuous, low-impact process rather than a disruptive event. The engineering team follows a CI/CD (Continuous Integration and Continuous Delivery) model, where code changes are tested, validated, and deployed incrementally as soon as they are ready. This means that your organisation’s users — whether they access Xoxoday through a browser, via the Slack integration, or through the Microsoft Teams app — experience updates as seamless improvements rather than interruptions.Blue-green and canary deployments
The core of Xoxoday’s zero-downtime release process is its use of blue-green and canary deployment techniques. In a blue-green deployment, two identical production environments run in parallel. Traffic is shifted from the active environment to the updated one only after the new version has passed all validation checks, eliminating any window of instability. Canary deployments go further by gradually routing changes to a small subset of users first, monitoring for errors, and then progressively increasing traffic once stability is confirmed. If any issue surfaces, traffic is immediately redirected to the previous environment, and end users are shielded from the impact entirely. These techniques are especially important when Xoxoday updates integrations with third-party HR systems such as Workday, SAP SuccessFactors, or Darwinbox. A phased rollout ensures that data flows between Xoxoday and these connected platforms remain uninterrupted during the transition.Planned downtime: advance notice and lean-hour scheduling
In rare cases where a major release requires a brief maintenance window, Xoxoday follows a structured communication and scheduling process. Customers receive advance notification through official channels well before the maintenance window begins. All such deployments are planned during lean hours — typically early morning on weekends — when user activity on the platform is at its lowest. This approach reflects Xoxoday’s commitment to maintaining agreed service levels while delivering meaningful product improvements.Monitoring and rollback readiness
Every deployment is accompanied by automated health checks and real-time monitoring. If post-deployment metrics deviate from expected thresholds, the system triggers an automatic rollback, restoring the previous stable state without manual intervention. This operational discipline means that even in the unlikely event of a regression, recovery time is measured in minutes rather than hours. Organisations evaluating platform reliability alongside this deployment model can reference Xoxoday’s ISO 27001 certification and SOC 2 Type II attestation, both of which mandate documented change management processes consistent with these practices. Learn more: Xoxoday Help Centre — System requirementWhat is Xoxoday's platform uptime SLA?
Learn about Xoxoday’s committed uptime guarantees and how service levels are measured and reported to your organisation.
How does Xoxoday manage data backup and recovery?
Understand Xoxoday’s backup frequency, retention policies, and recovery time objectives for business continuity.