RBMSoft has released Vexillo, a self-hosted feature flag management platform that gives engineering teams direct control over how and when features reach end users — without requiring a redeployment each time.
The release addresses a gap that product and engineering teams have long had to work around. Code delivery and feature visibility were always tightly coupled and it made every release decision stem from deployment decisions. Vexillo separates the two, letting teams ship code independently of when a feature actually goes live.
The Problem Vexillo Was Built to Solve
Most software teams today deploy continuously. Features go into builds, builds move through pipelines, and code reaches production on a schedule shaped by CI/CD workflows rather than business readiness. The friction appears when a feature is in production but the team is not yet ready to release it to the customers, to a specific segment, or at all.
Without a feature flagging system in place, the workarounds are costly. Teams hardcode visibility checks that accumulate as technical debt. Configuration changes get pushed through pipelines meant for code. Rollbacks require new deployments rather than a toggle. And when something breaks in production, the path to reversal runs through the same bottleneck as the original release.
Vexillo addresses this by placing a control layer between the code and the customer. Features can be shipped into production and held behind a flag until the team chooses to activate them. When that moment arrives, or when something needs to be pulled back immediately, the change happens at the flag level.
What Vexillo Delivers
Vexillo feature flag management tool operates as a self-hosted platform, meaning it runs inside the infrastructure the engineering team already controls. There is no SaaS dependency, no data leaving the organization’s environment, and no third-party service sitting between the flag state and the application.
For teams with strict data governance requirements or security constraints, this is a meaningful distinction from cloud-hosted alternatives.
The platform covers the core requirements a modern engineering team encounters when managing feature releases at scale.
Instant flag toggling. Features can be enabled or disabled directly from the Vexillo dashboard without touching the application. A staged rollout, an internal preview, a production toggle, or a fast rollback — all happen at the dashboard level. There is no need for redeployment.
Environment-level separation. Vexillo manages flags in the context of specific environments, so a feature active in staging can remain hidden in production. Teams can validate behavior in lower environments before activating anything for end users, without the risk of a misconfigured flag bleeding across boundaries.
Real-time flag propagation. When a flag changes, connected clients receive the update without polling or page reloads. The platform pushes changes to applications as they happen, which matters most when a team is reacting to a live incident or running a time-sensitive launch.
React SDK. Vexillo includes a React SDK built around a useFlag() hook, which lets developers manage feature visibility directly inside components. The SDK supports client-side applications, Next.js App Router, Node.js server-side rendering, fallback behavior, runtime overrides, testing utilities, and error handling.
Role-based access control and multi-organization management. Teams can manage permissions at the member and organization level, keeping flag operations appropriately scoped. For organizations running multiple teams or products on the same platform, multi-organization support allows them to maintain isolation without separate instances.
Why Self-Hosted Matters
The majority of established feature flagging services operate as managed cloud platforms. For many teams, that model is acceptable. For others, it introduces constraints that conflict with existing infrastructure decisions, compliance obligations, or cost structures.
A self-hosted deployment means the platform runs on the team’s own servers or cloud environment. Flag state, user data, and audit logs never leave that environment. There is no per-seat pricing tied to a third-party vendor, and no dependency on external uptime. The team controls the deployment, the updates, and the data.
This is the model RBMSoft has built Vexillo around. The platform is designed to be deployed inside an organization’s existing cloud setup, running alongside the services it manages rather than outside them.
Avdhut Nate, Delivery Head at RBMSoft, explained the reasoning behind the product’s direction:
“Engineering teams often get to production and then realize they have no clean way to control what the user sees. They’re patching it with config hacks or coordinating releases manually. Vexillo gives teams a proper separation between deployment and release, hosted inside infrastructure they own. That’s the piece that was missing for a lot of the teams we work with.”
— Avdhut Nate, Delivery Head, RBMSoft
The Release Control Gap in Product Engineering
Feature flag management has been a standard practice in mature engineering organizations for years. Companies like Meta, Google, and Netflix have long used internal flagging systems to control rollouts, run experiments, and separate code delivery from feature availability.
What has changed is that the need for this capability has moved down to mid-market and growth-stage engineering teams, many of whom do not have the resources to build internal tooling and prefer not to route flag operations through a third-party platform.
The tradeoff for teams evaluating self-hosted options has historically been implementation complexity — standing up a flag management system, building a dashboard, writing SDK support, and maintaining the whole stack. Vexillo’s position in the market is to package that capability as a ready-to-deploy platform rather than a build-it-yourself framework.
The platform includes a centralized flag dashboard for managing flags, environments, organizations, and members, alongside the SDK and real-time propagation layer that flag management requires at the application level.
Who Vexillo Is For
Vexillo is built for engineering teams that ship features continuously and need release control that matches that pace. The platform fits teams running React-based frontends, teams managing multiple deployment environments, and organizations that want flag operations inside their own infrastructure rather than on a third-party service.
The self-hosted model also makes Vexillo relevant to teams with compliance requirements — financial services, healthcare, and enterprise software contexts where data sovereignty governs tooling decisions. Flag state and associated metadata stay within the organization’s environment by design.
RBMSoft positions Vexillo as an accelerator rather than a custom build: a platform that provides production-ready feature flag management out of the box, configured to fit existing infrastructure rather than requiring teams to redesign around it.
Availability
Vexillo is available now. The platform includes the feature flag dashboard, environment-level management, real-time flag propagation, the React SDK, role-based access control, and multi-organization support. Teams can request a demo or access additional technical documentation through the RBMSoft website.
For engineering teams that have been managing feature releases through workarounds — config changes, hardcoded checks, or environment-specific branches — Vexillo offers a path to proper release control without adding a new SaaS dependency to the stack.
RBMSoft is a digital transformation and product engineering company specializing in retail and ecommerce technology. The company works with mid-market to enterprise clients including Big Lots, DSW, PetMeds, and Mills Fleet Farm, delivering platform modernization, AI integration, and product engineering services.
Media info:
Contact Person Name: RBMSoft
Company Name: RBMSoft
Website: https://rbmsoft.com/
Email: info@rbmsoft.com
Address: 717 Bonita Avenue Pleasanton, CA 94566 United States
