G2

Pranjal E.

Software Engineer

Small-Business (50 or fewer emp.)

9/29/2026

"Safer releases, one customer at a time"

4/5

What do you like best about LaunchDarkly?

The biggest value is shipping risky fixes to production turned off, then turning them on for one customer at a time across our many environments. Rolling back is a toggle, not a redeploy, so we ship faster with less risk. The REST API is excellent. We script almost all flag work and built a daily Slack digest on it to catch stale or partly rolled-out flags. Flags have become our release process, and the ROI shows up in emergency rollbacks we never had to do. Review collected by and hosted on G2.com.

What do you dislike about LaunchDarkly?

Targeting is easy to get wrong. Individual targets are stored apart from rules, and new rules default to the "user" context kind, which can silently match nothing. Stale-flag cleanup is left to us, so we built our own digest. It's also hard to see what flag value a long-running worker actually evaluated. Warnings on rules that can't match and built-in stale-flag tracking would help a lot. Review collected by and hosted on G2.com.

What problems is LaunchDarkly solving and how is that benefiting you?

It keeps a code fix separate from the decision to release it. We merge fixes to production turned off, turn them on for one customer to verify, then roll out everywhere. If something breaks, we turn the flag off instead of redeploying. We ship fixes faster, customer-specific issues can be tested safely in production, and bad releases have a much smaller impact. Review collected by and hosted on G2.com.