Entando supports the common cloud providers with the expected minor differences when it comes to networking, scaling, etc. There is a guide for Google GKE here: https://dev.entando.org/v6.2/tutorials/devops/installation/google-cloud-platform/ and Amazon EKS: https://dev.entando.org/v6.2/tutorials/devops/installation/elastic-kubernetes-service/eks-install.html. Installation instructions are in the works for Azure and OpenShift as well.
You can expect to pay a few dollars a day to host a minimal Entando installation on Google, Azure, or Amazon, and of course you’ll pay more depending on the scale of your application. Check the corresponding billing/cost explorer for your provider and you’ll see charges for everything in the stack, e.g. for AWS you’ll see line items for EKS, ELB, EC2, etc.
We don’t currently have a guide on scaling the architecture but the usual suspects will be for shared services like keycloak, any containers running your microservices, possibly the App Builder container if you have a large content team, etc.