![Klaus K.](/assets/transparent-ad5be28fbcd25b7b08d2cebe1d957125437fb5407d75ee717965ad22c8808791.gif "Klaus K.")
KK

Klaus K.

Senior Software Engineer

Mid-Market (51-1000 emp.)

10/28/2025

"Effortless Feature Flagging with Outstanding Support and Value"

4.5/5

What do you like best about DevCycle?

It is extremely easy to use and implement. Anyone can easily find the whats, hows, and whys on their platform and feature flagging approaches from their docs. On top of all that, they are delivering much more than what we needed from a feature flag solution, and for a very small price. We use their product every day and it made our products so much quicker and safer. Now we can even explore doing multiple kinds of beta tests and not worry about unfinished code reaching our customers. Last but not least, whenever we had an question or issue, they were very quick to respond. Review collected by and hosted on G2.com.

What do you dislike about DevCycle?

That the company it is somewhat new. This means it doesn't have all the features others might have. That said, it is not something we miss, and they are quick to add new features and improve existing ones.

The truly worst part that I had to deal with them was a piece of software that is in beta. We had an initial trouble setting it up with OpenFeature, but it was just the initial setup. After that it went smoothly. Review collected by and hosted on G2.com.

What problems is DevCycle solving and how is that benefiting you?

Since the implementation is so easy, both on the code and the platform, we are doing way more Alphas and Betas than before. This enables us to have a code that is much more reliable before it reaches the users, and when it reaches, we can gather feedback from a select group before making it available to all. Another point is that this gave the Product team access to control those access. So now they don't need to create tickets to organize releases if they want. Lastly, we don't need to worry about release times as much. We can deploy the code while hidden from everyone, and when it is safe, we can turn the feature flag or even schedule when we want that. No more worrying about broken code that needs to be released.

Before we could do some of that, but our in house solutions were much more code dependent. So that means that to give/remove access to someone in a Beta needed a deploy. Not only it was a slower process, which made us do less Alphas and Betas, but it was way riskier. Review collected by and hosted on G2.com.

Show More

Current UserValidated ReviewerIncentivizedSource: Seller invite

See what 37 reviewers think of DevCycle

4.5 out of 5 · Verified reviews from real users

[
Read all reviews
](https://www.g2.com/products/devcycle/reviews)