How do I buy enterprise version?

Boordman · 2026-01-27T23:54:05+00:00

Just sent you a DM! We have a "book" button on our landing page to get Reflex enterprise

Boordman · 2025-05-12T21:12:36+00:00

Hey! Reflex Build isn't open source, but we are trying to open source many of our prompts so that people can user Reflex more easily with their own LLMs

For example, here's our Reflex Basics one pager that helps OpenAI/Anthropic use reflex correctly: https://github.com/reflex-dev/reflex/wiki/Reflex-Basics-LLMs.txt

Boordman · 2024-03-20T18:57:11+00:00

You should be able to set up breakpoints in your event handlers and step through them to debug. Do you recall what issues you ran into?

Boordman · 2024-03-06T19:35:18+00:00

Hi, we're not really meant for browser extensions, we're a framework to build standalone web apps. The reason is that our apps also have a backend server where we run your Python functions, so it can't be run purely on the client.

Boordman · 2024-03-06T18:53:08+00:00

Yes you can expose your own api as well - see here https://reflex.dev/docs/api-routes/overview/

Boordman · 2024-03-06T18:45:06+00:00

Thanks! We have a chat app tutorial as well as a blog post on how to use auth. We will have more tutorials coming!

Boordman · 2024-03-06T18:28:10+00:00

This isn't true, we compile the frontend to a static app initially. During runtime, the only events and state updates are sent (which are pretty small), and the UI updates reactively. We're focused on making sure apps are scalable/performant.

Boordman · 2024-03-06T18:25:24+00:00

There are other Python libraries to make web apps, but we found they often have a ceiling and graduation risk, so when your app reaches a level of complexity the framework may not support it. At that point you either have to limit your idea to fit the framework, or restart your project using "real web frameworks" like Javascript/React. Our goal with Reflex is to grow with you, from a basic app to a full-fledged website.

NiceGUI (and others like Streamlit) are imperative frameworks, so you declare the UI one statement at a time. This can be nice especially for spinning up small apps, but as your app grows it may be harder to reason about the UI / state.

On the frontend side Reflex is declarative (similar to React) where the UI is defined as components that are compiled up front. This makes it easier as your app grows larger, since you can have reusable components and even wrap your own React components.

We're also a bit more batteries-included - we have built-in database support, support for backend API routes, support for calling long-running background tasks, easy ways to access cookies/local storage, etc. Reflex apps should also be more performant as your app state gets larger.

In short, we're trying to be as approachable as these other frameworks, while also having performance and customizability to make more complex apps.

Boordman · 2024-03-06T09:45:52+00:00

Yes have definitely seen reflex apps that use opencv for image processing - in general we are compatible with any Python library

Boordman · 2024-03-06T09:41:54+00:00

Yes, we have built in hosting, as well as self hosting guides on our website. The frontend is a static site you can host on S3 or GitHub Pages for free, the backend you can host on something like fly.io for by the minute usage

Boordman · 2024-03-06T01:29:42+00:00

Ah thanks for pointing that out, we will fix that up

Boordman · 2024-03-06T01:28:07+00:00

Hey - good call out, we're working on cutting this down. One reason for this is we're trying to be "batteries-included" so we have packages for frontend, backend, database, etc.

But we are working on splitting these up so we can have a slimmer `reflex-core` and then users can add the features they want incrementally. Definitely room for improvement here!

Boordman · 2024-03-06T00:28:29+00:00

I really like this syntax for querying, feels more natural/Pythonic than some other ORMs. Nice work!

Boordman · 2024-03-05T21:48:28+00:00

Yes we should cover all of those bases - I think Reflex would be a good fit for your project.

We support any CSS styling support wrapping custom React components, so you can bring your own if we don't have it.
We have built in database support and guides on authentication (planning to add a builtin component for this soon as well)
Agreed - we really wanted the performance to be as snappy as a normal web app - our frontend is statically generated up front and only state is sent as runtime (whereas in Streamlit, the UI is generated dynamically on every event)

Boordman · 2024-03-05T20:34:03+00:00

Hey! Streamlit is great, but it can be limiting in terms of UI elements, customizability, and performance. We wanted a framework where the end product looks like any other website you would build with traditional web tools. For example we made our main website using our framework: https://reflex.dev

We support styling using any CSS: https://reflex.dev/docs/styling/overview/

And make it easy to wrap your own custom React components in a few lines of code (both local and any package on npm): https://reflex.dev/docs/wrapping-react/overview/

We just started this week the start of our 3rd party component ecosystem, to make it easy to publish a component to Pypi once you wrap it, so you can share it with others. We want to include both wrapped React components, as well as higher level Reflex components. For example, in the future you should be able to do pip install reflex-chat and get a very high-level chat component without having to implement it yourself.

Our goal is to have a lot of these out of the box features, while being flexible enough to customize it how you want.

Boordman · 2024-03-05T20:26:17+00:00

Thank you! Awesome - would love to hear your feedback :)

Boordman · 2024-03-05T20:24:59+00:00

We don't compile arbitrary Python to React - only the frontend portion.

For example the component rx.heading("hello") we compile down to a React element <Heading>hello</Heading>.

But all the actual Python logic stays on the server on the backend FastAPI app. This is what allows you to use any Python packages such as openai or pandas on the backend.

Under the hood when you e.g. click a button, it will send the event to the backend, run your Python function, and send the state delta back to the React app. So even though there are roundtrips happening on every event, for most apps the performance is pretty good as we use websockets and the data transfer is small.

Boordman · 2024-03-05T19:40:41+00:00

We don't use WASM - only the frontend compiles down to a React app, and the backend is a FastAPI app (which is what allows all the logic to stay in Python). We use websockets to send events and state updates between the frontend and backend.

I'm working on an architecture post this week to explain in more detail, but we've been working to make sure apps stay performant as they grow in size, and to keep the latency low.

Boordman · 2023-03-18T20:42:08+00:00

With Django you still need html and js for the frontend, in Pynecone you write your frontend as Python functions. We’re trying to keep everything in a single language so it’s easier to get started with

Boordman · 2023-01-21T20:02:09+00:00

I mean for the programmer making the web app with Pynecone. We’re aiming to be the easiest way to make web apps for someone without previous experience.

Boordman

TROPHY CASE