As a solo developer or a small team, we don't want to use fancy branching strategies or highly complex CI and staging environments. Still, we want to be able to deliver new features to my users with confidence. That is what I was thinking a lot of times back in the days when I developed apps for mobile phones.

FeatureNinjas serves feature flags from within GitHub repositories. Push changes early onto your main branch and use a flag to enable those changes only for you. When you have finished all the work, start with a rollout. If you work in a team, enable those features first to your colleagues. Then, do a gradual rollout to your users.

In contrast to other feature flagging services, FeatureNinjas does not provide a UI. Flags are created and managed using Json in your GitHub repositories. FeatureNinjas will pick up those Json files and serve the flags through a simple API whenever you push changes. Define gradual rollouts, conditions, variables, and more fully in Json. We evaluate flags on our servers. There is no need to include any client library. Therefore, FeatureNinjas will work with any programming language, framework, or tool that supports HTTPS.

FeatureNinjas is a GitHub app, which is why it has deep integration into GitHub. It is free now and will cost 15$ per month for organizational accounts starting next year.

We're just getting started and are looking for feedback and early adopters.

I’m confused. How is this better (Or, not worse than if you consider the additional overhead of a network call for every incoming request) than having your app just read the same json file from the deployed code?