releases.shpreview

Environments can now have multiple SDK keys

v8.20.0-rc.1

July 24, 2026Relay ProxyView original ↗
1 featureThis release1 featureNew capabilitiesAI-tallied from the release notes
From the original release noteView original ↗

8.20.0-rc.1 (2026-07-24)

Features

Support for Multiple SDK Keys in Relay Proxy

This release candidate brings multiple SDK keys to the Relay Proxy: a single environment can now have more than one SDK key and more than one mobile key active at the same time.

For more information, check out the recent product update and our developer docs.

What this means

Managing SDK keys is now more flexible. Each LaunchDarkly environment can support multiple SDK keys, giving you the tools to rotate keys without downtime, isolate access across services or teams, and set expiration dates to enforce key rotation policies.

Each key now has its own name, description, and optional expiration date. Fine-grained custom role support means you can control who can view or manage individual keys — down to the key level.

You can manage keys through the updated UI (Settings → Security → SDK Keys) or via API.

Requirements and scope

  • Auto-configured environments only. Concurrent keys arrive through Relay Auto Config (RAC). Environments configured manually (file, environment variables, or TOML) continue to use a single key.
  • SDK keys and mobile keys. Client-side IDs remain single per environment in this release.
  • Analytics events are attributed to the environment's primary SDK key, not to the individual key a request came in on.

Fetched July 25, 2026