Personally I'd stick with Heroku for now unless you're hitting real limitations or anticipate them quite soon. Cloud fiddling tends to not produce a lot of visi

Personally I'd stick with Heroku for now unless you're hitting real limitations or anticipate them quite soon. Cloud fiddling tends to not produce a lot of visible customer value at early stages. Cloud choices are also "stickier" than most people expect. Migrating a successful service is often much harder than the initial cloud build. The Heroku -> AWS path is a pretty natural one to take. You could stay in Heroku, create an AWS account and start managing your DNS configuration with an IAC tool (e.g. terraform) in AWS. That then opens up a bunch of options later down the line, like S3 integrations, peering an AWS VPC with Heroku, wiring up various AWS managed services, CDN, cert issuance and so on, all using the same basic tech. You could keep your current workflow but a pretty smooth migration path available to move off Heroku and into AWS on your own time. If you need to. I don't "love" AWS, but I know most of the rough edges now and I think that's how a lot of people feel about it. I think Heroku also has pretty strong GCP integration so that's also a natural option. You could also avoid making a cloud choice now and just use any DNS provider with a decent API. P.S: I think you could be successful with any of the services you listed, but would not recommend Linode, Hetzner, OVH etc due to the lack of managed service options. If you're using Heroku now, I predict you'll want managed service options in future. Apart from the services you listed, you might also be interested in fly.io (I'm not affiliated).