[grocketeer]

Networking would definitely be a concern and I 100% agree that programming for higher failure rates is a must.

I would certainly default to bare metal, likely a simple go binary running as a Job side-runner for a main prod server hosted in the cloud.

> Lastly, I would definitely consider using gitlab.com to host code and run a gitlab runner from home. The previous parts of what I wrote become moot. The runner just connects when it can and runs jobs.

Gitlab runner looks promising, though I am not sure if it's intended for work outside the git workflow.

Thank you for your thoughts.

[favflam]

You can do a POST with an api access token to gitlab.com to get a job to run with custom environmental variable settings. So, you don’t have to use git to start a job.