Xoxoday provides a minimum of two distinct environments — a sandbox (staging) and a production environment — by default, and maintains both throughout the full lifecycle of the engagement.
Sandbox and Production: Two Environments by Default
Xoxoday provisions at least two environments for every implementation: a sandbox (staging) environment and a production environment. This separation is standard practice and is established before onboarding begins, giving your team a dedicated space to validate configurations before anything reaches live operations. The sandbox environment is purpose-built for training, testing, and internal validation. Your HR, IT, and operations stakeholders can explore Xoxoday’s reward and recognition workflows, configure payout rules, test integrations, and run end-to-end scenarios — all without touching real employee data or live transactions. For example, if your organisation is integrating Xoxoday with Darwinbox or SAP SuccessFactors, the sandbox lets your team validate data mappings, workflow triggers, and sync schedules before the connection goes live. The production environment is activated once configurations are reviewed and approved. It handles actual reward issuance, redemptions, and reporting for your workforce. Because all user acceptance testing happens in the sandbox first, the production rollout is low-risk and predictable.Why Environment Segregation Matters
Keeping sandbox and production separate is a core data security practice. It ensures that test data, dummy accounts, and configuration experiments never contaminate your live reward ledger or employee records. Xoxoday’s architecture aligns with standards such as ISO 27001 and SOC 2 Type II, and environment isolation is a direct expression of those controls. This separation also strengthens change management. When your organisation rolls out a new reward programme, updates an approval workflow, or onboards a new business unit, those changes are first validated in the sandbox. Your IT team can configure a Slack or Microsoft Teams notification trigger in the sandbox, verify the employee experience end to end, and only then promote the change to production.Maintained for the Full Engagement Lifecycle
Both environments remain active after go-live — not just during initial implementation. Your team retains sandbox access for ongoing regression testing, training new administrators, and trialling future enhancements without service disruption. This continuity means your organisation always has a safe space to test before committing any change to production, whether that is six months or three years into the engagement. Learn more: Xoxoday Help Centre — ImplementationData Security and Compliance Standards
Learn how Xoxoday’s ISO 27001 and SOC 2 Type II certifications protect your organisation’s data across all environments.
Go-Live Readiness and Cutover Process
Understand the steps Xoxoday follows to validate sandbox configurations and promote them safely to production at go-live.