> 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-cloud/networking-requirements.md).

# Networking Requirements

## Firewall Requirements

The following firewall rules are required for accessing Bindplane Cloud. This includes user browsers, API clients, and collectors.

### app.bindplane.com

The primary endpoint for Bindplane Cloud is `https://app.bindplane.com`. This endpoint serves all user traffic including browsers, API clients, and managed collectors.

#### Endpoints

Bindplane provides an [Open API spec](/cli-and-api/api.md) with programmatic access to all Bindplane functionality.

* REST API — `https://app.bindplane.com/v1/<endpoint>`
* OpAMP — `wss://app.bindplane.com/v1/opamp`

#### Protocols

The following operations access `app.bindplane.com` over port `443`:

* API requests (HTTPS REST) — `/v1/<endpoint>`
* User browsers (HTTPS and WebSocket)
* Collectors (OpAMP WebSocket) — `/v1/opamp`

Your firewall and/or proxy must allow WebSocket upgrades.

#### Egress

Allow outbound access to Bindplane Cloud:

* **Host:** `https://app.bindplane.com` (TLS)
* **IP:** `34.120.255.184`
* **Port**: `443/tcp`

Note: IP addresses associated with `app.bindplane.com` can change in the future. If your environment supports it, prefer allowing outbound access by hostname (SNI/explicit proxy allowlist) rather than pinning a single IP. If you must pin IPs, ensure you have a process to update allowlists when the resolved IP changes.

Outbound access to Bindplane Cloud is required to support collector management.

#### Ingress

Bindplane Cloud does not require inbound access into customer networks. Collectors initiate outbound connections to Bindplane Cloud; Bindplane Cloud does not initiate inbound connections to collectors.

### Other Endpoints

#### bdot.bindplane.com

Collector installation scripts utilize this endpoint for collector downloads. This endpoint uses HTTPS and does not require websockets.

Allow outbound access to Bindplane Cloud:

* **Host:** `https://bdot.bindplane.com` (TLS)
* **IP:** `34.36.182.107`
* **Port**: `443/tcp`

## FAQ

**Q**: Does Bindplane use Transport Layer Security (TLS)?\
**A**: All connections to Bindplane cloud utilize Transport Layer Security (TLS).


---

# 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.bindplane.com/production-checklist/bindplane-cloud/networking-requirements.md?ask=<question>&goal=<endgoal>
```

`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.