> For the complete documentation index, see [llms.txt](https://docs.neurox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neurox.com/installation/alternative-install-methods.md). # Alternative Install Methods Generally, we recommend most users deploy a single, combined Neurox Control + Workload cluster for simplicity. See [Install Neurox](/installation/install-neurox.md). However, this default method requires that the Kubernetes cluster to have all 3: ingress, persistent disk, and GPU nodes. Sometimes clusters with GPU nodes may not have ingress or persistent disk, such as certain on-prem deployments. Neurox is architected in such a way that the Control plane components and the Workload management components can be deployed separately to different Kubernetes clusters due to infrastructure or networking constraints. See [Architecture Overview](/architecture/overview.md) for more information. ## Install Neurox Control plane standalone Neurox Control can be installed anywhere that has ingress and persistent disk and does not require GPU nodes (those can be joined as Workload clusters with GPU nodes). A common approach is to deploy Neurox Control onto vanilla EKS, GKE, AKS or IKS cluster. See [Neurox Control plane standalone](/installation/alternative-install-methods/neurox-control-plane-standalone.md) for instructions. --- # 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://docs.neurox.com/installation/alternative-install-methods.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.