Loading...
LaunchDarkly charges per Monthly Active User. They have no incentive to help you remove flags. FlagShark does. We only make money when your flag count goes down. Keep LD for targeting and rollout. Use us for cleanup.
FlagShark recognises the LaunchDarkly SDK signatures across all 13 supported languages. Detection is syntax-aware — tree-sitter AST for TypeScript, JavaScript, Go, and Python, precise regex for the rest — so comments and strings rarely trigger false positives.
Custom wrapper around the LD SDK? Define your patterns in .flagshark.yaml and we'll detect those too.
Every stale flag is a live evaluation in your code: a branch that still runs, a wrapper still maintained, a dead path still tested. Flags that are 100% rolled out and serving the same variant to everyone keep generating that evaluation overhead.
LD's dashboard has a "stale flags" panel, but nothing ships a PR to remove the dead code behind it. That's the gap FlagShark fills.
Teams typically remove 30–50% of their LD flags within the first 90 days of using FlagShark — cutting the flag-driven branches, wrappers, and evaluations cluttering their codebase. (Removing flags trims your code and evaluation surface; it doesn't directly change LaunchDarkly's per-user MAU bill.)