Skip to main content
Book a demo

Connect LaunchDarkly to ECA

Give ECA governed access to LaunchDarkly’s 141 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo ECA setup guide

Set up

Add LaunchDarkly to ECA in four steps

Admins approve the server once. Everyone in ECA then gets it through the same governed connection.

  1. 1

    Approve LaunchDarkly in Runlayer

    Add LaunchDarkly from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect ECA to Runlayer

    Users add the Runlayer Plugin to ECA by following Runlayer’s setup guide. ECA reaches LaunchDarkly’s 141 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    ECA setup guide
  3. 3

    Sign in to LaunchDarkly

    An admin adds LaunchDarkly credentials to Runlayer once. They never sit in the client’s configuration.

  4. 4

    Use LaunchDarkly from ECA

    LaunchDarkly’s approved tools appear in ECA. Every call is checked against policy and recorded.

Tools

141 LaunchDarkly tools in ECA

Runlayer policy decides which of these ECA users can call.

  • Apply agentcontrol config approval

    Apply an already-approved AgentControl Config approval request.

  • Apply approval request

    Apply an already-approved flag approval request.

  • Archive flag

    Archive a feature flag (reversible).

  • Check flag rollout complete

    Check whether a feature flag is fully rolled out to a single deterministic variation across all traffic-bearing environments.

  • Check removal readiness

    Detailed safety check before removing a feature flag.

  • Clone agentcontrol config variation

    Clone an existing AgentControl Config variation with selective overrides.

  • Copy flag config

    Copy a flag's targeting configuration from one environment to another.

  • Create agent graph

    Create a new agent graph in a project.

See all 141 LaunchDarkly tools

Control

What Runlayer can see and stop in ECA

Some controls apply to every client at the gateway. Others depend on what ECA exposes to Runlayer.

  • Gateway policy (available)

    Every LaunchDarkly call from ECA passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, ECA as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for ECA yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination