Fair point, but it's important not to fool ourselves in terms of data safety or at least specify what we mean when we say "it's private on your vps". If your c

Fair point, but it's important not to fool ourselves in terms of data safety or at least specify what we mean when we say "it's private on your vps". If your code is private and not meant to fall into external hands, then putting it on a VPS won't protect it. The only way is to put it on a machine that's only used from workstations that access it in a local-only fashion, inside containers/vms that have no way to contact the outside world. This means the build process may not access the internet and has to rely on a cache of external libs if needed and allowed. This also implies that network config won't allow access as forbidden via VLANs or similar measures. If someone wants to steal your code, grabbing it from your vps won't be harder than doing the same on github/gitlab because the procedures to get access will be very similar. I suspect by private code you mean code which shouldn't be publicly clone'able but isn't behind locked doors otherwise.