◇ Could this help me?
Yes on the stack, with the deployment advice treated as one opinion rather than a rule. The application stack named is mainstream, well documented, and a genuinely reasonable default, which matters because a conventional stack is the one an assistant has seen the most examples of. Be skeptical of the blanket instruction to abandon managed platforms for raw cloud services: containers, registries, and load balancers add real operational work that a solo builder often cannot absorb, and the right answer depends on team size and compliance needs rather than on the platforms being wrong. This is a general practice.
I am choosing a stack for a new project I will describe. Compare the mainstream default of a Python API with an ORM, a React-based frontend with TypeScript and utility styling, and a Postgres database against the alternatives you would consider for my specific case. Then compare deploying on a managed platform against assembling the equivalent on a general cloud provider, and be concrete about the operational work each option adds: what I would have to maintain myself, what breaks at 2am, and what it costs at low and moderate traffic.