Reverse proxy for now, but Pynecone is also working on a single command deploy feature that should take care of all this automatically. Should be released soon.
With PySaaS, your app's frontend is compiled down to a NextJS app, and FastAPI is built-in for the backend.
UI components are fully-customizable, and are actually wrappers around React components using Chakra UI. If you want to get fancy, you can even wrap your own components in three simple steps.
PySaaS uses the Pynecone web framework rather than Django or Flask.
This allows you to build the entire stack in a single language instead of having to learn and switch between multiple. You can install and import any Python library as you would with any Python file.
The frontend is compiled down to a NextJS app, and FastAPI is built-in for the backend. UI components are fully-customizable, and are actually wrappers around React components using Chakra UI.
That kind of other-language-to-JS stuff works great for small, one-man projects that never go to production. Unfortunately, other than TypeScript, none of these solutions have really achieved critical mass, and they all fizzle out after a few years, leaving you with a horrible mess to clean up. You have layers and layers of indirection, and you don't know whether your problem is your code, or a Python library, or the Python-to-JS layer, or one of the JS libraries, and no one on the Internet can help you because your stack is completely bespoke.
I applaud you trying to make it easier for people to get started, but throwing them on top of this Tower of Babel and pretending it will never come crumbling down into a mess of inconsistent languages and libraries is a recipe for pain. TypeScript is not that hard. If you're teaching beginners how to build a web front end, just start with that, and let them use either TypeScript or Python on the back end, depending on how ambitious they are.
