A private certificate authority (X.509 & SSH) & ACME server for secure automated certificate management.
step-ca is a private certificate authority (X.509 & SSH) and ACME server designed to provide secure, automated certificate management for DevOps teams and security professionals.
Key Features:
Issues HTTPS server and client certificates compliant with RFC5280 and CA/Browser Forum standards.
Manages TLS certificates for DevOps use cases, including VMs, containers, APIs, databases, and Kubernetes pods.
Supports SSH certificate issuance for user authentication via single sign-on (SSO) tokens or host identity documents.
Enables automated enrollment, renewal, and passive revocation with short-lived certificates.
Integrates with multiple provisioners, including OAuth OIDC, ACME, cloud instance identities, and SCEP.
Acts as an ACME server compatible with popular clients like certbot, acme.sh, and Caddy.
Audience & Benefit:
Ideal for DevOps teams, security engineers, and organizations seeking to simplify certificate lifecycle management. step-ca helps automate PKI operations, reduce manual overhead, and enhance security by enabling short-lived certificates and seamless integration with existing identity providers and infrastructure tools. It supports both X.509 and SSH use cases, making it a versatile solution for modern DevOps environments.
step-ca can be installed via winget, ensuring easy setup and deployment.
README
step-ca
step-ca is an online certificate authority for secure, automated certificate management for DevOps.
It's the server counterpart to the step CLI tool for working with certificates and keys.
Both projects are maintained by Smallstep Labs.
ACME is the protocol used by Let's Encrypt to automate the issuance of HTTPS certificates. It's super easy to issue certificates to any ACMEv2 (RFC8555) client.
Delegate SSH authentication to step-ca by using SSH certificates instead of public keys and authorized_keys files
For user certificates, connect SSH to your single sign-on provider, to improve security with short-lived certificates and MFA (or other security policies) via any OAuth OIDC provider.
For host certificates, improve security, eliminate TOFU warnings, and set up automated host certificate renewal.
The step command reference is available via step help,
on smallstep.com,
or by running step help --http=:8080 from the command line
and visiting http://localhost:8080.
Feedback?
Tell us what you like and don't like about managing your PKI - we're eager to help solve problems in this space. Join our Discord or GitHub Discussions