For the complete documentation index, see llms.txt. This page is also available as Markdown.

Networking Requirements

Bindplane Server can run fully offline, but certain optional features such as version detection, analytics, or LLM integrations require network connectivity to specific endpoints.

No outbound internet connectivity is required for running Bindplane Server (Self-Hosted).

However, several optional features and integrations may require access to external endpoints.

Feature
Outbound Internet Connection Required
Description

Bindplane Server

No

Operates fully offline

Optional

Checks for new BDOT releases

Analytics

Optional

Sends anonymized usage metrics

Google SecOps Integration

Optional

Enables SecOps-specific features


Bindplane API Endpoints

NOTE

For self-hosted Bindplane, the UI can be accessed with your browser on port 3001. The URL will be http://<IP_ADDRESS>:3001, with IP Address being that of the Bindplane Server. To log in, use the credentials you specified when running the init command.

Bindplane provides an Open API spec with programmatic access to all Bindplane functionality.

  • REST API — http://<IP_ADDRESS>:3001/v1/<endpoint>

  • OpAMP — wss://<IP_ADDRESS>:3001/v1/opamp

GitHub Endpoints (for legacy or custom configurations)

  • https://api.github.com/

  • https://github.com/observIQ/bindplane-otel-collector/

  • https://raw.githubusercontent.com/observIQ/bindplane-otel-collector/


Collector Version Detection

Bindplane periodically checks for new versions of the Bindplane Collector (BDOT). Depending on your deployment type and version, it uses the following endpoints:

Deployment Type
Version / Date
Default Endpoint
Notes

Bindplane Cloud

Since 2025-08-12

https://bdot.bindplane.com

Current default

Bindplane Self-Hosted

Since v1.94.0

https://bdot.bindplane.com

Can be reconfigured to use GitHub

Earlier versions

Before 2025-08-12 (Cloud) or v1.94.0 (Self-Hosted)

GitHub only

Deprecated behavior


Analytics

If analytics are enabled, Bindplane Server may send anonymized usage metrics to https://api.segment.io/

NOTE

Analytics are optional and can be fully disabled in the Bindplane configuration file.


Google SecOps Integration

If you plan to use the Google SecOps Partner Integration, the Bindplane server must be able to reach the following endpoints over outbound HTTPS (port 443):

Endpoint
Purpose

oauth2.googleapis.com:443

OAuth Token Exchange

chronicle.<region>.rep.googleapis.com:443

Data Processing Pipeline Management API

Replace <region> above with the region of your Google SecOps instance.

Last updated

Was this helpful?