Global networking creates a secure, private network that connects all your Bnodes within your Brightnode account. This feature enables Bnode-to-Bnode communication as if they were on the same local network, regardless of their physical location across different data centers.Documentation Index
Fetch the complete documentation index at: https://docs.brightnode.cloud/llms.txt
Use this file to discover all available pages before exploring further.
How global networking works
Global networking provides each Bnode with a private IP address accessible only to other Bnodes in your account. This creates an isolated network layer separate from the public internet, which can be used for:- Distributed computing workloads.
- Microservice architectures.
- Secure database connections.
- Internal API communication.
- Multi-Bnode machine learning pipelines.
Enable global networking
To enable global networking for your Bnode:- Navigate to the Bnodes section and click Deploy.
- At the top of the page, toggle Global Networking to filter and show only Bnodes with networking support.
- Select your desired GPU configuration and complete the deployment process.
Connect to other Bnodes
Each Bnode with global networking enabled can be accessed by other Bnodes using its internal DNS name:POD_ID with the target Bnode’s ID. For example, if your Bnode ID is abc123xyz, other Bnodes can reach it at abc123xyz.brightnode.internal.
Test connectivity
Verify network connectivity between Bnodes by opening a web terminal in one Bnode and running:Run internal services
Services running on networked Bnodes are automatically accessible to other Bnodes without exposing ports publicly. Simply bind your service to all interfaces (0.0.0.0) and connect using the internal DNS name.
For example, a database on Bnode abc123xyz listening on port 5432 would be accessible to other Bnodes at:
Security best practices
Global networking provides network isolation, but proper security practices remain essential. Never expose ports on Bnodes running sensitive services like databases, cache servers, or internal APIs; instead, use global networking for these components. Even within your private Bnode network, you should implement authentication between services.Supported data centers
Global networking is available in these 17 data centers worldwide:| Region ID | Geographic location |
|---|---|
| CA-MTL-3 | Canada |
| EU-CZ-1 | Czech Republic |
| EU-FR-1 | France |
| EU-NL-1 | Netherlands |
| EU-RO-1 | Romania |
| EU-SE-1 | Sweden |
| EUR-IS-2 | Iceland |
| OC-AU-1 | Australia |
| US-CA-2 | California |
| US-GA-1 | Georgia |
| US-GA-2 | Georgia |
| US-IL-1 | Illinois |
| US-KS-2 | Kansas |
| US-NC-1 | North Carolina |
| US-TX-3 | Texas |
| US-TX-4 | Texas |
| US-WA-1 | Washington |
- Geographic proximity for lower latency
- Compliance requirements for data residency
- Availability of specific GPU types
Next steps
With global networking configured, explore these related features:- Expose ports to make specific services publicly accessible
- Set up network volumes for shared persistent storage.
- Set up SSH access for secure Bnode management.