One Codebase. Many Products.
Multi-Variant Applications
Stop forking repos and drowning in if/else logic. Build your software once and use ConfigBee's runtime controls to power infinite variants, delivering different features, configurations, and experiences for different customers, regions, or communities. No redeployments. No code forks.
Start Building
Customization scales faster than code. Multi-Variant Applications fix that.
As products grow, supporting different customers, regions, and enterprise clients usually means forking codebases, maintaining multiple deployments, or drowning in if/else logic. Multi-Variant Applications are a different approach: build once, configure behavior everywhere. ConfigBee is the variant management layer that makes it possible.
The Three Layers of a Multi-Variant Application
A clean architecture for infinite customization
Generic Codebase
Developers build features controlled by flags and driven by configurations. The code asks if a feature is enabled rather than asking which customer is requesting it. This keeps your codebase clean, reusable, and easy to evolve.
Build-Time Variants
Define deployment-level variants from the same repo, including App Store builds, region-specific deployments, enterprise distributions, and demo versions. Each variant operates with predefined features and configurations.
Runtime Variants
At runtime, the same deployed app behaves differently based on domain, user group, account, or geography. Multiple branded experiences. No redeploys. No code changes. Just configuration.
Real-World Example
A matrimony platform serving 50 communities from one codebase
Before: The old way
- ✗ Separate repo per community
- ✗ Bug fixes ported to 50 places
- ✗ Feature parity issues across variants
- ✗ Only engineers can launch new communities
- ✗ Weeks to launch a new community portal
After: With ConfigBee
- ✓ One repo, one deployment
- ✓ Fix once, all communities benefit
- ✓ Each community has its own look, features, domain
- ✓ Product team launches new communities
- ✓ New community live in minutes
Why Multi-Variant Applications Win
One Codebase, Infinite Products
Faster Go-To-Market
Non-Engineers Can Contribute
Safer Changes
Lower Cost, Lower Risk
Scale Without Complexity
ConfigBee as Your Variant Management Layer
The platform between your code and your users
Managing variants at scale requires strong configuration schemas, contextual targeting, real-time updates, clear ownership, and safe rollbacks. ConfigBee provides all of this by sitting directly between your code and your users as the variant management layer.
Feature flags per variant
Each variant can have its own set of enabled features controlled independently without any code changes.
Contextual targeting
Target by user, account, organization, domain, or any custom attribute. The same deployment, infinite experiences.
Real-time updates
Change a variant's behavior instantly. No redeploy, no cache flush, no user reload required.
Role-based access control
Product, ops, and CS teams can manage their own variants safely without ever touching engineering.
Multi-environment support
Separate dev, staging, and production variants. Test before you ship to users.
Instant rollbacks
Something wrong with a variant? Revert in one click. No incident, no hotfix.
Ready to build your first Multi-Variant Application?
Start with ConfigBee's runtime controls and turn your codebase into a platform that spawns products.
No credit card required • Free forever plan available