> 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/high-availability.md).

# High Availability

Bindplane is capable of running in high availability (HA) mode. Bindplane runs in an **active-active** HA mode, meaning that the workload of the application is spread across all nodes in the cluster.

<figure><img src="https://1405008107-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgmiOMzBfoNFwmKJFHMcJ%2Fuploads%2Fgit-blob-09498b95bf7d8aad8aa31824063a131d01ae592c%2Fproduction-checklist-bindplane-high-availability-readme-image-1.png?alt=media" alt="Bindplane docs - High Availability - image 1"><figcaption></figcaption></figure>

When operating Bindplane in high availability, several user-managed components are\
required.

* [Load balancer](/production-checklist/bindplane/high-availability/load-balancer.md)
* [PostgreSQL](/production-checklist/bindplane/high-availability/postgresql.md)
* [Prometheus Measurement Database](/production-checklist/bindplane/high-availability/prometheus.md)
* [Event Bus](/production-checklist/bindplane/high-availability/event-bus.md)

One or more Bindplane servers can be installed. Each server is stateless. All data is stored in the Postgres and Prometheus databases. Communication between servers is handled by the event bus. The configuration between all Bindplane servers should be the same.

### Example Implementations

#### Google Cloud

See the [Multi Node Architecture On Google Cloud](broken://pages/3Fc7OnBWxDIVttFF4qKI) guide for details on how to deploy Bindplane server's distributed architecture on Google Cloud using services such as Cloud Load Balancer, Pub/Sub, and CloudSQL.


---

# 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/high-availability.md?ask=<question>&goal=<user_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.