Boulder vs Entrust Certificate Manager

Boulder is an open-source ACME certificate authority written in Go and used to run Let’s Encrypt. ACME lets a certificate authority verify control of an identifier and allows subscribers to issue or revoke certificates for identifiers they control. Boulder divides its work among web front ends, registration and validation authorities, a certificate authority, storage authority, publisher, and CRL updater. These boundaries separate CA functions by security context, with the certificate authority receiving instructions from the registration authority. Components communicate through gRPC, and the software stores ACME accounts, authorizations, challenges, orders, and certificates. Boulder is free under the Mozilla Public License 2.0 and is listed for API, Linux, and self-hosted use. Maintainers recommend Docker and Docker Compose for development and experimentation, and document connecting Certbot or another ACME client to a local instance. That Docker environment is not suitable for production: it uses publicly available private key material, exposes debug ports, and is described as brittle when components fail. Boulder is built for Let’s Encrypt and Web PKI baseline requirements; maintainers say it often does not fit other organizations’ production needs.

Entrust Certificate Manager centralizes discovery and lifecycle management for digital certificates, from audit and issuance through renewal and revocation. It can find certificates across networks, cloud environments, and CA repositories, then provide continuous monitoring, reports, and alerts. Policy-driven workflows automate lifecycle steps, and certificates from Entrust and third-party CAs can be managed through one control point. Entrust describes deployment across on-premises, private cloud, and public cloud environments. Integration choices include cloud, automation, CA gateway, enrollment protocol, secrets management, and custom REST APIs. The API can query certificates by metadata, import certificates, and update custom-field metadata, subject to token permissions. Compatibility information lists PostgreSQL 15 or higher, OpenID Connect 1.0, LDAP v3, and other specified components. Entrust says the product supports crypto-agility and post-quantum readiness. Pricing is on request, and there is no free plan. Entrust was founded in 1969 and is headquartered in Minneapolis, Minnesota.