Why you should proxy your feature flag service
Today I learned,
using feature flags is amazing. It helps you control features across multiple environments in seconds and even release things slowly. But the nightmare comes when the service gets blocked on the user side. My experience was with Statsig getting blocked at the network level by adblockers, enterprise VPNs, or other filtering tools. Turns out, these tools are starting to treat feature flag requests the same as tracking scripts.
The fix is simple, route the SDK traffic through a proxy on your own domain so it looks like a first-party request. You don’t think about it until it bites you.