How TownSq Uses Feature Flags to Control Releases Across Web, Mobile, and Backend

Feature flag management that separates deployment from release across a platform serving millions of community members

TownSq provides HOA software and community management tools across web and mobile applications, connecting homeowners, board members, and community managers in one platform.

As the company grew and started releasing more complex features, including payment-related functionality, it needed a better way to control how new functionality moved from deployment to customer release.

With ConfigCat feature flags, TownSq now manages feature releases separately from deployments. The team can give selected customers early access, coordinate functionality across web, mobile, and backend applications, and safely validate scenarios that need to run in production.

Your Cat-Scan Summary

Overview

Industry

Industry

HOA and community management

Company Size

Company Size

201-500 employees

Using ConfigCat Since

Using ConfigCat Since

2024

Use Case

Use Case

Customer targeting, beta releases, production testing, cross-stack feature control

Key Wins

Key Wins

Separation of deployment and release, controlled production testing, customer-specific rollouts, clear visibility across environments

Who is behind the flag?

About TownSq

TownSq began in 2013 under the name SocialCondo. Today, it provides technology for HOAs (Homeowner Associations) covering a wide range of everyday community management needs, from homeowner communication to HOA financial management.

Its platform is available across web and mobile, and connects homeowners, board members, and community managers in one ecosystem. TownSq focuses strongly on usability, with an intuitive interface, robust communication tools, and streamlined workflows for key community management processes, including violations and architectural reviews.

The platform already operates at significant scale, with more than 2.7 million managed units, 3.5 million registered users, and 2.6 million logged users across the TownSq ecosystem.

Looking ahead, TownSq aims to expand its market presence through organic growth across its product portfolio, deepen customer engagement, and pursue its ambition of becoming the largest player in its industry.

TownSq Success Story Cover

The Purr-fect Stack

Using Feature Flags Across Web, Mobile, and Backend

TownSq has an engineering organization of around 120 people, working across frontend, mobile, and backend applications.

Its core technology stack includes:

  • Angular for web applications
  • Kotlin and Swift for mobile applications
  • Java with Spring Boot on the backend

ConfigCat is used across frontend, mobile, and backend applications. On the frontend and mobile side, TownSq mainly uses feature flags to control releases. On the backend, flags are used more selectively, primarily when server-side behavior needs to stay aligned with the frontend.

Because ConfigCat supports a broad range of client-side and server-side SDKs, TownSq can apply one feature management approach across different parts of its technology stack rather than solving release control separately in each application.

Before ConfigCat Walked In

The Challenge: Manual Feature Flags Couldn't Keep Up With More Complex Releases

Before adopting ConfigCat, TownSq already had its own approach to feature flags, but managing them required changes inside the applications themselves rather than using a dedicated feature flag management layer.

“In the past we managed feature flags manually in our systems; for example, we had to update a config file in the project to enable a feature.”

The process was workable when release requirements were relatively simple. As TownSq's product grew, however, the team increasingly needed to make release decisions independently from the application configuration itself.

They needed greater flexibility in how new functionality reached customers. This included the ability to:

  • release features to selected clients,
  • coordinate releases across web, mobile, and backend applications,
  • run tests that required production infrastructure,
  • manage beta access without tying every change in availability to another deployment.

The need for finer release control became more important as TownSq started shipping more complex functionality, including payment-related features.

The manual setup was no longer a good fit for these release scenarios. TownSq needed a dedicated feature flag management solution that could support more complex rollouts without adding unnecessary operational overhead.

How the Cat Saved the Day

The Solution: Separating Feature Deployment from Feature Release

TownSq has now been using ConfigCat in production for around two years.

The biggest shift was in how the team could structure a release. Code could move through the deployment process while feature availability remained independently controlled. With ConfigCat, functionality can be deployed behind a feature flag and activated separately when the team is ready.

Engineering typically creates and manages the flags, while the product team works closely with engineering to decide what should be released and which users should be included in a beta. That gives the two teams a shared release mechanism without making product availability dependent on another code change.

This distinction matters for TownSq because new functionality can involve several applications at once and may also depend on external systems that are not fully available in lower environments.

Sharing Release Control Between Engineering and Product

Feature flag management at TownSq is not owned by one team in isolation. Engineering is generally responsible for creating and managing the flags, while product and engineering work together to decide what should be released and which users should be part of the beta.

Engineering can focus on getting that code into the right environment, and product and engineering can decide separately when the feature should reach customers.

The Cat in Action

How TownSq Uses ConfigCat in Production

TownSq currently uses Targeting Rules rather than percentage-based rollouts. Those rules support several parts of its release process giving selected clients early access to validating functionality that can only be tested properly in production.

Releasing Features to Specific Customers

Not every TownSq feature needs to become available to the entire customer base at once. Targeting rules allow the team to make functionality available to a defined set of clients during a beta or early release phase. Access can then be expanded later without changing the application code or preparing another build.

This gives TownSq a practical way to introduce new functionality gradually while keeping the release audience under control.

Running Controlled Tests in Production

Some TownSq integrations with banks cannot be fully tested in lower environments. That creates an unusual release requirement: the real production environment is sometimes necessary for validation, even though the functionality is not yet ready for the full customer base.

“Since we have integrations with banks, sometimes we can't run a test in our lower environments and those tests need to run in production; ConfigCat helps us control who can use the feature during that phase.”

Targeting solves that problem by limiting access to the intended test audience. The functionality can run in the real production environment with access limited to the intended test audience. Everyone else continues using the existing experience until the team is ready to widen the rollout.

Coordinating Web, Mobile, and Backend Releases

A TownSq feature can span more than one application. A new experience on the web or mobile frontend may depend on corresponding backend behavior, so the different layers need to remain aligned during rollout.

Using ConfigCat across frontend, mobile, and backend applications gives the team a shared mechanism for controlling that availability. Backend feature flags are used selectively where server-side behavior needs to stay synchronized with what users see in the client applications.

For a stack that includes Angular, Kotlin, Swift, and Java, this provides a consistent approach to feature delivery even when the underlying applications are different.

Why They Picked the Cat

Why TownSq Chose ConfigCat

TownSq evaluated LaunchDarkly during its selection process. The team needed a feature flag platform that could handle its release requirements without adding more complexity than the problem required.

“We evaluated LaunchDarkly during our selection process. In the end we chose ConfigCat because of the price and the simplicity.”

For TownSq, ConfigCat offered the balance the team was looking for: the feature management capabilities it needed, a straightforward workflow, and pricing that made sense for the organization. Teams evaluating the two platforms can explore the ConfigCat vs. LaunchDarkly comparison for a closer look at targeting, SDK support, environments, pricing, and other feature management capabilities.

From Meow to Wow

Future Outlook: Supporting TownSq's Growth

TownSq plans to continue expanding its product portfolio, deepen customer engagement, and grow its presence in the community management market.

As the product evolves, ConfigCat gives its engineering and product teams a way to control new releases without tying every change in availability to another deployment.

For a platform serving millions of users, that control becomes increasingly valuable: teams can continue shipping code while deciding separately when a feature is ready to reach customers.

Is ConfigCat a Fit for You?

Move Beyond Manually Managed Feature Flags

TownSq moved from manually maintained configuration files to a feature flag management process that gives engineering and product teams separate control over deployment and release.

If your team is facing similar challenges with customer-specific rollouts, multi-application releases, or production-only testing, a dedicated feature flag service can provide the same kind of release control.

Start using ConfigCat to build more flexibility into the path from deployment to release.

Want more? Discover our other success stories!

Inspired by TownSq's story?

Start your own success story with ConfigCat.

Cat with a chat cloud