> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/production-checklist/bindplane.md). # Bindplane Server (Self-Hosted) Bindplane is made up of several components. The store, measurements database, and event bus. Bindplane can be configured as a single instance or high availability mode. By default, a Bindplane Server operates in the single instance mode where all components are included in the installation. Optionally, users can operate Bindplane in high availability mode. This documentation will cover each component and where they fit within both operation modes. ### Single Instance Single instance is suitable for small, medium, and large deployments of Bindplane. This mode\ is the easiest way to get started as it requires a single Linux server or virtual machine. Single instance mode is the recommended deployment model for users who prefer simplicity at the expense of fault tolerance. When fault tolerance is required, Bindplane can be configured in high availability mode. {% hint style="info" %} **NOTE** When Bindplane is down due to maintenance or an outage, managed collectors will continue to operate\ like normal. Collectors do not depend on Bindplane to be available. {% endhint %} When operating in single instance mode, Bindplane does not depend on third-party systems such as a remote database. For more details, see the [Single Instance](/production-checklist/bindplane/single-instance.md) documentation. ### High Availability High availability is a great choice for users who can support a more complex deployment to gain\ fault tolerance. When operating Bindplane in high availability mode, an individual Bindplane server\ can go offline for maintenance without causing an outage. The high availability architecture is significantly more complex, as it requires the following\ supporting systems: * 2 or more Bindplane servers * Load balancer * PostgreSQL database * Dedicated Prometheus deployment * Event bus For more details, see the [High Availability](/production-checklist/bindplane/high-availability.md) documentation. --- # 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.bindplane.com/production-checklist/bindplane.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.