Interoperability & Standardization #6246
Description
Tracking issue for aligning Reflex with Python ecosystem standards so the framework composes naturally with existing tools and workflows rather than requiring its own conventions.
Theme
Reflex should be mountable in arbitrary Python backends and configurable via standard tooling. Users shouldn't need Reflex-specific knowledge to integrate Reflex into their existing stack.
Scope
ASGI Interoperability (ENG-9182)
Make Reflex a mountable ASGI sub-app instead of owning the full server stack. This lets users compose Reflex with Starlette, Litestar, Django, FastAPI, or any ASGI framework — and enables Reflex to drop into existing app architectures without rewriting the server layer.
- Directly enables #46 (Embedding Reflex in other apps — oldest open issue)
Config via pyproject.toml with App Profiles (ENG-9183)
Support [tool.reflex] in pyproject.toml with named profiles (dev, prod), making rxconfig.py optional. Aligns with how every other Python tool is configured.
- Related: #6117 (flexibility in renaming rxconfig.py)
Existing Issues
- #46 — Embedding Reflex in other apps
- #6117 — Flexibility in renaming rxconfig.py
Roadmap
Part of the Reflex Framework Roadmap.