Can Xoxoday apply hot patches without disrupting users?

​

Zero-downtime patching by design

Xoxoday is built on a cloud-native architecture that treats continuous delivery and operational stability as first-class requirements. When a security fix, bug patch, or minor update needs to go out, Xoxoday deploys it without taking the platform offline or interrupting active user sessions. This is possible because every component of Xoxoday runs inside Docker containers orchestrated by Kubernetes. Rather than restarting the entire application, Kubernetes performs a rolling upgrade — replacing old container instances one by one while keeping the remaining instances live and serving traffic. At no point during a hot patch deployment does a user encounter an outage, a broken page, or a lost session.

​

How the CI/CD pipeline powers safe deployments

Every code change — whether a critical security patch or a minor configuration update — moves through Xoxoday’s CI/CD pipeline before it reaches production. Automated build, test, and validation stages run first, ensuring that a patch does not introduce regressions before it ever touches a live environment. Once validation passes, the Kubernetes rolling upgrade begins. Traffic is gradually shifted from old instances to newly patched ones, with health checks confirming each new instance is ready before the next old one is retired. If an issue is detected mid-rollout, the pipeline can halt or roll back automatically, protecting users from a faulty release.

​

What this means for integrations and connected workflows

Xoxoday integrates with tools your organisation relies on daily — including Slack, Microsoft Teams, Workday, SAP SuccessFactors, and Darwinbox. Because patches are applied with zero downtime, these integrations remain active and functional throughout any update window. An employee redeeming a reward through a Slack bot or a manager approving a recognition via Microsoft Teams experiences no interruption, even if a patch is being deployed in the background at that exact moment. This matters particularly for organisations running time-sensitive recognition campaigns, automated reward disbursements, or real-time loyalty workflows where even brief platform unavailability would create a poor employee experience.

​

Consistency under change

Rolling upgrades also preserve session state and in-flight transactions. A user halfway through redeeming a reward or an admin running a bulk upload will not see their action fail because a patch landed mid-operation. Xoxoday’s containerised architecture isolates each running instance, so live sessions continue on their current instance while new instances come up with the patched code. This approach aligns with Xoxoday’s broader reliability commitments, which are independently verified as part of SOC 2 Type II and ISO 27001 compliance programs. Change management controls, including patch deployment procedures, are audited as part of these certifications, giving your IT and security teams documented assurance that updates are handled in a controlled, traceable manner. Learn more: Xoxoday Help Centre — Uptime, monitoring