We are early Porter users, and it strikes the right balance of being being "full service" to get you started quickly but then letting you tweak what we need in custom ways as you grow.

The setup was simple - EKS cluster created for you (or you can use your own), automatic bot instrumentation to build and push containers for you, Heroku-like "git-ops" etc.

But, under the hood they made the (IMO) wise choice to use each cloud's tooling as much as possible so you can modify things as needed. For example, the EKS cluster on AWS is in a regular autoscaling group. Persistent drives for containers (if you opt-into them) are regular EC2 block devices, etc.