I like that you can just use the hostname for web and ssh, without considering that the same IP address isn't exclusively yours.
And, sure, you can add a -p option. But if you have 20 VMs (which is how many come with their basic plan) you'd have to remember all the different port numbers.
hmm. I see the point about using the same hostname… but that's what .ssh/config is for.
You also can't really use the public hostname for this, can you. Unless you do really complex DNS trickery, you can only return one (set of) IP address for a given name. It would thus need to be the same IP address for everyone. Which works only as long as 2 users don't have overlap in the VMs they want to access…
(I guess they can run a solver and try to make it work for as long as possible, including reassigning IPs… but it'll hit a wall at some point?)
Sorry, I don't understand your point about the DNS thing. I don't think multiple owners share the same hostnames. Each owner has a set of 20 hostnames that are unique to their account. And there are 20 IP addresses shared across all owners.
> I don't think multiple owners share the same hostnames.
That's exactly what I mean, this approach wouldn't be able to handle unconstrained sharing of systems among multiple users. If you're, say, a freelancer who has access to a bunch of people's systems… and another freelancer has access to half of those, and then a bunch of others… these combinations create exclusions that can make the whole thing unsolvable if they're large enough.
And, sure, you can add a -p option. But if you have 20 VMs (which is how many come with their basic plan) you'd have to remember all the different port numbers.
(I'm not in the target market for their service.)