The idea and functionality looks good. Some quick friendly feedback:<p>For production I would want to run this in Docker in some sort of a portable fashion.<p>Looking at the documentation it seems that you have to manually enter the password when you start up step-ca. That's not really going to work for automated setups. You need to be able to inject secrets from environment variables, or these days, Kubernetes secrets.<p>There's also the issue of backing up your CA secrets, e.g. if your step-ca process dies and you want to restart it somewhere else. That may be out of scope for step-ca though and handled through some other process, which is fine.<p>Might be good to add some documentation on how to set this up in a high availability fashion so it is not a single point of failure.<p>I do like the relative simplicity of this compared to all the other CA solutions out there. Good luck and thanks for the work.