> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/self-hosting/guides-for-self-hosting/deployment-overview.md). # Deployment Overview Overview of Juspay Hyperswitch deployment considerations including topology, environments, security, and monitoring For an Enterprise-grade production installation of Juspay Hyperswitch the recommended approach is to deploy Kubernetes on a managed cloud - Google Cloud Platform, Amazon Web Services or Microsoft Azure. The following is the high-level flow for a Hyperswitch deployment: The critical considerations to be made for the deployment are as follows: * Choosing the deployment topology (Single-region, Multi-region, Active-Passive) * Choosing the Hyperswitch environments to deploy (Test, Sandbox, Production) * Kubernetes Cluster and Namespace separation strategy * Helm Chart customization * Scale and Upgrade strategy * Ensuring security and compliance * Setting up the monitoring stack The recommendations for each of these considerations can be found in the subsequent sections. --- # 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.hyperswitch.io/self-hosting/guides-for-self-hosting/deployment-overview.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.