How Scoro Replaced a Homegrown Feature Flag System with ConfigCat

Who is behind the flag?

About Scoro

Founded in 2013, Scoro is a professional services automation platform built for agencies, consultancies, and service businesses seeking full visibility into operations and project profitability.

They're proud to help professional services firms around the globe increase profitability by 20%+, and they're not slowing down. The team is continuously working on delivering more proactive insights and elevating the platform with AI capabilities.

The Purr-fect Stack

Tech Stack & Development Culture

Scoro runs a cloud-based SaaS product powered by PHP, Go, and Node.js. ConfigCat is used primarily on the backend, supporting private and public APIs.

And here's the important part: feature flags are involved from the very first development tasks all the way to production rollout. They're not added at the end, they're part of the workflow.

Feature flags allow engineers to build multiple features simultaneously while controlling when and how those features become visible.

In practice, this means:

• enabling specific features in certain environments during development
• working on multiple features without exposing unfinished functionality
• rolling out features gradually in production
• quickly rolling back changes if something goes wrong

Feature flag management has become a key part of how Scoro delivers software continuously. This approach aligns with modern progressive delivery practices, where new functionality is introduced gradually instead of being released to everyone at once.

Before ConfigCat Walked In

The Challenge: The Limits of Homegrown Feature Flags

Before adopting ConfigCat, Scoro relied on a homegrown feature flag system. At the beginning, their in-house feature flags did the job. But as the platform grew and releases became more complex, the limitations started to appear.

The team needed more flexibility in how features were released. Their internal system couldn't support the targeting and rollout strategies they wanted. They were looking for a feature flag solution that could support:

• wide and narrow rollout rules
• logical targeting instead of manual switching
• a solution that could scale without adding operational overhead
• high availability guarantees

Maintaining their own flag system started to feel less like a competitive advantage and more like maintaining internal infrastructure. Instead of helping the team ship faster, it was slowing them down. Many growing teams eventually reach this point and start evaluating the trade-offs between building their own feature flag system and adopting a managed platform.

How the Cat Saved the Day

The Solution: Moving from Homegrown Flags to a Dedicated Feature Flag Service

Scoro evaluated several feature flag platforms, including LaunchDarkly and Unleash, before selecting ConfigCat. One requirement played a key role in their decision: high availability. Scoro needed a proxy-based solution that could guarantee reliable feature flag delivery across their infrastructure. The ConfigCat Proxy met their requirement and has provided stable operation without incidents since adoption.

The transition began with a full migration.

Once the migration was complete, the team quickly started using ConfigCat across their development lifecycle.

During development, engineers use feature flags to isolate individual features when many features are being worked on at the same time.

In production, ConfigCat enables several important release strategies:

• geographic rollouts to specific customer regions
• percentage-based rollouts for higher-risk features
• controlled feature exposure while monitoring performance
• instant rollback if issues appear

What previously required manual coordination with a homegrown system is now handled through rule-based targeting.

Why They Picked the Cat

How Scoro Uses ConfigCat in Production

For Scoro, the biggest benefit of moving away from homegrown feature flags was gaining flexibility without adding complexity.

ConfigCat allows the team to manage sophisticated rollout strategies while keeping the system simple and reliable. As the team puts it, ConfigCat is a

New engineers joining the team often notice how easy it is to toggle feature flags across different environments. What used to require manual effort in their in-house feature flag system now takes only a few clicks. Sometimes the biggest improvement over a homegrown solution is simply removing unnecessary complexity.

From Meow to Wow

Future Outlook: Smarter Releases and Continuous Innovation

Scoro continues to expand its platform with deeper insights and AI-powered capabilities. With ConfigCat, the engineering team can focus on improving the product instead of maintaining internal tooling.

Feature flags now allow Scoro to innovate faster while maintaining the reliability their customers expect.

Is ConfigCat a Fit for You?

When to Move from Homegrown Feature Flags to a Feature Flag Service

Many teams start with homegrown feature flags. It's a natural solution in the early stages of a product. But as systems grow, in-house feature flag solutions often struggle with:

• rule-based targeting
• gradual rollouts
• global reliability
• operational maintenance

Scoro's story shows how moving from a homegrown feature flag system to a dedicated feature flag service can remove these limitations and help engineering teams release features faster and more safely.

If your team is maintaining a homegrown feature flag system, it might be time to ask whether building infrastructure is still the best use of your engineering time.