Side by side
Boulder vs EJBCA
Both stand on public key infrastructure software. Which one you can start free with, which one lets you read the code, and what each costs once you pay.
Boulder provides a modular ACME certificate authority implementation, but its development environment is explicitly not production-ready. Its stated production focus and support priorities make fit assessment important for organizations outside Let’s Encrypt.
Visit BoulderChoose EJBCA Community for free PKI learning, testing, and prototyping, especially when its deployment and enrollment options fit your setup. For production needs requiring advanced PKI capabilities, compliance, high availability, or SLA-backed support, consider Enterprise; its price is available by contacting Keyfactor.
Visit EJBCAThe facts
| Boulder | EJBCA | |
|---|---|---|
| Free plan | Yes | Yes |
| Open source | Not published | Yes |
| Runs on | API, Linux, Self-hosted | API, Linux, Mac, Self-hosted, Web, Windows |
| Lowest paid plan | Free or on request | EJBCA PKI SaaS: £62,065 a year |
| Plans published | 1 | 5 |
| Maker | Not published | Not published |
| Website | github.com | ejbca.org |
| On public key infrastructure software | #5 of 26 | #1 of 26 |
Boulder: what it does well
- Free under the Mozilla Public License 2.0.
- Supports ACME issuance and revocation workflows.
- Separates certificate authority work across components.
- Works with Certbot or another ACME client locally.
- Deployment guidance describes mutual TLS and firewalling.
What to know first
- Docker development setup is unsuitable for production.
- Built for Let’s Encrypt and may not fit other production deployments.
- Timely support may not be available for other deployments.
- Development setup exposes debug ports and uses public private-key material.
EJBCA: what it does well
- One installation can host multiple independent PKIs.
- Supports certificate validation through OCSP and CRL.
- Enrollment options include CMP, SCEP, EST, ACME, SOAP, and REST APIs.
- Community supports Helm, container, or source deployment.
- Helm and Ansible playbooks can automate installation and configuration.
What to know first
- Community Edition is not intended for production use.
- Community lacks audit, compliance, SLA, high availability, and required security capabilities.
- Enterprise pricing requires contacting Keyfactor.
- Community support through GitHub Discussions is best-effort.
Alternatives to Boulder Alternatives to EJBCA The whole list
