CertAutoPilot vs win-acme
win-acme is a popular open-source ACME client for Windows: installed on an IIS server, it obtains a certificate, binds it to the site and renews it with a scheduled task. CertAutoPilot manages Windows certificates from a central service over WinRM, together with the rest of your infrastructure.
| CertAutoPilot | win-acme | |
|---|---|---|
| Model | Central service, agentless; connects to Windows over WinRM (NTLM, Basic or Kerberos) | Installed on each Windows server, renews with a scheduled task |
| Windows targets | IIS (sites and bindings, several sites per server), Microsoft Exchange, any Windows path or script | IIS bindings, the certificate store, scripts |
| Certificate authorities | ACME (public and private CAs) and Microsoft AD CS | ACME |
| Other systems | 18 more targets: Linux, Kubernetes, load balancers, firewalls, vaults, CDNs | Windows only |
| Many servers | One certificate deployed to every server, verified and rolled back centrally | Configured on each server |
| Visibility | Central inventory, expiry alerts, approvals, audit log | Per server |
| Licence | Free tier with every feature; Enterprise by certificate count | Open source (Apache 2.0) |
When win-acme is the right choice
A few stand-alone IIS servers with public names, managed by people who are comfortable on each machine, are well served by win-acme.
When CertAutoPilot fits better
- Certificates come from your internal Microsoft AD CS as well as public CAs.
- One certificate is shared by an IIS farm, an Exchange organisation or a load balancer in front of them.
- You want no software installed on production Windows servers, and a central record of what was deployed where.
- Older Windows servers are involved: CertAutoPilot builds the PFX it deploys in a form Windows Server 2016 can import.
Questions
What does CertAutoPilot need on the Windows server?
Only WinRM enabled and an account that is a local administrator. Nothing is installed. If a local account gets HTTP 401 over NTLM with UAC on, see our post on LocalAccountTokenFilterPolicy.
Can it update IIS bindings on several sites at once?
Yes. A target can select one site, several sites or every site, and filter bindings by IP address, port and host name. A preview shows which bindings will change before you deploy.
Run it on your own infrastructure. The free tier includes every feature.
Talk to us →