> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/security-privacy-and-compliance/enterprise-infrastructure.md). # Enterprise Infrastructure This article provides a high level overview. For more detailed information, head to [Trust Center](https://trust.rhythms.ai/) See how Rhythms' enterprise infrastructure ensures reliability, security, and scalability with Azure hosting, backups, and integrations. Our infrastructure is built to meet the demanding needs of enterprise customers, providing robust, scalable, and reliable services with comprehensive backup and disaster recovery capabilities. ## **Enterprise-grade Azure Infrastructure** Microsoft Azure infrastructure with 24/7 monitoring, 99.9% target availability, and global CDN implementation for optimal performance across regions. ## **Reliable Backup Infrastructure** Point-in-time recovery with 35-day retention, weekly geo-redundant backups with 1-year retention, and regular backup testing and validation. ## **Enterprise Integration Suite** Comprehensive SSO support, SCIM provisioning, and extensive enterprise integrations for seamless deployment in your environment. ## **Built for Enterprise Scale** Performance optimization through caching, US-based data centers with planned EU and APAC expansion, and robust reliability measures. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.rhythms.ai/security-privacy-and-compliance/enterprise-infrastructure.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.