> For the complete documentation index, see [llms.txt](https://docs.zerve.ai/zerve-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerve.ai/zerve-docs/self-hosting/self-managed.md). # Self-managed installs Run the whole of Zerve on your own infrastructure, including on-premises and air-gapped installs. With a **self-managed** install, your organization runs the whole of Zerve, including the app itself, on its own Kubernetes infrastructure. It suits organizations that need everything inside their own network. Self-managed installs have their own detailed documentation, covering requirements, installation, sign-in with your own identity provider, AI model providers, compute, storage and security configuration. **It's available on request**: contact your Zerve account team. ## Air-gapped installs A self-managed install can run with **no internet access**. It uses: * Your own **container registries**, with Zerve's base images mirrored into them * Your own **package mirrors**, for Python and Linux packages * Your own **LLM gateway**, so all model traffic goes to an endpoint inside your network ## Self-managed or bring your own cloud? If your requirement is for your **code and data** to stay in your own cloud account, [bring your own cloud](/zerve-docs/self-hosting/self-hosting.md#bring-your-own-cloud) is simpler: Zerve keeps running the app, and you don't manage any of it. Choose a self-managed install when the app itself must run inside your network too. --- # 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.zerve.ai/zerve-docs/self-hosting/self-managed.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.