@qwinter I used to segregate apps on different VPS. Largely through fear of apps conflicting with each other (different modules/scripts) and my personal ignorance of how containers worked.
It all cost me a fortune !! Multiple small bottom tier VPS, each of which did not consume their resources to an adequate level.
I've since gone with steadily bigger beefier machines, and certainly get better price/performance, adding on extra apps to research ("play") and they don't tax the power of a well-spec'ed host.
I do have separate VPS, one for Cloudron, one for non-Cloudron Docker deployments, etc. So I do segregate apps to different hosts but hopefully with more logic than I did before.
So I would go with the best host which makes sense to you, rather than multiple smaller ones, except where there is a clear technical reason (e.g. I don't risk my main Cloudron host with non-Cloudron docker apps).
Debugged this with @ZeZaung a bit. Somehow, it was possible to re-run cloudron-setup on the existing install and this reset the database even though the app containers and data were still there. I have made a fix which should hopefully mitigate the problem.
As I said on the other thread I seem to have managed to install cloudron on Ubuntu 20.04 LTS by following your advice to use ./cloudron-setup --version 5.6.3. I've disabled automatic upgrades and I'll wait a bit to upgrade to version 6.
All is good!
Just my 2 cents here : like girish said, if you want to run other things besides cloudron, you should install cloudron in a VM.
If you really want to dedicate the whole machine to cloudron, there is really no need to bother with the additional layer of complexity, another OS to keep up to date and such. I would go bare-metal in this case. That's how I've been running cloudron for 2 years, and it's great.