Kadence hosts customer data in one of two regions: the European Union or the United States. Each customer account is hosted in a single region only — we do not split a customer's data across regions or replicate it between them.
Available Regions
EU region: AWS Dublin, Ireland (eu-west-1) — the default region, and where all customers were hosted prior to the introduction of Regional Data Hosting.
US region: AWS Ohio (us-east-2) — available for customers with US data residency requirements.
For a customer hosted in a given region:
Customer data is stored and processed entirely within that region.
Application infrastructure runs in that region.
No persistent customer data is stored outside the customer's chosen region.
This supports enterprise, regulated industry, and public sector data residency requirements.
Choosing a Region
Region is set when a customer's account is first provisioned, based on their data residency requirements. It is not a self-serve, in-app setting — talk to your CSM or [email protected] if you need to confirm or discuss your account's hosting region.
Moving an existing account to a different region after go-live is not a self-serve action and requires a review with your Kadence team — it isn't something that can be toggled at will.
Login & User Experience
Hosting region is designed to be invisible to end users. Everyone signs in at the same normal login page, and the platform automatically routes each user to their account's region in the background — there's nothing for end users to select or configure.
Client & Integration Support
Core web, mobile (iOS and Android), Kadence Agent, and SSO all support both the EU and US regions. If you're building against the Public API from a US-hosted account, make sure your integration points at the US endpoints rather than the default EU ones — contact [email protected] for the correct endpoint details for your account.
Some integrations and features roll out to a new region shortly after the region itself goes live rather than on day one. If you're evaluating a specific integration for a US-hosted (or other non-default region) account, check with your CSM to confirm current support.
Infrastructure & Availability
Kadence runs on AWS using a multi–Availability Zone (multi-AZ) architecture in each region, which means:
Data is replicated across multiple availability zones within the region
The platform remains highly available and resilient to infrastructure failures
Automated, encrypted daily backups are taken and stored separately from production systems
Security
Encryption in transit: All data is protected using TLS
Encryption at rest: Databases, backups, and object storage are encrypted
Monitoring & auditing: AWS services such as CloudTrail and CloudWatch are used for logging and monitoring
Compliance
Kadence leverages AWS infrastructure that is compliant with:
GDPR
ISO 27001
SOC 2 Type II
This helps ensure strong security, privacy, and operational controls across the platform, in either region.
For the most up-to-date information on Kadence security, privacy, and compliance, visit:
https://trust.kadence.co