And @Terra as well.
It’s complicated. And when you’re using a hosting provider, they probably won’t allow you to do it anyway.
You can hop from private server to private server as long as they have a shared grid config, and as long as the grid server is reachable for each private server.
There’s still the single point of failure in the actual grid server that maintains all the things between grid nodes.
Each grid node has its own configuration files, so you can change grid nodes in whatever way you want (decay, harvesting rates, taming rates, everything), but you’ll run into problems when you change the passwords for them. They’ve somewhat fixed this in one of the latest releases, but there’s still a huge chance it’ll disconnect you on zoning into another grid node.
I’ve put a lot of work in the technical background of it all, but decided not to run a private server for Atlas, since unlike ARK it’s still extremely inefficient and takes up a huge amount of resources for each grid node.
As a comparison: I run 6 ARK servers, which use about as much resources as 1-2 grid nodes in Atlas.
My system has 8 cores, and Atlas will fully utilize one core regardless of what a grid node is actually doing. Even if there’s no one online, a 9-node grid will put my system at a constant 100% CPU usage. And I only have the one system to run servers on 