I'm only speculating, and/or it could even differ per organization since in my mental model deploying Orion is only one step of many, but I would guess the two

I'm only speculating, and/or it could even differ per organization since in my mental model deploying Orion is only one step of many, but I would guess the two stacks you mentioned are famous for their watch-and-refresh development model. Thus, the coder presses "Save" (or perhaps "Commit", if "Save" is not atomic enough for deployment) and then either the CI system pushes out files or deploys for you or Orion pokes the development server to grab the latest files. I am 100% positive it will take some mental and maybe even logistical reorganization to switch to a cloud-based coding environment. Almost every change I can think of in a professional capacity is evaluated in a cost-benefit analysis. But today I am home sick, and thus have no access to my properly configured PyCharm, nor access to the local feature branches on my machine and it would be a bunch of ssh hoop jumping to deploy anything that I did write while at home. My interests are pretty much in descending order of that list. I would love a copy of cloud-PyCharm.