15 ms·

Thanks again; glad to shed some light :) I totally get you; we're struggling to find the correct wording. As an engineer, I also bump into the "gradual (tempor

• satyrnein 4y ago
  For me, it's that you described it as a LaunchDarkly competitor, which is mainly that "rollout" use case. It makes me expect the features they have, like alerts that a flag is serving the "launched" variation to everyone, and can be ripped out, or code search to see if any references to a flag remain. I gather you're probably not doing that stuff? That said, I have LaunchDarkly for feature rollout, an ACL layer for clients to control their own team's permissions, and then custom code to enable features based on a client's package plan. It feels like a lot of conceptual overlap, and a unified solution would be nice.
  • nirga 4y ago
    Yes that’s our long term goal. I don’t like having to adapt 4 different tools to do things which are quite similar.