ConfigCat

Deploying code doesn’t have to mean releasing a feature. ClimatePartner uses ConfigCat to deploy changes early, test them with selected team members, and roll them out more broadly when they’re ready. The result: safer testing, fewer merge conflicts, and more control over releases. See how they use feature flags across their decarbonisation platform 👇 https://lnkd.in/dMUuNtV8 #FeatureFlags #ContinuousDelivery #DevOps

Two of our most requested features are finally here: Approval Flow and Scheduled Changes 🙌 Many teams told us they wanted more control over Production changes without slowing down everyday feature flag management. They also wanted a simple way to prepare changes in advance and have them go live at the right time. With the new workflow, you can now: - propose feature flag changes for review, - require approval before changes reach selected environments, - schedule changes for a specific date and time, - and keep a controlled bypass option for urgent situations. We wrote more about why we built them and how they can fit into your release workflow here: https://lnkd.in/dZyijEvX

Did you know ConfigCat has a Proxy? If you want more control over how feature flag configuration reaches your applications, the ConfigCat Proxy gives you a self-hosted layer between your apps and ConfigCat. It can: - cache configuration closer to your applications - reduce outbound connections and config downloads - evaluate flags without exposing raw configuration to clients - keep serving the lat cached config if the CDN become temporarily unreachable - support restricted and air-gapped environments And despite the name, it solves a very different problem from the corporate HTTP proxy your network might already use. In our latest article, we explain how both work, when you need each one, and when using the ConfigCat Proxy makes sense for your architecture. 👉 Read the article: https://lnkd.in/dfUzuWnm #FeatureFlags #DevOps #SoftwareArchitecture #ConfigCat

Most of what we build at ConfigCat lives in the cloud. But the cloud isn't quite as weightless as it sounds. Data centres already account for 1.5% of global electricity demand and that number is expected to keep growing. So this summer, we wanted to contribute to something a little more rooted in the physical world. 🌱 ConfigCat adopted 1,500 saplings through the Plant A Tree Project and we’re really happy to support the work they’re doing. It won't cancel out the footprint of the internet and we wouldn't pretend that it does. But putting 1,500 more trees in the ground still feels like a pretty good thing to do. Hopefully, these 1,500 little trees will be around for many years, providing some very welcome shade during the hotter summers ahead. 🌳

A/B testing isn't just about sending 50% of users to version A and 50% to version B. The hard part is designing an experiment you can actually trust. - What should the primary metric be? - Who should be assigned to each variation? - When should someone count as "exposed"? - What happens if the new version improves one metric but makes the product slower? Our latest guide breaks down how feature flags can help you run controlled A/B tests, measure meaningful outcomes, and gradually roll out the winning version afterward. Read the full guide: https://lnkd.in/d-R-u87u #ABTesting #FeatureFlags #SoftwareDevelopment

What happens to your feature flags when the network goes down? With ConfigCat, flag evaluations continue locally using the latest valid configuration. When connectivity returns, the SDK retrieves the newest version without requiring an application restart or redeployment. Our new article explains how this works, what happens when no cached configuration is available and how to test your setup properly. Read more: https://lnkd.in/dFzXGa_G #FeatureFlags #SoftwareDevelopment #Reliability

In a multi-tenant SaaS product, you may need to release a feature to one customer without exposing it to everyone else. Feature flags make that possible without a separate deployment. Our latest guide covers three ways to target features by tenant in ConfigCat: - Custom attributes for simple, lightweight rules - Segments for reusable tenant groups - Separate environments for independently managed configurations The right choice depends on how much isolation and flexibility each tenant needs. Read the full guide: https://lnkd.in/dkMzy94W #FeatureFlags #SaaS #MultiTenancy #SoftwareDevelopment #DevOps

Building your own feature flag system can seem simple: add a boolean, store it somewhere, and move on. Then come gradual rollouts, targeting, permissions, audit logs, multiple SDKs, and the awkward question of who will maintain it all. At some point, the small internal tool becomes shared release infrastructure. Our latest article explores the real costs and trade-offs of building, self-hosting, or buying a feature flag solution, including the cases where building your own is still the right call. Read it here: https://lnkd.in/djhh__mv #FeatureFlags #SoftwareEngineering #DevOps #BuildVsBuy

Not sure which ConfigCat plan fits your application? Our new guide shows you how to estimate configuration downloads across backend, web, and mobile, so you can choose the right plan without guesswork. Read it here: https://lnkd.in/dSPVJeqh #FeatureFlags #DevOps #ConfigCat

Feature flags are useful. Feature flags that also check if a customer is actually ready? Even better. MyCashflow combines ConfigCat targeting with its own pre-tenant migration state, so merchants only get a feature when both the rollout rules and their data say: go. The result: safer launches, fewer release-day surprises, and no need to unleash every change on every merchant at once. Read the full story: https://lnkd.in/dkQCvY5Z #FeatureFlags #SaaS #Ecommerce #SoftwareDevelopment