Self Hosting

Use reflex deploy for the managed workflow. Follow this page when you need to run the frontend and backend on your own infrastructure.

Clone your code to a server and install the requirements.

Edit your rxconfig.py file and set api_url to the publicly accessible IP address or hostname of your server, with the port :8000 at the end. Setting this correctly is essential for the frontend to interact with the backend state.

For example, if your server is at app.example.com, use:

It is also possible to set the environment variable API_URL at run time or export time to retain the default for local development.

If you want to serve the backend behind a reverse proxy at a subpath (e.g. nginx routing /api/* to Reflex), set backend_path on the config instead of baking the prefix into api_url. Every backend endpoint (event websocket, /ping, /_upload, /_health, /_all_routes) is mounted under that prefix, and the frontend baked into the export automatically calls the backend at the prefixed URLs — no request rewriting in the proxy is required.

frontend_path plays the analogous role for the frontend and the two are independent.

Note: changing backend_path (or frontend_path) requires a full restart of reflex run — routes and mount points are registered at startup, so hot reload alone will not move them.

Then run your app in production mode:

Production mode creates an optimized build of your app. By default, the static frontend of the app (HTML, Javascript, CSS) will be exposed on port 3000 and the backend (event handlers) will be listening on port 8000.

Exporting a static build of the frontend allows the app to be served using a static hosting provider, such as Netlify or GitHub Pages. Make sure api_url is set to an accessible backend URL when the frontend is exported.

This will create a frontend.zip file with your app's minified HTML, Javascript, and CSS build that can be uploaded to your static hosting service.

It also creates a backend.zip file with your app's backend Python code to upload to your server and run.

You can export only the frontend or backend by passing in the --frontend-only or --backend-only flags.

It is also possible to export the components without zipping. To do this, use the --no-zip parameter. This provides the frontend in the .web/build/client/ directory and the backend can be found in the root directory of the project.

Another option is to run your Reflex service in a container. For this purpose, a Dockerfile and additional documentation is available in the Reflex project in the directory docker-example.

Before building the image, update rxconfig.py and add requirements.txt to the project folder:

Notice that the api_url should be set to the externally accessible hostname or IP, as the client browser must be able to connect to it directly to establish interactivity.

You can find the requirements.txt in the docker-example folder of the project too.

The project structure should look like this:

After all changes have been made, the container image can now be created as follows.

Finally, you can start your Reflex container service as follows.