Happy to see this project hit public beta! I&#x27;ve deployed Let&#x27;s Encrypt on a couple of side projects during the last month or so, and my experience has been mostly positive.<p>The official client still needs some work, especially in terms of auto-configuration on apache, nginx and others, but it&#x27;s getting there. Some say it&#x27;s become a bit bloated, which is true to a certain degree, but probably necessary to achieve the goals they have set for it.<p>Luckily, Let&#x27;s Encrypt is based on an open specification (ACME) and it&#x27;s really easy to implement a custom client. There are already more than 10 client implementations out there[1], all created with different goals in mind - anything from a Ruby gem to a simple scripts to get your own CSR signed. If you&#x27;re not running your typical LAMP or LEMP stack, and don&#x27;t want to run the official client which is more of a certificate manager requiring root access, that&#x27;s definitely something to look into.<p>Note that if Windows XP support is relevant for your use-case, you might want to hold off. There&#x27;s currently a problem with how XP deals with name constraints, which means any application using Windows XP&#x27;s SSL API (I believe it&#x27;s called schannel?) won&#x27;t work - for example Internet Explorer and Chrome. This might get fixed in the future[2]. Hopefully, that&#x27;s not relevant to you. :)<p>[1]: <a href="https:&#x2F;&#x2F;community.letsencrypt.org&#x2F;t&#x2F;list-of-client-implementations&#x2F;2103?u=pfg" rel="nofollow">https:&#x2F;&#x2F;community.letsencrypt.org&#x2F;t&#x2F;list-of-client-implement...</a>
[2]: <a href="https:&#x2F;&#x2F;github.com&#x2F;letsencrypt&#x2F;letsencrypt&#x2F;issues&#x2F;1660" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;letsencrypt&#x2F;letsencrypt&#x2F;issues&#x2F;1660</a>