Features

HTTP Relay provides communication service between HTTP clients. If you are looking for a solution similar to WebRTC but simple to use and supported by all web browsers and HTTP clients, you are in the right place.

Concept

Peers exchange data by requesting the same URL.

https://demo.httprelay.io/<method>/<channel>

• <method> - communication method (sync, link, mcast, proxy)
• <channel> - unique channel name (can be random character string known just by peers)

Example: https://demo.httprelay.io/link/mysecretchan123

Use case

HTTP Relay is the most useful in cases when:

• Service/peers has no public IP address or it is dynamic

• Ports can’t be open because of the security or technical reasons

• Application can’t be built as an HTTP server

• Peers are behind HTTP Proxy server

Run your application workers as clients using proxy communication method

• No need for configuration when adding/removing

• No need for real IP address or open port

• Easy to manage and integrate with your reverse proxy

CI/CD deployment hooks

• No need to open ports

• Better security

Serve web application online from your browser

• An application can be packed to a single HTML file

• “Server-side” can have UI

IoT

• Track

• Control

• Update

HTTP Relay v.s. WebRTC

WebRTC is designed to provide streaming capabilities. HTTP Relay is designed to send messages and transfer data between peers using standard HTTP requests.

Communication methods