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
  • Get started
    • Overview
    • Onboarding
    • Get started
    • Launch Insights
    • LaunchDarkly architecture
    • LaunchDarkly vocabulary
  • AgentControl
    • AgentControl
    • Manage AgentControl
  • Feature flags
    • Create flags
    • Target with flags
    • Flag templates
    • Manage flags
    • Code references
    • Contexts
    • Segments
  • Releases
    • Releasing features with LaunchDarkly
    • Release policies
    • Percentage rollouts
    • Progressive rollouts
    • Guarded rollouts
    • Feature monitoring
    • Release pipelines
    • Engineering insights
    • Release management tools
    • Applications and app versions
    • Change history
    • Restoring previous flag versions
  • Observability
    • Observability
    • Session replay
    • Error monitoring
    • Logs
    • Traces
    • Observability metrics
    • Product analytics events
    • LLM observability
    • Alerts
    • Dashboards
    • Service map
    • Vega for auto-remediation
    • Observability MCP server
    • Search specification
    • Observability settings
    • Observability integrations
  • Experimentation
    • Experimentation
    • Experiment metric types
    • Experiment configuration
    • Managing experiments
    • Analyzing experiments
    • Multi-armed bandits
    • Holdouts
  • Metrics and events
    • Metrics in LaunchDarkly
    • Creating metrics
    • Metric groups
    • Events
    • Autogenerated metrics
  • Warehouse native
    • Warehouse native metrics
    • Setting up external warehouses
    • Creating experiments using warehouse native metrics
  • Infrastructure
    • Connect apps and services to LaunchDarkly
    • LaunchDarkly in China and Pakistan
    • LaunchDarkly in the European Union (EU)
    • LaunchDarkly in federal environments
    • Public IP list
  • Your account
    • Projects
    • Views
    • Environments
    • Tags
    • Teams
    • Members
    • Roles
    • Account security
    • Feature previews
    • Billing and usage
    • Changelog
Sign inTry it free
LogoLogo
On this page
  • Overview
  • The EU version of this docs site
  • Supported features
  • Integrations available in the EU instance
  • EU instance URLs
  • Initialize an SDK for the EU instance
Infrastructure

LaunchDarkly in the European Union (EU)

Was this page helpful?
Previous

LaunchDarkly in federal environments

Next
Built with

Overview

This topic explains how the version of LaunchDarkly that is available on domains residing in the European Union (EU) is different from the version of LaunchDarkly available in the United States. The LaunchDarkly EU instance complies with EU data residency principles, including the protection and confidentiality of EU customer information.

To comply with these data principles, the LaunchDarkly EU instance includes additional controls on its infrastructure and security configurations. These controls allow management of customer data flows that are not available in the US instance of LaunchDarkly. The EU instance resides in the AWS Frankfurt (eu-central-1) region and operates nearly the same as the US instance of LaunchDarkly. Operational monitoring with Datadog and edge delivery/CDN (Fastly) still operate from regions within the United States.

The EU instance only supports net new Enterprise and Guardian plan accounts and LaunchDarkly trials.

The EU version of this docs site

You can view an EU instance-specific version of this documentation site.

The EU version of the docs site is different from the standard version in the following ways:

  • EU instance URLs display with .eu URLs, including within code samples. To learn more, read EU instance URLs.
  • Features and integrations that the EU instance does not support are marked with a warning message. To learn more, read Supported features.

To view the EU instance-specific version of this documentation site, change the site version menu to “EU docs”.

Supported features

The EU instance supports the following features:

  • AgentControl
  • The Billing page
  • Core flagging features through the LaunchDarkly application and API
  • Code references
  • Experimentation, including Snowflake native Experimentation
  • Some flag imports
  • Guarded rollouts
  • The LaunchDarkly Relay Proxy
  • Live events
  • The local MCP server
  • Metrics
  • Most SDKs, except for edge SDKs and the Roku SDK
  • Single sign-on (SSO)
  • Streaming data export

The EU instance does not currently support the following features:

  • Applications and app versions
  • Debugging guarded rollout errors
  • Edge SDKs
  • Inbox notifications for approval requests
  • Launch Insights
  • The hosted MCP server
  • Migration flags
  • The Roku SDK
  • The support chatbot
  • SCIM-based user provisioning for Okta SSO

Integrations available in the EU instance

Integrations connect LaunchDarkly to other systems and move data between them. Only the following connected systems are currently enabled.

The EU instance initially will only support customer requested integrations. Requested integrations are provisioned shortly after each request. The following integrations are enabled:

  • AppDynamics
  • Chronosphere events
  • Crossplane
  • Custom approvals
  • Datadog flag triggers
  • Datadog events
  • DynamoDB segments integration
  • Dynatrace flag triggers
  • Dynatrace events
  • Elastic (ELK) Stack
  • Github Actions
  • Honeycomb flag triggers
  • Honeycomb events
  • IntelliJ IDEA plugin
  • Jira
  • Last9
  • New Relic
  • MS Teams incoming webhooks
  • PagerDuty
  • Redis segments integration
  • ServiceNow approvals
  • Slack incoming webhooks
  • Snowflake Data Export
  • Splunk Observability Cloud
  • Splunk
  • Twilio Segment

EU instance URLs

The EU instance, including the LaunchDarkly application, the instance API, and SDK use the base domain eu.launchdarkly.com in the URL path. If your network uses application or network layer firewalls, you must update them to allow these URLs. If you do not do this, LaunchDarkly will not function properly.

These URLs are:

  • https://app.eu.launchdarkly.com
  • https://clientsdk.eu.launchdarkly.com
  • https://clientstream.eu.launchdarkly.com
  • https://events.eu.launchdarkly.com
  • https://sdk.eu.launchdarkly.com
  • https://stream.eu.launchdarkly.com

To learn how to configure your SDK correctly using these endpoints, read Service endpoint configuration.

Initialize an SDK for the EU instance

You can initialize an SDK for the EU instance using the initialization options for the SDK.

Depending on the SDK, you may need to configure multiple service endpoints in the initialization options. These could include the base and polling endpoint, streaming endpoint, and events endpoint. Server-side SDKs normally require streaming and events settings, not polling. For a list of available service endpoints, read EU instance URLs.

The details of how to set these options differ between SDKs, as LaunchDarkly respects each language’s URI and URL naming conventions and supported services. For this reason, it is critical to reference the documentation for each individual SDK.

Configure your SDK: Service endpoint configuration