All Use Cases
Security

Enterprise PKI with Constrained CAs and ACME Automation

Full CA hierarchy with X.509 Name Constraints, OCSP revocation, SPIFFE identity (X.509 + JWT-SVID), and Let's Encrypt ACME -- all managed from one platform.

Create a Constrained Intermediate CA

Name Constraints enforced. Chain verified. ACME ready.

Three steps. Complete certificate lifecycle.

From root CA creation to automated renewal, every certificate is constrained, tracked, and audited.

Create Root CA

Provision an offline ECDSA or RSA root CA with a hardware-backed key. The root signs intermediate CAs only -- it never issues leaf certificates directly.

Issue Constrained Intermediate

Create scoped intermediate CAs with RFC 5280 Name Constraints -- permitted and excluded DNS names, IP ranges, and email domains enforced at the cryptographic level.

Auto-Renew with ACME

Workloads use the built-in ACME endpoint to request and renew certificates automatically. No manual CSRs, no expiry surprises, no toil for engineers.

Everything a modern PKI needs

From root of trust to certificate inventory, the entire lifecycle in one place.

RFC 5280

Name Constraints

Permitted and excluded DNS names, IP ranges, URIs, and email domains enforced as a CRITICAL extension -- intermediate CAs are cryptographically scoped to their environment.

Permitted DNS Excluded DNS IP Ranges CRITICAL ext
X.509 + JWT

SPIFFE Identity

Issue X.509-SVID and JWT-SVID identities for workloads. Every service gets a cryptographically verifiable identity -- no more service account passwords or shared API keys.

X.509-SVID JWT-SVID SPIFFE URI SAN
RFC 8555

ACME Automation

Built-in ACME server compatible with Certbot, cert-manager, and any RFC 8555 client. Workloads request and renew certificates automatically with no human involvement.

Certbot cert-manager Let's Encrypt
Revocation

OCSP and CRL

Real-time OCSP responder and periodic CRL distribution. Revoke a certificate and the change propagates immediately -- no waiting for cache expiry.

OCSP stapling CRL distribution Instant revoke

Cryptographic Boundaries, Not Policy Alone

Name Constraints are not soft policy -- they are a CRITICAL X.509 extension. Any certificate authority in the chain that tries to issue a certificate outside its permitted scope will be rejected by every compliant TLS stack.

Every CA key is stored with envelope encryption (AES-256-GCM). The key encrypting key is backed by your chosen KMS -- AWS KMS, Azure Key Vault, HashiCorp Vault, or a PKCS#11 HSM. The private key never leaves hardware in hardware-backed configurations.

Root CA
Intermediate CA
Leaf Cert

Ready to take control of your PKI?

Deploy CoreLink and manage your entire certificate authority hierarchy -- from root of trust to automated leaf renewal -- from one platform.