5 posts tagged with "pricing"

Outages happen. Even the best engineering teams and the most reliable infrastructure eventually run into network failures, service disruptions, or unexpected connectivity problems.

The real question is not whether a platform will ever experience an incident. It is what happens to your application when it does.

A feature flag service is often part of the path used to manage releases, disable problematic functionality, and respond to production issues. The last thing you want during an incident is for the feature flag system itself to make your application unavailable.

ConfigCat SDKs are designed to avoid that problem. They evaluate feature flags locally, keep using the latest valid configuration when refresh requests fail, and retrieve updates once connectivity returns. Your application does not need to be restarted or redeployed.

Let's look at how this fault-tolerance architecture works.

Local Evaluation: The Foundation of Fault Tolerance​

When you create feature flags and targeting rules in ConfigCat, they are distributed to SDKs through a static configuration file called config.json.

The ConfigCat SDK downloads and caches this configuration, then evaluates flags inside the application process. It does not contact ConfigCat every time your code checks a flag.

This distinction is important. Once the configuration has been downloaded, the SDK can evaluate flags locally using the cached targeting rules and rollout settings. Feature evaluations remain fast, and your application does not depend on a constant connection to ConfigCat for every decision it makes.

The network is only needed when the SDK checks for an updated configuration. If a refresh request fails, the SDK can continue evaluating flags using the version it already has.

This local evaluation model is a central part of the ConfigCat architecture and one of the reasons the SDKs can remain both fast and resilient.

If you are researching ConfigCat pricing or comparing it to alternatives like LaunchDarkly, you are likely trying to answer one simple question:

Which plan do we actually need?

ConfigCat pricing mainly depends on how many times your applications download their feature flags configuration per month, with larger plans allowing higher usage. While most of our users find ConfigCat pricing super simple, we have learned that for some, it is difficult to estimate their usage.

This guide shows you exactly how to estimate your usage and choose the right plan without guesswork.

Change, while sometimes challenging, often paves the way for growth and improvement. In light of this, and with our ongoing commitment to providing our users with the best possible experience, we are writing to announce an important shift in our pricing policy.

Our goal at ConfigCat has always been to balance quality service with sustainable pricing. In light of recent developments, we have had to make some adjustments to our pricing policy to accommodate the current market conditions and ensure that we continue to offer competitive and transparent pricing to our users.

The main idea about our pricing is that our prices are fixed, deterministic and there are no hidden fees. Also we offer a forever free plan without requiring any commitment or credit card information. All features are available in all plans - even the free - helping the evaluation process of our customers.

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.