(This post is a community wiki; other community members are welcome to edit and improve it.)
Figuring out where to begin with selecting ACME certificate management software can be tricky. The client options documentation page lists a lot of choices, each one of which may be useful for its specific intended audience. But the recommendation at the top to just use Certbot if you need a client doesn't always help answer the question of whether one needs to use a standalone client in the first place. Certbot is good at what it was intended to do, but with the proliferation of the ACME protocol into many pieces of software, there may be something built-in to the system that you're already using that might be better suited to your needs.
This flowchart is intended to give a starting point, with the technologies that we've seen most recommended around here. It won't give a perfect answer for everyone, but if you're not sure where to begin with securing your site it should give you a first option to consider looking at. Feel free to create a new post (not replying to this one, but a separate post) with details of your specific needs if you want personalized recommendations.
The most recent update to the flow chart by @toddhgardner doesn't honor the intention of this chart. It is supposed to reflect the most common recommendations as they are tried and true solutions. Todd's product is new and the only posts I recall about his product are his own posts promoting it.
In addition, while the question newly added to the chart comes up often in the community there are many possible solutions not just that one new product. These solutions vary considerably and some of the more common ones discussed are:
Education about best practices
Use of hooks or similar techniques to briefly open port 80
Using a firewall that allows filtering by HTTP URL
Use of tls-alpn-01 challenge to use port 443
Different architectures in complex setups
Other products that handle DNS authorizations (ex: acme-dns)
I am inclined to restore the original chart unless there are good objections.
Perhaps someone could make a different guide to show highlights of the different ACME related products. There are many that have features that are useful in certain cases. I am personally not keen to create such a guide but that would be better than adjusting this flowchart to mention every possible ACME product.
@MikeMcQ Of course, my apologies. I took this line as an invitation to share:
What the current chart didn't illustrate is how to use ACME for purely internal systems where they will never open port 80, 443, or anything else. Companies are often also stuck on old DNS systems that offer no facility to change things programmatically, so they don't have any good options. Essentially, a delegated, central ACME client approach rather than each server on its own.
Sure, but that wasn't the only line describing the purpose of the chart. You can imagine how unwieldly it would become should there be a box for every possible ACME related product.
The chart wasn't intended to guide companies with large installations as noted by the first question in the chart. Discussing companies and their infrastructure often needs more complex solutions. We discuss that from time to time in this community and it usually involves quite a bit of back and forth.
I think there is some value to having a grid, checklist, or similar which covers those more complex setups. This chart wasn't intended for that. And, I think if you re-read the intro and the chart you'll find your enthusiasm for promotion got the better of you this time