> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/support/service-level-agreement/flosum-devops-data-migrator-and-trust-center-support.md). # Flosum DevOps, Data Migrator, & Trust Center Support As our flagship product, Flosum DevOps is natively built on the Salesforce platform and delivered as a managed package within a Salesforce OEM Production org. This deep integration means Flosum's availability and performance align with Salesforce's infrastructure. Consequently, our service delivery adheres to Salesforce's robust uptime guarantees and recovery SLAs, ensuring enterprise-grade customer reliability. #### From Salesforce: Salesforce Services are designed with continuous improvement and Trust (e.g., Availability, Performance, and Security) in the infrastructure. Salesforce uses commercially reasonable efforts to make its on-demand services available to its customers 24/7, except for planned downtime, for which Salesforce gives customers prior notice, and force majeure events. Excellent availability statistics are critical to Salesforce’s customers’ success and the success of Salesforce as a company. Salesforce generally does not focus on a specific percentage, as they do not believe their job on availability will ever be complete. Live and historical statistics on Salesforce system performance are publicly published at[ https://trust.salesforce.com/en/#systemStatus](https://trust.salesforce.com/en/#systemStatus). Salesforce's Recovery Time Objective (RTO) is 12 hours, and its Recovery Point Objective (RPO) is 4 hours. Salesforce’s disaster recovery plans currently have the following target recovery objectives: (a) restoration of the Service within 12 hours after Salesforce declares a disaster; and (b) maximum Customer Data loss of 4 hours, excluding. However, a disaster or multiple disasters causing the compromise of both multiple Salesforce data centers at the same time, and excluding development and test bed environments, such as the Sandbox service. This page has the Disaster Recovery and Business Continuity Plans[ https://compliance.salesforce.com/en/disaster-recovery-bcp](https://compliance.salesforce.com/en/disaster-recovery-bcp) --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.flosum.com/support/service-level-agreement/flosum-devops-data-migrator-and-trust-center-support.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 `automate deployments from our CI pipeline` 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.