For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Sign inTry it free
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
  • SDKs
    • SDK concepts
    • SDK features
    • Client-side SDKs
    • Server-side SDKs
    • AI SDKs
    • Edge SDKs
    • OpenFeature providers
    • Observability SDKs
    • Relay Proxy
      • Determining whether to use the Relay Proxy
        • Relay Proxy use cases
        • Relay Proxy guidelines
      • Relay Proxy Enterprise
      • Implementing the Relay Proxy
      • Versioning policy
Sign inTry it free
LogoLogo
On this page
  • Overview
SDKsRelay Proxy

Determining whether to use the Relay Proxy

Was this page helpful?
Previous

Relay Proxy use cases

Next
Built with

Overview

This category contains topics about how to decide whether to use the Relay Proxy.

We recommend using the Relay Proxy in certain situations. The Relay Proxy is not appropriate for all customer configurations.

You may want to use the Relay Proxy to:

  • reduce costs incurred by cloud providers for outbound network connections
  • improve performance when using many SDK clients on a single host
  • integrate LaunchDarkly in a PHP environment
  • reduce initialization latency in short-lived and serverless environments, or in Function-as-a-Service (FaaS)
  • reduce operational work when creating new projects and environments
  • increase availability in countries with strict network policies
  • reduce redundant database traffic
  • use synced segments or larger list-based segments with server-side SDKs

To learn more, read Relay Proxy use cases.

If you decide the Relay Proxy is appropriate for your use case, you should follow our architectural and caching guidelines. To learn more, read Relay Proxy guidelines.