Reflex Raises $14M Series A for Custom Enterprise Apps

Selling a company software it can keep gives Reflex a demanding proposition to build around. The San Francisco startup offers customers editable applications, a Python foundation and engineers who can help put those applications to work, leaving the continuing commercial relationship to earn its place alongside code the buyer already controls.

Reflex has raised a $14M Series A led by Standard Capital, with Databricks Ventures, Y Combinator, Lux Capital and Abstract Ventures participating, according to SiliconANGLE's October 29 report. Co-founders Nikhil Rao, CEO, and Alek Petuskey, CTO, are expanding a business whose assignment now includes helping customers choose, build and deploy the software their operations require. The financing supports engineering and sales expansion as the company prepares its Workflows product.

What Reflex's Series A is funding

SiliconANGLE reports that the round brings Reflex's total funding to $19M. The company's own August 2023 seed announcement documents a $5M round led by Lux Capital, backing the open-source ecosystem and a hosting service. That earlier investment addressed a developer's journey from writing Python to deploying a web application; the current offer reaches further into the customer's operating business.

Reflex's enterprise service starts with an agreed project and a measure of success. Engineers work alongside the customer, connect the relevant systems, prepare access and deployment with IT, and organize a handover with code, documentation and support. Building an application together is scoped as its own project, separate from the onboarding included in enterprise plans.

That division matters to the purchase. A customer needs to understand what the platform supplies, which implementation work is included and who will carry the application forward after rollout. Reflex is putting those questions inside its commercial offering. The work can begin with a purchasing approval or a dashboard around existing systems, giving the team a bounded assignment before it considers replacing something as consequential as an ERP.

The Python project has become an enterprise proposition

Reflex's founders started with a problem familiar to Python developers: useful logic can be ready well before there is a usable web application around it. The seed announcement dates the framework's launch to December 2022. The company then participated in Y Combinator's Winter 2023 batch, developing the infrastructure around an open-source foundation.

The current documentation spans UI components, databases, authentication, deployment, secrets and observability. That breadth shows how much has to surround generated application code before a team can share an internal tool with colleagues. A useful screen needs a route to the right data, the right access rules and someone able to understand a failure when work depends on it.

Company materials report more than 1M applications built, nearly 30,000 GitHub stars and usage inside 30% of the Fortune 500. These are different measures of developer adoption, with no published conversion rate from framework use to paying enterprise contracts. They describe an unusually broad introduction to prospective users while leaving the sales team with the more personal task of finding a funded problem inside each organization.

For buyers, the open-source foundation also changes the review. Their developers can inspect and extend the code, bringing technical judgment into a purchase that might otherwise be judged mainly through a vendor demonstration.

Deployment belongs in the buying decision

Reflex's bring-your-own-cloud offering supports deployment into an enterprise customer's AWS, GCP or Azure account. Its product documentation describes builds, registries and managed runtimes operating within that customer's cloud. The proposition addresses a constraint that exists before the first application feature is considered: the organization may already have decided where its workloads are allowed to run.

The company also established a Databricks Apps integration in June 2025. That integration connects the AI Builder to data and deployment inside the Databricks environment. For a Python-oriented data team, the route from an existing data investment to an application can therefore remain close to infrastructure the organization already uses.

The operating value becomes clearer in Reflex's Autodesk customer case study. The company-hosted account describes a consultant delivering a connected client application during a 60-day engagement, moving project information out of recurring spreadsheet handoffs. It is a specific customer account, rather than a forecast for every buyer, and its relevance lies in the delivery arrangement: a person with knowledge of the customer's problem could take more of the application into production.

That is where the sales conversation becomes concrete. Buyers can ask which systems the proposed application touches, where it runs and which person will be able to change it when the process changes.

Workflows extends the job beyond the application

Reflex's planned Workflows product remains on a waitlist. The company describes processes backed by readable Python, with progress saved between steps, explicit human approvals and retries after failed calls. Its examples follow work across documents, customer systems and notifications, extending the platform's role from presenting information into coordinating an operation.

Those mechanics carry a different kind of responsibility. A workflow that waits for a purchasing decision must preserve whose approval is needed and what happens after it arrives. A retry that changes an external system needs to handle the possibility that part of the work already succeeded. Reflex's description puts these details in the application code and its execution history, where a customer's team can inspect them.

The financing arrives while Reflex is also hiring for the commercial work around delivery. Current company job listings ask for help turning open-source adoption and founder-led demand into a repeatable sales operation. Rao and Petuskey have a framework already moving through organizations; the expanding team now has to follow it into the projects, cloud accounts and working relationships where a company decides to make that framework part of its business.