Why a network needs several transports
The same connection between two nodes can behave very differently depending on the network. QUIC may work well in one place, UDP may be blocked in another so only HTTPS-like traffic gets through, and WireGuard may be the right choice elsewhere. Picking one protocol in advance means living with its limits, or switching by hand when something stops working.
CloudBridge takes a different approach: nodes support several transports and choose between them based on the state of the channel.
Five transports
The platform currently supports QUIC, MASQUE, WebRTC, WireGuard and AmneziaWG. Each suits a different situation: QUIC recovers quickly from packet loss, MASQUE looks like ordinary HTTP/3 to the network, WebRTC traverses NAT well, WireGuard is simple and fast, and AmneziaWG adds obfuscation for networks with DPI.
The hard part is not supporting all five. It is switching between them so that the application does not notice.
Measurement and switching
A node continuously measures latency, jitter and channel availability. When the current transport starts to degrade, the session moves to another transport instead of dropping and reconnecting.
This is the difference between a reactive and a proactive design: you can notice degradation early rather than waiting for the channel to fail completely.
Points of presence
The network runs through three points of presence: Moscow, Frankfurt and Amsterdam. Several points give fault tolerance and let the network pick a route close to the client. For Russian and European clients this keeps latency low in a way a single location cannot.
Predictive routing
In the project’s research lab, ai-routing-lab, the experiment goes further: models are trained on historical channel metrics (RTT, packet loss, jitter, load) and try to predict the best route before the current one degrades. This is still research, not the basis of production, but it shows the direction: from switching after a failure to switching on a forecast.
The lab’s tests: 196 unit tests and 71.73% coverage. CI runs the tests on Python 3.11 and 3.12 and checks dependencies with Safety and Bandit.
What is open
The Go implementation of MASQUE VPN is open source: github.com/cloudbridge-research/masque-vpn. It is a learning implementation, but a working one: CONNECT-IP over QUIC/HTTP/3 with a REST API for managing tunnels.
More about the platform is on 2gc.dev.