Hmm, food for thought;
The whole galaxy ui backend, being a meteor app itself, using ddp, meteor accounts, methods, graphql and whatnot, could in theory be invoked from a third party app. One simply needs to monitor the developer console for incoming/outgoing ws messages to see what goes on per each ui action.
Furthermore, an app can keep track of the number of connected clients (and perhaps some OS metrics depending on the environment) and at least conservatively decide for itself if it is sufficient to service the incoming load.
And then - oh and this would be so very meta - it could itself spin up a new instance or spin itself down.
Now I know it’s best if there’s an official API of sorts for this, but hey, this could still be a very fun community hack weekend project