The Relay Proxy is a lightweight Go application that runs within your infrastructure and handles all streaming connections to the Harness platform. It fetches all of your flag, target, and target group data on startup, caches it, fetches any updates over time, and serves it to your connected downstream SDKs.
To learn more about deploying the relay proxy see Deploy the Relay Proxy.
To read more about use cases and advantages of the Relay Proxy see the Why use the Relay Proxy?.
You can also read more about the use cases, architecture and more in our blog post.
To view the many configuration options available read Configuration.
To view how to securely connect sdks to the Relay Proxy with HTTPS enabled see TLS.
By default the Relay Proxy runs with an In Memory Cache.
To run with persistent storage in redis read Redis.
If you'd like to run the Relay Proxy in airgapped environments or locations with poor internet reliability you can generate offline flag configuration and run the Relay Proxy in a fully offline mode. To learn more read Offline Mode.
For info on horizontal scaling Relay Proxies and a working example see Load Balancing.
If you'd like to build and run the Relay Proxy on Windows see Windows.
For info on the external Harness SaaS endpoints the Relay Proxy communicates with see Outbound Endpoints. For info on the Relay Proxy endpoints your sdks will connect to see Inbound Endpoints.
For help on debugging your Relay Proxy install see Debugging.
See the contribution guide.