Beam Updates Orchestrator Gateway Documentation

Beam published updated guidance for orchestrators deploying dedicated Worker Gateway infrastructure instead of using the shared BeamCore gateway. Orchestrators can now customize their communication topology using WebSockets, TCP/UDP, HTTP, relay hubs, or other architectures. Workers continue submitting Proof of Bandwidth directly to BeamCore, while the orchestrator gateway handles worker communication and task assignment. Dedicated gateways are recommended for production deployments.

• •Orchestrators can run custom worker-gateway infrastructure instead of shared BeamCore
• •Topology fully customizable; no enforcement of specific communication architecture
• •Workers still submit PoB directly to BeamCore for verification
• •Dedicated gateways recommended for production deployments