> For the complete documentation index, see [llms.txt](https://library.zoom.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.zoom.com/admin-corner/architecture-and-design/cloud-architecture-diagram.md). # Cloud Architecture Diagram {% hint style="info" %} Use the fullscreen arrows in the upper-right corner of the embedded Figma prototype to take a closer look at the Zoom Cloud Architecture diagram. Many product flows have been consolidated into a single "Common Platform Flows" page while some products have unique flows that are detailed on their own page.\ \ Please use the Feedback buttons to let us know if this is helpful and leave a comment with any other ideas we could implement in the future! {% endhint %} {% embed url="" %} {% hint style="warning" %} Having trouble loading the embedded view? Be sure to accept or reject the GitBook cookie request. {% endhint %} --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://library.zoom.com/admin-corner/architecture-and-design/cloud-architecture-diagram.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.