Skip to main content
Integrate with External Certificate Authorities (CAs) to use existing PKI infrastructure or connect to public CAs for certificate issuance.
This page is for product admins setting up PKI infrastructure. Teams issuing certificates should see Applications.

Public CAs

Public CAs issue certificates that browsers trust, for public-facing services:

ACME-compatible CA

Connect to any CA that supports ACME, such as ZeroSSL or Buypass.

Let's Encrypt

Free, automated certificates for public domains.

DigiCert (ACME)

DigiCert certificates through ACME with External Account Binding.

DigiCert (CertCentral API)

DigiCert TLS and code signing certificates through the CertCentral Services API.

GoDaddy

Domain Validated certificates through the GoDaddy Certificates API.

Sectigo

Sectigo certificates through ACME with External Account Binding.

AWS ACM public CA

Publicly trusted certificates from AWS Certificate Manager.

Private CAs

Private CAs issue certificates for internal services, from PKI you already run in the cloud or on premises:

Microsoft ADCS

Microsoft AD CS over MS-WCCE through an Infisical Gateway.

Azure ADCS (web enrollment)

Microsoft AD CS over HTTPS web enrollment.

AWS private CA

Private certificates from AWS Private Certificate Authority.

Venafi TLS Protect Cloud

Venafi’s cloud-based certificate management platform.

Venafi TPP

Venafi Trust Protection Platform, on premises.
Don’t see your CA? Contact [email protected] and we’ll help you set up the integration.

FAQ

Yes. You can have both Internal and External CAs in the same Certificate Manager.

What’s next?

Internal CA

Create your own private CA hierarchy.

Certificate Policies

Define constraints for certificates.

Certificate Profiles

Create profiles that link CAs with policies.

Applications

Issue certificates through Applications.