Satisfying the feature request of our customers from the mobile app development industry, ConfigCat now supports semantic version (SemVer) based user targeting. Typical use case where app builders wish to enable or disable features based on the iOS or Android version on the device their app is running on. For example deciding if 2.3.40 is less than or equals 2.30.4 sometimes not that straightforward by only using the traditional < > = comparators.

Show us your most innovative idea in using feature flags with ConfigCat, and we’ll send you a pack of gifts including your choice of video or music streaming worth $100, or books worth $150 + a pack of ConfigCat and GitHub swag + a commercial ConfigCat subscription.

We'd like to make ConfigCat available for as many users as possible. Our SDKs are available in multiple languages. But still lots of our users missed Ruby support in ConfigCat:

• Does configcat have Ruby sdk??
• So I am sad you don’t have a Ruby client I can see.
• Are you planning to support Ruby?

The Ruby SDK​

Finally we decided to create a standalone Ruby SDK.
Ruby is an interpreted language. It's very similar to Python and we already have an SDK written in Python. Taking advantage of this, the first idea was that we simply convert our Python code to Ruby and everything will be just fine.

TL;DR​

If you're a software reseller you are allowed to buy a ConfigCat subscription for your client. You are allowed to resell one subscription to one client only. Of course, you are allowed to resell more subscriptions to the same client.

Here is how to do it.

What is 2FA?​

2FA is a way of granting access to users only after presenting two separate pieces of evidence (factors). One of these factors is usually a password which the user should know and the other factor something they have or even something they are. This way you can be sure that only knowing your password won't be enough for an attacker to gain access to your account.

How does 2FA work in ConfigCat?​

In our case the first factor is password you use to login to ConfigCat Dashboard. The second factor is a 6-digit number generated via an Authenticator App.

Students should have access to the highest-quality education available. So we partnered with @GitHubEducation and joined the GitHub Student Developer Pack.

Feature flag services are getting popular, but...​

As feature flags are getting popular, an ever-growing number of developers are facing the challenges associated with them.

No matter if you implement your own feature flag library, or choose a hosted feature flag service like ConfigCat, chances are high you want to use your feature flags in your frontend and in your backend services as well.

If your feature flags can be toggled on a central feature flag dashboard, such as

"Thank you guys, you rock."​

We love to get emails like the one above. And sometimes we do. 😃 Actually, more often than I've ever dared to imagine.

Part of the reason our users love us (well, when they do) are those million little tweaks we do to our feature flag service on a daily basis.

Normally we don't share those little tweaks and updates

Our architecture, stacks and why did we choose them. A recipe for SaaS startups for an affordable, scalable and high-performing system that scales well.

ConfigCat is using ConfigCat as a feature flag and configuration management service. Here is how and why.​