Relay Proxy

LaunchDarkly Relay Proxy is a lightweight proxy that maintains a single streaming connection to the LaunchDarkly feature flag service and shares that stream…

  • Development
  • Network Services
LaunchDarkly Relay Proxy is a lightweight proxy that maintains a single streaming connection to the LaunchDarkly feature flag service and shares that stream with many clients on your local network or Kubernetes cluster, so each server can read flag updates without opening its own direct connection.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

69/100 Good

Maintained
100last commit 15 days ago
Popular
43134 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
82no serious findings, CI, tests, OpenSSF Scorecard 5.6/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
134
Open issues
25
Last commit
2026-11-06
Latest release
v9.0.0
Activity
rising

Checked 15 days ago - source: GitHub (launchdarkly/ld-relay)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Install with Composer and publish config Run the Composer (a PHP package manager) commands to install the package and publish its configuration file. Without that file in your project, you won't have a place to tell Relay which servers to use. source
  • List each server with an address or command In the published config, give each MCP server either an HTTP URL or a Stdio command (the exact program and arguments to run). If this is missing or wrong, the app can't connect to that server and you'll get transport errors. source
  • Set Stdio timeouts and environment variables For Stdio servers, set a timeout and any environment variables the command needs, such as API keys. This helps the app fail quickly instead of hanging when the command starts too slowly or is missing required settings. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can relay work with a reverse proxy or Cloudflare tunnel?

In one Plex report, a Cloudflare Tunnel and reverse-proxy setup worked for direct domain access, but the user could not connect when relay was disabled.

What does enabling relay do for accessing a server?

A user asks what enabling relay does and how it works for accessing a Plex server. The snippet does not state the exact mechanism.

What deployment and troubleshooting guidance is available for a relay proxy?

The Academy material says it covers deployment recommendations and basic troubleshooting steps for common issues. It also notes what problems the Relay Proxy may solve.

What limitations should be considered before relying on a relay proxy?

The Academy material covers what issues the Relay Proxy will not address. The snippet does not list the specific issues.

Answers sourced from academy.launchdarkly.com, forums.plex.tv, www.reddit.com

Community

Collected 48 days ago - public community threads