ConfigCat

We use ConfigCat to manage feature flags across all our applications, from Native Apps to backend services, in all environments.

We use ConfigCat daily to quickly deploy to production and to be able to roll out our features to our users in a controlled manner. ConfigCat is also used for some operational toggling, giving access to certain features based on the authorized role. Meaning, as an example - our support organization have access to a wider range of features in our system

Currently, feature flags in desktop apps with future expansion towards webapps and mobile in combination with desktop apps. The desktop apps are a combination of WPF and UWP apps using. NET Framework and. NET Core ranging from 4.6 (Framework) to 6.0 (Core). Apps can either be fully on prem or leverage Azure and/or AWS.

We were in need of a decent experimentation tool and, in addition, a tool that also handles feature flagging (since they are very similar). In previous companies I managed, this was often built in-house. Still, in this scenario, we had quite a diversity of platforms between websites, mobile apps, and backend systems that implementing across all those would have been time-consuming. We needed to get something up and running quickly.

We use ConfigCat to separate our deployments from our releases and to manage configuration for our clients. We also use it to de-risk our deployments, especially when there is a performance risk. It makes QA and testing simpler as QA is in charge of what is turned on/off). It has unlimited environments and seats, so we can comprehensively cover all of our many personas within the organization. The ConfigCat team is super helpful and responsive. There are many SDKs available and nice extensions. I am very happy we chose ConfigCat over the competitors.

ConfigCat is very easy to do business with - responsive to feature requests and willing to help us onboard. The abundance of code samples on the site makes sure that we're doing things the right way. We're just starting out our journey with the product, but the model lines up very well with how we structure our products, projects, and teams.

The ConfigCat is the best approach for us because it allows changing configuration without deploying a new version of code. Also, it allows setting the percentage of the user that comes to a new version of code, which is really perfect for testing a new feature. Very friendly support, that are always ready to help you.

There are quite a few solutions around for feature flags, ConfigCat was the best one for us because it had the best license model - you get the most for your money and it was comparable to similar solutions in all of its features as well - so we had the best of both worlds. One highlight for me though was the use of the Jira integration. I queried with the ConfigCat team as I wondered if there were any plans to integrate with the Jira support for feature flag engines that would allow us to search for features via JQL - there weren't but they went ahead and implemented them which was outstanding service.

<div>We use ConfigCat primarily to separate our deployments from feature release.<br></div><div><br></div><div>We also use it to gradually roll out features to specific users or cohorts to evaluate the release, A/B test and make ad-hoc, targeted config changes.</div>

We make use of ConfigCat to test new features in production in a controlled manner, enable the rollout of these new features on a per-tenant basis once testing has been completed and, should the need arise, rollback a feature if an unexpected issue is found.