Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

EJBCA

ejbca.org

  • Free plan
  • Open source
  • Windows
  • macOS
  • Linux
  • Web
  • API
  • Self-hosted
8.7 Club score Visit ejbca.org

What EJBCA is

EJBCA is open-source public key infrastructure (PKI) and Certificate Authority software for managing certificates, registration, enrollment, and validation. One installation can support multiple separated, independent PKIs through its CA, RA, and VA modules. Certificate validation uses OCSP and CRL, and listed enrollment options include CMP, SCEP, EST, ACME, SOAP API, and REST APIs. Community Edition is available as a container, through Helm, or from source; Helm and Ansible playbooks can automate setup and configuration. It is presented for internal PKIs, DevOps workflows, industrial environments, IoT devices, and national eIDs. The free Community Edition is licensed under LGPL version 2.1 or later and is intended for learning, testing, and prototyping, not production workloads. It lacks production capabilities including audit, compliance, SLA, high availability, and security features. Enterprise adds advanced PKI functionality and professional support with an SLA.

Who it suits

EJBCA suits organizations managing internal PKIs or securing industrial environments, IoT devices, national eIDs, and DevOps workflows. Community Edition is for learning, testing, and prototyping rather than production use.

Good to know, and what to watch

  • Supports multiple independent PKIs in one installation
  • Certificate validation includes OCSP and CRL
  • Offers CMP, SCEP, EST, ACME, SOAP, and REST enrollment
  • Helm and Ansible can automate deployments
  • Community Edition is free and open source
  • Community Edition is not intended for production
  • Community lacks audit, compliance, SLA, and high availability

EJBCA Enterprise

—

EJBCA Community Edition

Free

EJBCA Enterprise Cloud trial

Free

EJBCA Enterprise trial

Free

Free plan · 30-day trial

Getting started

  1. Visit the EJBCA website.
  2. Choose Community Edition for free or start the Enterprise trial through AWS or Azure marketplaces.
  3. Deploy Community Edition with Helm, as a container or from source.
  4. Automate installation and configuration with Helm or Ansible playbooks if needed.

Limits to check

Community Edition is intended for learning, testing and prototyping rather than production, and lacks audit, compliance, SLA, high availability and security capabilities required for production workloads. The Enterprise trial lasts 30 days.

The Club's review

EJBCA is open-source PKI and Certificate Authority software for organizations that need to issue, manage, and validate certificates. It is best suited to teams building internal PKIs, securing IoT or industrial systems, supporting national eID programs, or automating certificate work in DevOps.

Overview

A single installation can run multiple secure, separated PKIs through its CA, RA, and VA modules. That makes EJBCA a strong fit when one organization needs distinct trust domains without treating certificate authority, registration, and validation as unrelated systems. OCSP and CRL support handle certificate-status checks, alongside revocation workflows.

The project dates to 2001, and Community Edition is licensed under LGPL version 2.1 or later. EJBCA is a registered trademark owned by PrimeKey Solutions AB, a wholly owned subsidiary of Keyfactor Inc.

Key features

Enrollment and validation

Community and Enterprise list enrollment support for CMP, SCEP, EST, ACME, SOAP API, and REST APIs. This range gives teams options for connecting different provisioning workflows, while OCSP and CRLs cover validation after issuance. Organizations with varied device and application enrollment needs will have more room to standardize on one PKI platform.

Deployment and automation

Community Edition can be deployed with Helm, as a container, or from source. Helm and Ansible playbooks can automate installations and configurations, making the software a natural candidate for infrastructure managed as code. The trade-off is operational: flexible deployment choices help experienced teams, but do not remove the work involved in running PKI infrastructure.

Integrations and controls

EJBCA lists HSM and crypto-token support, including PKCS#11-based and REST API-based key vault integration, AWS CloudHSM, and AWS KMS. The comparison also includes Common Criteria certification and audit logging to file, database, or syslog, while several advanced security and compliance capabilities are Enterprise features. Teams with strict production controls should weigh those Enterprise capabilities and its SLA against Community Edition's limitations.

Pricing

EJBCA offers a free Community Edition and a free Enterprise trial. The free edition provides basic PKI functionality for learning, testing, and prototyping; it is not intended for production use. That boundary matters: Community lacks audit, compliance, SLA, high availability, and security capabilities required for production workloads.

  • EJBCA Community Edition: free. Free open-source software for basic PKI work, suited to learning, testing, and prototypes rather than production.
  • EJBCA Enterprise trial: free. A 30-day trial of Enterprise edition functionality through AWS or Azure marketplaces, useful for evaluating the paid edition before committing.
  • EJBCA Enterprise: custom pricing. It adds advanced PKI functionality, multiple deployment options, and a support agreement with an SLA, making it the relevant plan for production deployments that need those assurances.

Enterprise includes professional support with an SLA. Community users can turn to GitHub Discussions on a best-effort basis, which is a less dependable support arrangement for organizations operating critical certificate services.

Platforms

EJBCA supports Linux, web access, APIs, and self-hosted deployment. Community Edition's Helm, container, and source options give technical teams flexibility over how they run it; the platform is better suited to organizations prepared to manage their own infrastructure than to users seeking a hosted, low-operations service.

Who it's for

EJBCA is a good fit for enterprises, public-sector organizations, and infrastructure teams securing industrial environments, IoT devices, national eIDs, DevOps workflows, or internal PKIs. Its separated PKIs, broad enrollment protocol support, and deployment automation serve complex environments well. It is not the right production choice for teams that need Community Edition's free price but also require production-grade audit, compliance, availability, security, or SLA coverage.

