LaunchDarkly

What Plutus imports

• Flag changes
• Segment changes
• Environment changes

Connecting

Method: Service Access Token

1. In LaunchDarkly, go to Organization settings > Authorization and click Create token.
2. Give the token a name, set its type to service token, and assign it the built-in Reader role. Plutus only reads the audit log, so no write access is needed.
3. Copy the token. LaunchDarkly only shows it once.
4. In Plutus, paste the token into Access Token.
5. If your organization runs on LaunchDarkly’s EU or federal instance, also fill in Instance URL — a token issued on one instance doesn’t work on another. Leave this blank for the standard instance.
6. Optionally, fill in Resource filter with a LaunchDarkly resource specifier (e.g. proj/my-project:env/production:flag/*) to narrow the sync to one project, environment, or flag. Leave it blank to track every project and environment the token can see.
7. Click Save & connect, then Sync now to pull flag rollouts onto your cost charts.

Notes

A flag ramped to 100% moves spend with no deploy, no merged PR and no release — the one cost-moving change your Git and CI event sources cannot see. Only flag, segment and environment changes are overlaid; member invites, token creation and project renames are filtered out. Note that LaunchDarkly gates audit-log retention on its own plan: on Developer and Foundation only the last 30 days of history exist to backfill, so on those plans the timeline fills in going forward rather than reaching back.