Managed PKI or your own PKI: operating models and providers
What is the difference between your own PKI and a managed PKI?
With your own PKI, you run the certification authorities yourself. Microsoft describes this option as a completely self-managed PKI with internal CAs chained to an internal root CA. With a managed PKI, a provider runs the PKI or parts of it: GlobalSign calls its offering “Public Key Infrastructure as a Service (PKIaaS)”, and Sectigo describes a “managed platform” for privately trusted certificates.
Between the two sit cloud CA services from large cloud providers. AWS describes its service as building private CA hierarchies of root and subordinate CAs without the investment and maintenance costs of operating an on-premises CA. What the terms behind this mean is explained in What is a PKI?.
Do third parties have to trust the certificates?
Microsoft names a criterion: if outside parties do not need to trust the issued certificates, now or in the future, a self-managed PKI with an internal root CA as the trust anchor may be enough. That gives you direct control over the security policies. For certificates that third parties should trust, Microsoft names the alternatives: buy a CA certificate from a commercial CA and issue internally below it, or use certificates from a commercial CA with a public root.
What does running your own PKI involve?
Your own PKI means carrying the tasks yourself. Microsoft lists these among the ongoing work of a CA:
- creating and managing certificate templates,
- managing the certificate lifecycle (issuance, revocation, renewal),
- maintaining the CA (updates, backups),
- managing and verifying CRL and OCSP availability.
Protecting the keys adds cost. Microsoft recommends an HSM for production CAs but calls it a significant capital investment. And according to Microsoft, an offline root brings new tasks: updating, maintenance and access.
How a PKI is built is covered in Building a PKI. The steps on Windows are in Setting up your own certificate authority (CA) on Windows.
What software is there for your own PKI?
According to Microsoft Learn, Active Directory Certificate Services is a Windows Server role for issuing and managing PKI certificates. Open-source and commercial products add to that, for example step-ca from Smallstep, an online CA for X.509 and SSH certificates, and EJBCA from Keyfactor. For EJBCA the documentation names several deployment forms: SaaS, cloud, software appliance, hardware appliance, container and software stack.
Which providers are there?
- AWS Private CA: A cloud CA service that, according to AWS, builds CA hierarchies with root and subordinate CAs. It issues X.509 certificates, for example for TLS, for authenticating users, computers, API endpoints and IoT devices, and for code signing. According to AWS, private CAs are Regional resources. AWS names connectors for Kubernetes, Active Directory and SCEP.
- DigiCert Trust Lifecycle Manager: According to DigiCert’s documentation, a solution that combines CA-agnostic certificate management with PKI services. DigiCert counts intermediate CA creation and private certificate issuance for users, devices and servers among the PKI services.
- EJBCA (Keyfactor): CA software that, according to its documentation, can implement virtually any PKI architecture, from a self-contained internal PKI to infrastructure with high availability requirements. The documentation names a national eID, an IoT platform or your own internal PKI as fields of use.
- GlobalSign Managed PKI: Called PKIaaS by GlobalSign. Features on the product page include using existing Active Directory policies to control who may issue which certificates, an audit trail and an API integration.
- Google Cloud Certificate Authority Service: According to Google, a highly available and scalable service that simplifies and automates deployment, management and security of private CAs. It has two operation tiers: DevOps for high volumes of short-lived certificates and Enterprise for lower volumes of long-lived ones.
- Microsoft Cloud PKI (Intune): According to Microsoft Learn, a cloud-based service for certificates on Intune-managed devices, without on-premises servers, connectors or hardware. It can create a two-tier hierarchy with root and issuing CA in the cloud, or anchor an issuing CA to your own root.
- Sectigo Private PKI: According to Sectigo, a managed platform for issuing and managing privately trusted TLS/SSL certificates, with seat-based licensing.
- Smallstep: According to the platform documentation, the maker of step-ca offers a hosted platform (SaaS), “Run Anywhere” for a customer-operated data center, and “Step CA Pro”, a commercial extension of the open-source server.
What do cloud CAs cost?
AWS and Google state their prices on their price pages. All amounts below are shown there in dollars, reflect the pages as of 19 November 2026 and may change.
What does AWS Private CA charge?
According to its price page, AWS charges a monthly fee per CA, a fee per issued certificate and for the use of OCSP:
- $400 per CA per month in general-purpose mode, $50 in short-lived certificate mode (certificates valid for up to 7 days).
- Certificates in general-purpose mode per month and Region: $0.75 for the first 1,000, $0.35 up to 10,000, then $0.001; short-lived certificates $0.058.
- OCSP: $0.06 per certificate per month with a response, plus $0.20 per 100,000 queries.
- The first 30 days of the first private CA per account and Region carry no operating charge; issued certificates are charged even then.
What does Google charge?
Google’s Certificate Authority Service also charges per CA and per certificate:
- DevOps tier: $20 per CA per month, certificates $0.30 up to 50,000, $0.03 up to 100,000, then $0.0009.
- Enterprise tier: $200 per CA per month, certificates $0.50 up to 50,000, $0.05 up to 100,000, then $0.001.
- Example from the price page: one DevOps-tier CA with 10,000 certificates per month costs $3,020.
What applies to the other providers?
Microsoft gives no price for Microsoft Cloud PKI but requires a subscription in addition to Intune Plan 1 or Plan 2. Sectigo names “flexible seat-based licensing”, and GlobalSign pay-as-you-go, deposit or license deals. Smallstep points to a pricing request.
What matters when you decide?
The providers’ pages give no recommendation for an individual case. These questions help with the choice.
Who holds the key?
At Google, HSM-protected CA keys are possible in both tiers, a customer-managed key through Cloud KMS only in the Enterprise tier. With Step CA Pro, Smallstep says you keep full control over the CA and signing keys.
For Cloud PKI, Microsoft names HSM keys in Azure Managed HSM, with one exception: CAs created during the trial period use software-backed keys. These stay software-backed after you buy a license, and according to Microsoft they cannot be converted to HSM-backed keys. If you want to keep the root, you can anchor an issuing CA to your own root.
How much operating work stays with you?
AWS speaks of a CA without the investment and maintenance costs of on-premises operation, Microsoft of a service without on-premises servers, connectors or hardware. Work remains even then: you create certificate profiles and distribute the trust anchors to the devices. For Microsoft Cloud PKI, the documentation explicitly lists trust profiles for the root and issuing CAs and SCEP profiles.
How does the service connect to Active Directory and Intune?
Microsoft Cloud PKI issues certificates for Intune-managed devices (Android, iOS/iPadOS, macOS, Windows) and needs a SCEP profile. AWS names a connector for Active Directory, offered at no additional charge according to its price page. Smallstep describes itself as a replacement for AD CS, with support for SCEP and NDES and the option of bringing your existing root CA.
What do the providers say about audit and location?
Sectigo names auditability and data sovereignty as goals, and GlobalSign an audit trail for ISO and other requirements. These are statements by the providers, not audits. Whether they meet your requirements, you have to check against the provider’s evidence.
Location counts too: AWS private CAs are Regional resources and cannot be copied between Regions. With Microsoft Cloud PKI, both endpoints sit with Intune: Intune hosts the CRL distribution point for each CA, the CRL is valid for seven days and is refreshed every 3.5 days. Intune also hosts the AIA endpoint for each issuing CA, and relying parties can use it to retrieve parent certificates.
Sources
- Microsoft Learn: Securing PKI: Planning a CA Hierarchy, retrieved on 19 November 2026
- Microsoft Learn: Securing PKI: Protecting CA Keys and Critical Artifacts, retrieved on 19 November 2026
- Microsoft Learn: Securing PKI: Technical Controls for Securing PKI, retrieved on 19 November 2026
- Microsoft Learn: What is Active Directory Certificate Services?, retrieved on 19 November 2026
- Microsoft Learn: Overview of Microsoft Cloud PKI for Microsoft Intune, retrieved on 19 November 2026
- AWS: What is AWS Private CA?, retrieved on 19 November 2026
- AWS: AWS Private CA Pricing, retrieved on 19 November 2026
- Google Cloud: Certificate Authority Service documentation, retrieved on 19 November 2026
- Google Cloud: Select the operation tiers, retrieved on 19 November 2026
- Google Cloud: Certificate Authority Service pricing, retrieved on 19 November 2026
- DigiCert: Trust Lifecycle Manager, retrieved on 19 November 2026
- GlobalSign: Managed PKI, retrieved on 19 November 2026
- Sectigo: Private PKI, retrieved on 19 November 2026
- Smallstep: Platform documentation, retrieved on 19 November 2026
- Smallstep: Pricing, retrieved on 19 November 2026
- Smallstep: step-ca Certificate Authority Overview, retrieved on 19 November 2026
- Keyfactor Docs: EJBCA Introduction, retrieved on 19 November 2026