G2

Lovepreet S.

Graphic Designer and Software Tester

Computer Software

Small-Business (50 or fewer emp.)

9/9/2026

"Let’s Encrypt Makes HTTPS Simple,Free, Automated, and Accessible"

5/5

What do you like best about Letsencrypt?

For me, the biggest advantage of Let's Encrypt is its sheer practicality. Managing HTTPS becomes much simpler because I no longer have to treat an SSL certificate as a separate product that needs to be purchased and then maintained individually for each domain.

The setup can also be automated by installing an ACME client, which is especially useful on servers that host multiple domains or are administered by more than one person. That same automation can handle renewals on a regular schedule, removing the need for time-consuming manual work and reducing the chance of missed updates, integration is very easy.

Another thing I appreciate about Let's Encrypt is that it doesn’t lock you into any particular hosting provider. The only real requirement is that you control the domain, which can then be used to verify that you’re entitled to request an SSL certificate for it. For that purpose, Let's Encrypt offers HTTP-01, which is one of the simplest ways to prove domain ownership.

To me, one of the most compelling aspects of Let's Encrypt is that the private keys can remain on the server, or be generated directly by the ACME client.

Overall, I think this open-source project makes HTTPS security accessible even for smaller-scale operations. In that sense, Let's Encrypt removes the main barriers to implementing SSL encryption—both the cost and the often frustrating complexity of the process. Review collected by and hosted on G2.com.

What do you dislike about Letsencrypt?

The main argument I have against the proposal is that certificate management still requires technical expertise. The service itself may be completely free of charge, but configuring the ACME client, DNS, the web server, permissions, and renewals can be fairly involved. It should auto apply, integration of ssl should be auto.

Another issue is the short lifetime of the certificates. Without an automated renewal process, certificates can expire and disrupt the service. The current default is 90 days, but it is set to decrease to 64 days in February 2027 and then to 45 days in February 2028. That means certificate management and renewal need to be fully automated to avoid expiration problems; a system administrator should not have to remember to renew a certificate. Review collected by and hosted on G2.com.

What problems is Letsencrypt solving and how is that benefiting you?

Before services such as Let's Encrypt became available, getting HTTPS set up for multiple websites often involved buying certificates, handling renewals, completing manual validation, and dealing with a considerable amount of administrative overhead.

Let's Encrypt changes that paradigm by making it possible to obtain publicly trusted TLS certificates automatically, as an integral part of server administration rather than as a separate purchasing and management task.

This is particularly beneficial for systems that use many domains. I can set up an ACME client once and then have the system renew certificates automatically on a regular basis, instead of having to track each certificate’s expiration date separately.

For me, the most valuable aspect of Let's Encrypt is that it lets me integrate certificate administration into the normal operations of my websites and servers. That reduces the number of tasks I need to schedule and manage separately.

Not having to pay for certificates is an added bonus, but automatic renewal matters more to me because it enables proper HTTPS operation without requiring special attention. Combined with the fact that Let's Encrypt certificates are trusted by default, it makes Let's Encrypt a clear winner for day-to-day HTTPS operations. Review collected by and hosted on G2.com.