This directory contains several examples of how to deploy Reflex apps using docker.

In all cases, ensure that your requirements.txt file is up to date and includes the reflex package. Commit the reflex.lock/ directory that reflex init creates so the frontend dependencies installed in the image match the ones you developed against.

Start here. This single-container deployment exports the frontend statically and serves it via a single HTTP port using Caddy, with a local Redis for state. The backend starts instantly because the frontend is built into the image, and a multi-stage build keeps bun, node_modules, and other build tooling out of the final image. It works anywhere a container with one exposed port can run, including platforms such as Render or Heroku.

This deployment is intended for use with a standalone VPS that is only hosting a single Reflex app. compose.yaml provides a webserver with automatic TLS in front of the app, which stores its data in SQLite. Adding the compose.prod.yaml override swaps in postgres and redis, which also lets the backend run multiple workers.

This example deployment is intended for use with App hosting platforms, like Azure, AWS, or Google Cloud Run. It is the backend of the deployment, which depends on a separately hosted redis instance and static frontend deployment.