As clarified by some sibling comments, having your own engineers writing code that has access to your private keys is potentially problematic. For one thing, a

As clarified by some sibling comments, having your own engineers writing code that has access to your private keys is potentially problematic. For one thing, a malicious or disgruntled engineer could sneak in code that exposes your private key material in some fashion. Secondly, and more likely, your engineers may make a mistake that inadvertently exposes process memory, which would include your private key material. In simpler terms, it often pays to have a firewall between important company secrets and the guy/gal who happens to be working on your web app this month. Assuming you would answer the question "Do your engineers have root access to production machines?" in the negative, you probably also don't want your engineers writing code that has access to the things that the root user has access to. One other way to put this is, are you comfortable running your Go process as root (in order to bind to port 443)?