> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/overview-2/container-deployments.md). # Container Deployments Orchestration across multiple Cloud providers Approximately 90% of workloads deployed on DuploCloud run in Docker containers. The platform orchestrates these containerized applications using **Azure Kubernetes Service (AKS)** or **DuploCloud's built-in orchestration engine**, which offers a simpler alternative to Kubernetes. On Microsoft Azure, DuploCloud supports many application hosting options, including AKS, Azure WebApps, and native Docker containers. This flexibility allows users to leverage the most appropriate orchestration model for their workloads while working within a cloud-neutral interface. DuploCloud also supports a wide range of application types beyond containers. If you need support for a custom Service, please contact the DuploCloud support team. The typical turnaround time is one business week. --- # 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.duplocloud.com/docs/automation-platform/overview-2/container-deployments.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.