Item: ConfigCat
Rating: 10
Author: Paul Witherspoon

Overall Satisfaction with ConfigCat

Use Cases and Deployment Scope

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.

Pros and Cons

Pros

Feature flagging(!!)
Environment Set up
Support
High performance at scale

Cons

Could use a React SDK
Having the Pro tier be more usable for normal Saas organizations by offering more environments.

Most Important Features

Feature Flagging
Price
Flexibility

Return on Investment

Faster, more frequent delivery to customers
Faster ROI
Better Quality and control of our software
Better iteration and product development - fits very well with agile methodologies

Alternatives Considered

LaunchDarkly

ConfigCat was cheaper and the support is better.

Key Insights

Do you think ConfigCat delivers good value for the price?

Yes

Are you happy with ConfigCat's feature set?

Yes

Did ConfigCat live up to sales and marketing promises?

Yes

Did implementation of ConfigCat go as expected?

Yes

Would you buy ConfigCat again?

Yes

Likelihood to Recommend

We use this all across our product to allow us to be very agile and to decouple and de-risk our deployments from releases. It is excellent at identifying stale flags (called Zombie Flags in ConfigCat) and shows every place in the code they are used for safer and easier removal.

Comments

Please log in to join the conversation

Gergely Sinka
commented 3 years ago
Hi Paul! Thanks for your review. :) The React SDK was requested by others well. Good news, we just published an alpha to npmjs. We'll wait for some feedback and then publish a stable version. How many environments do you feel would be reasonable in the Pro plan? Cheers ;)

Powerful, simple feature flagging