What is the problem that you solve that would justify adding a dependency on an external service that shims itself between us and our precious users?
Rolling out features to subsets of users in a controlled fashion... it's just a such damn trivial thing to do.
At scale, a hosted solution might be justified.
After using LD for a year I found it expensive, slow, broken. They were cool and gave me a large credit.
Now I use a self-hosted "microservice" which works at our scale (100s of users).
Feature Flags are only checked on sign in here, so the load on our service is very low.
But is in go, which is "fast" and web-scale, right?
IDK about this product, but split.io has more features and better UI than you could get from a handful of engineers working part-time.
I agree: like error reporting, it's not a hard, unsolvable problem, but it's a problem I had a few times and decided, why reimplement the wheel I could create a helpful open source solution?