I think you're right - we should include those instructions for now, and provide a bastion-as-a-service later. The daemon route is clearly preferable for custom

I think you're right - we should include those instructions for now, and provide a bastion-as-a-service later. The daemon route is clearly preferable for customers, so we'll build that out (we already have manual key-adding confirmation, and we record the IPs of people who attempt to download/upload keys). I would note, though, that if we're hacked, the attacker doesn't get access to the users. We actually don't store the encryption keys for the deployment keys; the client does. Still, the daemon route is what we need to do. Thanks for the feedback.