# Getting Started with DuploCloud DuploCloud manages cloud infrastructure in over two hundred organizations ranging from startup, small businesses to publicly listed companies. We categorize our clients into two segments: * **Young companies** with little to no in-house DevOps expertise and very limited automation. Typically, these organizations want to completely revamp their DevOps stack and move to modern technologies like Kubernetes. In this scenario, DuploCloud is installed in a fresh cloud account, and the organization’s existing deployment is migrated to the new account using state-of-the-art automation, pipelines, security, observability, and compliance—supporting Kubernetes and serverless deployment models. Data sources like databases, S3 buckets, etc., are migrated to the new account or remain in existing accounts. The onboarding process is described in detail in the next section. * **Mature organizations** with significant in-house DevOps expertise. Mature organizations must decide between operating in their existing account or migrating to a new account. If an organization wants to modernize, for example, migrating from VM to K8s, moving to a new account is the best option. However, if there is already a mature K8s automation stack, it may be imported into DuploCloud and mapped to the DuploCloud constructs described in the policy model. Most use cases in mature organizations involve leveraging AI to build AI DevOps teammates that help handle growing volumes of support tickets and reduce DevOps backlog, allowing human teams to focus on higher-value work. --- # Agent Instructions: 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: ``` GET https://docs.duplocloud.com/docs/getting-started/welcome-to-duplocloud.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.