Csilla Kisfaludi

The feature flagging and experimentation space is heating up fast. OpenAI’s acquisition of Statsig shows just how important feature flag management has become and signals that the industry is moving toward AI-assisted, data-driven systems that optimize every release automatically.

This isn’t just another headline in the AI news cycle. It’s a sign of where software delivery is heading: toward AI-assisted, data-heavy development workflows where every release is measured, analyzed, and optimized.

For some teams, that’s the dream. For others, it’s just another layer of complexity standing between them and shipping code.

We've been working on some updates to make the ConfigCat dashboard easier and more enjoyable for managing your feature flags. Let's take a quick look at these new features.

We'd like to share the story of how we successfully rolled out Config V2, the latest and most advanced version of ConfigCat. Let us take you behind the scenes and show you how we used our own tool to achieve a smooth and gradual rollout. Join us as we explain the steps we took to launch Config V2 and demonstrate how we "eat our own dog cat food".

When we designed ConfigCat, our main purpose was to create an architecture that is scalable and resilient to short interruptions, so you don't have to worry about latency, service outages, and unwanted glitches in the system.

Nowadays, almost each and every business uses some sort of web application, so cyberattacks are becoming a daily struggle for huge enterprises as well as for small businesses. It’s not enough for programmers to build an application that looks great and works smoothly. Many consumers are getting aware of the need for security in the applications they are using.

As ConfigCat is a Software as a Service business with applications running in the cloud, we take security as seriously as reliability. Here are the security measures we take to ensure that we deliver a secure application.