Reflex Drives Enterprise Self-Hosted Revenue with Replicated

Overview

‍

Reflex is an AI-powered app builder that makes it fast and intuitive for teams to create full-stack internal applications entirely in Python. As the company began engaging with larger, more security-sensitive customers, it quickly became clear that offering a self-hosted deployment option was not just a competitive advantage. It was a requirement for enterprise adoption.

‍

Before Replicated, Reflex’s on-prem offering was undefined and inconsistent, and something the sales team “danced around.” With Replicated, Reflex launched a production-ready self-hosted workflow in weeks, expanded enterprise contracts, and turned on-prem deals into the foundation of its revenue strategy.

Challenge

‍

When enterprise prospects began asking for self-hosted deployments, Reflex lacked a repeatable path to deliver them.

‍

“Not having on-prem is almost a non-starter for a lot of these Fortune 500 companies,” said Simon Young, Engineer at Reflex. “We need to be able to give them something they can deploy in their own environment, managed by their own admins, with no external communication.

‍

Reflex’s team is small, and Simon was the only person on the team with significant infrastructure experience. Building a self-hosted deployment process from scratch, including packaging, installation tooling, support workflows, and enterprise-grade documentation, looked like a months-long effort.

‍

“We could have done it ourselves, but it would have been a ton of work,” Simon explained. “It probably would have taken me three months, realistically, because I’m the only person who knows infrastructure on the team. Maybe if I had a fully dedicated month with nothing else going on, I could have gotten something out. But it wouldn’t have included all the support bundles and embedded cluster functionality we get with Replicated.”

‍

Without a clear self-hosted story, sales cycles stalled, enterprise deals were harder to close, and the company was leaving meaningful opportunities on the table.

Solution

‍

Reflex selected Replicated to build and deliver its on-prem deployment offering because it provided a complete, enterprise-ready distribution platform with support built in

‍

From the moment the deal was signed, implementation moved quickly. Instead of spending months building tooling, Reflex was able to launch a first working version in weeks. The combination of Replicated’s distribution platform and expert support was critical.

‍

“The support is probably the best decision we made,” Simon said. “It’s above and beyond what most companies I’ve worked with have been able to provide. It was three or four sessions, and I was able to get into a productive cycle of pushing releases and testing locally. That was really the unlock to getting the amazing value out of Replicated.”

‍

That guidance helped Simon and the Reflex team move from an early Helm chart with gaps to a reliable, production-grade release workflow. Replicated’s platform handled packaging and release management, support bundle generation for troubleshooting, CI integration for automated releases, and Embedded Cluster options for non-Kubernetes environments.

‍

Instead of navigating Kubernetes and Helm complexity alone, Simon had expert help refining configuration, validating assumptions, and ensuring Reflex’s self-hosted builds would work in real customer environments.