Pros and cons

  • Pros: One installation can support multiple independent PKIs, useful for keeping trust domains separate.
  • Pros: CMP, SCEP, EST, ACME, SOAP, and REST enrollment support accommodates varied provisioning systems.
  • Pros: Helm and Ansible automation, container deployment, and source availability suit teams integrating PKI into managed infrastructure.
  • Cons: Community Edition is explicitly not intended for production and lacks capabilities required for production workloads.
  • Cons: Advanced security and compliance capabilities, professional SLA support, and multiple deployment options are tied to Enterprise, whose price is custom.

Alternatives

For a priced CA service with FIPS 140-3 Level 2 HSM-backed CAs, consider EZCA; its Basic plan is $200 a month per CA. KeyTalk CKMS is another paid option, with an S/MIME on-premise plan at €5 a month per user for up to 250 participants and multiple devices.

Among free options, OpenCA PKI provides open-source PKI management software, while step-ca offers a single configured intermediate CA, an offline root CA, and authority-wide issuance policies. OpenXPKI has a free Community Edition with Debian packages, example configuration, documentation, and mailing-list support; XiPKI is another free option. For certificate lifecycle automation at large scale, Keyfactor Platform is a paid alternative with no per-certificate fees and a deployment tested for 500 million-plus certificates. Boulder is a free, MPL-2.0-licensed option, but production deployment requires separate implementation and security work.

Browse more options in Public Key Infrastructure Software and Certificate Management Software.

Verdict

Choose EJBCA if your organization needs a flexible, self-hosted PKI with separated trust domains, broad enrollment protocols, and automation options. Community Edition is useful for learning and prototypes, but production buyers should plan for Enterprise: its advanced capabilities and SLA address the central gaps in the free edition. If you need production assurances without custom-priced Enterprise, or prefer a narrower certificate service, compare alternatives before adopting it.

The verdict

EJBCA provides broad PKI and certificate-management capabilities, with deployment and automation options for Community Edition.

Questions people ask

Is EJBCA free?

Community Edition is free and open-source. The Enterprise trial is also listed as free for a 30-day trial.

What license does Community Edition use?

It is released under LGPL version 2.1 or later.

Can Community Edition be used in production?

It is not intended for production because it lacks capabilities including audit, compliance, an SLA, high availability and security features.

How can Community Edition be deployed?

It can be deployed with Helm, as a container or from source. Helm and Ansible playbooks can automate installation and configuration.

What does Enterprise add?

Enterprise includes advanced PKI functionality, multiple deployment options and professional support with an SLA. Its pricing requires contacting Keyfactor.

What the maker publishes

Algorithms
Supported cryptography includes RSA, ECDSA, Ed25519, Ed448 and post-quantum ML-DSA, ML-KEM, SLH-DSA and composite algorithms. source
API security
The certificate-management REST service is disabled by default and uses client-certificate authentication when enabled. source
Application servers
EJBCA targets JEE 10 compliant servers, while the actively documented and supported platforms are WildFly and JBoss EAP. source
Automation
EJBCA installations and configurations can be automated with Helm or Ansible playbooks. source
Automation
Official materials provide Helm charts and Ansible playbooks for automated deployment and configuration. source
Certificate validation
EJBCA supports certificate validation through OCSP and CRL functionality. source
Company facts
LinkedIn lists Keyfactor as privately held, founded in 2001, headquartered in Independence, Ohio, with 501–1,000 employees. source
Company legal name
Crunchbase lists Keyfactor's legal name as Certified Security Solutions Inc., also known as CSS. source
Company relationship
EJBCA is a registered trademark owned by PrimeKey Solutions AB, a wholly owned subsidiary of Keyfactor Inc. source
Deployment
Community Edition can be deployed with Helm, as a container, or from source; the download page links Docker Hub, Artifact Hub, and GitHub. source
Deployment choices
Documented deployment types are SaaS, AWS and Azure cloud, software appliance, hardware appliance, container set and software stack. source
Documentation
The official documentation includes concepts, installation, operations, integration guides, tutorials, troubleshooting, release notes and supported-version information. source
Enrollment protocols
Documented enrollment protocols include ACME, EST, Microsoft auto-enrollment and SCEP. source
Founded
2001 source
Integrations
The comparison lists HSM and crypto-token support, including PKCS#11-based and REST API-based key vault integration, AWS CloudHSM, and AWS KMS. source
Intended users
EJBCA is presented for securing industrial environments, IoT devices, national eIDs, DevOps workflows, and internal PKIs. source
Kubernetes requirements
The container deployment documentation requires Kubernetes 1.32 or newer and Helm 3 or newer, plus a supported database and HSM for non-ephemeral production instances. source
Licence
EJBCA Community is open source under LGPL version 2.1 or later; dependencies use licenses including Apache 2.0, BSD, MIT and EPL. source
License
EJBCA Community is released under LGPL version 2.1 or later. source
Limit: administration
G2 reviewers say initial configuration and administration can be difficult for organizations with limited PKI experience. source
Limit: installation
A SourceForge reviewer reported installation errors while deploying EJBCA 6 with Ant. source
Limit: operations and reporting
G2 reviewers cite weak log visualization, cumbersome OCSP configuration, limited reporting and insufficient troubleshooting or training material. source
Limit: user interface
G2 reviewers report a complicated, inconsistent and user-unfriendly interface despite extensive configuration options. source
Management protocols
EJBCA provides CMP, a certificate-management REST interface and SOAP web services for certificate administration. source

Checked against the maker's pages on 14 Oct 2026.