ConfigCat's New Pricing Policy

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.

Change in Pricing Policy: Network Traffic Limits

One of the most notable changes in our new pricing policy is the introduction of network traffic limits. We understand this is a new concept for our users, so let us briefly explain.

Network traffic limits refer to an added quota or upper limit to the amount of data transferred between your applications and ConfigCat's Content Delivery Network (CDN) servers. It is the maximum amount of data transfer that is allowed for a particular user or client within a specified period. Just as roads have traffic limits to prevent congestion and ensure smooth flow, networks have traffic limits to maintain optimal performance and prevent the overuse of resources.

This can be understood as a cap or ceiling on the volume of data that can be sent or received from ConfigCat's servers. By introducing network traffic limits, we aim to ensure that our services remain scalable and reliable for all our users. This encompasses the requests made to retrieve feature flag evaluations, configuration settings, and other relevant data.

Factors that mainly influence the Network Traffic:

• Size of the Config JSON: This is affected by the number of feature flags, settings, targeting rules, segments, and the length of their values.
• Number of Clients Connecting to ConfigCat: Each time a client downloads the config JSON, it adds to the overall Network Traffic.
• Frequency of Changes in the Config JSON: The config JSON is cached on the ConfigCat CDN. If there's no change, the CDN responds with a "304 Not Modified" status. However, if there's a change, a "200 OK" response is sent, and the new config JSON is downloaded.

Reason Why? (Cloudflare Taxes ConfigCat Over Generated Traffic)

The primary reason behind this change is the additional costs we incur due to Cloudflare taxing ConfigCat over the generated traffic. ConfigCat utilizes Cloudflare as part of its infrastructure. As a result, managing and monitoring network traffic becomes crucial to ensure that our service remains cost-effective and sustainable. This change will allow us to manage these incurred costs better and continue providing our services at a fair and competitive price.

It is important to note that we have chosen not to add another pricing step but have included network traffic limits as a quota, because the majority of ConfigCat's users do not exceed the standard network traffic quota. Therefore, instead of introducing a new pricing tier, which might complicate the pricing structure and potentially affect a large number of users, ConfigCat has chosen to address this on a case-by-case basis.

Most of our users typically do not exceed this quota, which means most customers won't be affected by this change. Nevertheless, we understand that some users may have concerns, and we are here to address them. If you want to review the network traffic limitations, please refer to our pricing table for detailed information.

The new Pricing Policy's Impact on Users

We understand that any changes to our pricing policy may raise concerns about the functionality of your feature flags. Rest assured, our commitment to delivering high-quality feature flag management services remains unwavering. These pricing adjustments will not disrupt the functionality of your feature flags or configuration management.

We've worked diligently to ensure that the introduction of network traffic limits does not affect the performance or reliability of our services. This approach ensures that only those who require additional resources are addressed without impacting the broader user base. We have thoroughly tested and optimized our infrastructure to handle any increased demand that may arise from these changes. Your feature flags will continue to work seamlessly, and you can rely on ConfigCat to deliver the same high standards you are accustomed to.

If you have any questions or concerns about how these changes may impact your specific use case, please do not hesitate to reach out to our support team, we are here to help with any needed clarification.

Tips to Reduce Monthly Network Traffic

• Delete old feature flags and unused targeting rules.
• Avoid storing excessive data in the comparison value of targeting rules or segments.
• Be mindful of the amount of text in a text setting's value.
• Consider dividing feature flags into multiple configs to reduce the size of each download.

For a more detailed understanding, users can refer to the ConfigCat Docs on Network Traffic and the ConfigCat Calculator to get an estimate of their potential network traffic based on their specific use case.

Conclusion

While change can be daunting, we're often required to adapt to changes, but our primary goal remains to provide exceptional service without compromising on quality or affordability. Introducing network traffic limits to our pricing policy is a strategic move designed with our users' best interests in mind.

We recognize that such adjustments might raise questions. Rest assured, our support team is here to guide you through these changes. Your trust and satisfaction are paramount to us. Please don't hesitate to reach out for any further details on the new pricing policy.

For more updates, you can follow ConfigCat on Facebook, X, LinkedIn, and GitHub.