step-ca
smallstep.com
- Free plan
- Open source
- Windows
- macOS
- Linux
- API
- Self-hosted
What step-ca is
step-ca is an online Certificate Authority for automated management of X.509 and SSH certificates. It issues X.509 certificates for TLS, mutual TLS, document signing, and authentication, as well as SSH certificates for users and hosts. Provisioners can authorize issuance through ACME challenges, OIDC tokens, cloud instance identity documents, or short-lived JWK tokens. Automated issuance and renewal, plus passive revocation, apply to clients, servers, and Kubernetes workloads. Templates can customize names and identifiers, limit domains or key sizes, and create longer certificate chains. For signing-key protection, step-ca integrates with cloud key-management services, HSMs, TPM 2.0, and YubiKey PIV. Its designed architecture has an offline root CA and a configured intermediate CA that issues end-entity certificates. Installation options cover macOS, Windows, Linux, Kubernetes, and Docker. The open-source software is free; community support is available through Discord, with dedicated support contracts from Smallstep. Documented limits include restricted active revocation and legacy-protocol options, no certificate history or metrics, and no ACME External Account Binding.
Who it suits
step-ca is positioned for DevOps teams managing private certificates for infrastructure such as VMs, containers, APIs, databases, Kubernetes pods, and people. It suits teams able to work with a two-tier CA architecture and its documented limitations.
Good to know, and what to watch
- Automates certificate issuance and renewal.
- Issues both X.509 and SSH certificates.
- Supports cloud key services, HSMs, TPM 2.0, and YubiKey PIV.
- Installation options include Linux, Windows, Kubernetes, and Docker.
- Free open-source software.
- Active revocation is limited.
- No certificate history or metrics.
- No ACME External Account Binding.
- Community support is through Discord; dedicated support requires a contract.
Plans
Every plan and priceSmallstep Platform
step-ca (open source)
step-ca open source
Free plan
The Club's review
step-ca is a self-hosted private certificate authority for teams automating trust across infrastructure and people. It is best for DevOps groups comfortable operating PKI who need both X.509 and SSH issuance without a license fee. Its breadth and key-protection options are compelling, while its limited revocation and observability make it a poor fit for teams requiring a complete certificate-lifecycle control plane.
Overview
step-ca uses a two-tier PKI: an offline root anchors trust and a configured intermediate issues end-entity certificates. Keeping the root offline reduces exposure during day-to-day operations, while the intermediate handles automated workloads. The open-source plan includes one configured intermediate, so organizations needing several independent issuing authorities will find that architecture restrictive without additional arrangements.
The service issues X.509 certificates for TLS, mutual TLS, document signing and X.509 authentication. It also issues SSH certificates for users and hosts, including short-lived SSH user certificates through single sign-on. Automation covers issuance, renewal and passive revocation for clients, servers and Kubernetes workloads. That is a strong match for short-lived credentials, but limited active revocation means it should not be treated as a full response system for compromised certificates.
Key features
Provisioners connect issuance to existing identity and deployment controls. ACME challenge responses, OIDC tokens, AWS, GCP and Azure instance identity documents, and short-lived JWK tokens can authorize requests. This gives infrastructure teams alternatives to manually distributing long-lived credentials, with the right method depending on their identity stack.
X.509 and SSH templates can add custom subject alternative names or OIDs, restrict domains or key sizes, and build longer certificate chains. Those controls are useful where policy differs by service, namespace or user rather than applying one broad certificate profile.
CA signing keys can be protected with Google Cloud KMS, AWS KMS, Azure Key Vault, PKCS#11 HSMs, TPM 2.0 or YubiKey PIV. That range supports both cloud-managed and hardware-backed deployments, including environments with stricter key custody requirements. Integrations include ACME, SCEP, OIDC, cloud identity, Kubernetes cert-manager, Nebula and Envoy SDS, while Badger, BoltDB, MySQL and PostgreSQL provide configurable database backends.
Installation covers macOS Homebrew, Windows Winget or Scoop, Linux packages and binaries, Kubernetes and Docker. The hybrid deployment model therefore suits teams placing the CA close to workloads while retaining control of their infrastructure. Documented gaps remain: no certificate history or metrics, no dynamic SCEP, no ACME External Account Binding, and limited legacy-protocol and device-attestation options.
Pricing
step-ca (open source) — free. The free plan includes one configured intermediate CA, an offline root CA and authority-wide issuance policies. It has no Certificate Transparency integration and no ACME EAB. This is an unusually capable option for teams able to run and secure their own service, but the single-intermediate limit and missing operational features matter as deployments grow. Open-source support comes from the user community through Discord; dedicated support contracts are available from Smallstep.
Platforms
step-ca supports API, Linux, macOS, Windows and self-hosted deployments. Official packages, binaries, Kubernetes and Docker options cover conventional servers and containerized environments, while the hybrid model leaves placement and operational responsibility with the adopting team.
Who it's for
It is aimed at DevOps teams running private PKI for VMs, containers, APIs, databases, Kubernetes pods and people. Choose it when broad protocol coverage, automated short-lived certificates and control over CA keys matter more than a managed service or rich reporting. Teams that need active revocation workflows, certificate-history analysis, metrics, dynamic SCEP or stronger legacy and device-attestation coverage should look elsewhere.
Pros and cons
Pros
- Wide credential coverage: X.509 and SSH issuance spans transport security, mutual authentication, signing and human or host access.
- Flexible authorization: ACME, OIDC, cloud identity and JWK provisioners can align issuance with existing systems.
- Strong key-protection choices: Cloud KMS, HSM, TPM and YubiKey integrations support varied custody requirements.
- Useful policy controls: Templates can constrain names and key sizes or add organization-specific identifiers.
- No license cost: The open-source plan is free for self-hosted teams.
Cons
- One configured intermediate: The free plan limits separation between issuing authorities.
- Weak operational visibility: There is no certificate history or metrics.
- Revocation constraints: Active revocation is limited, reducing its fit for incident-response-heavy environments.
- Protocol gaps: Dynamic SCEP and ACME External Account Binding are absent, with limited legacy-protocol and device-attestation options.
- Operational burden: Self-hosting and community-led support require in-house PKI responsibility.
Alternatives
For a broader category view, see Public Key Infrastructure Software.
EJBCA is another free, open-source choice; its Community Edition is positioned for learning, testing and prototyping rather than production.
Choose EZCA when you want paid, FIPS 140-3 Level 2 HSM-backed CAs and a hosted commercial model.
KeyTalk CKMS suits organizations seeking paid on-premise S/MIME licensing by user, including multi-device support.
OpenCA PKI is a free open-source PKI management option for Linux, macOS and self-hosted or web deployments.
OpenXPKI offers a free, fully functional community code base with Debian packages and mailing-list support.
XiPKI is a free Apache License 2.0 project for API and self-hosted deployments.
Keyfactor Platform is the paid alternative when certificate-lifecycle automation at very large scale and commercial support are priorities.
Boulder is a free MPL-2.0 option, but production deployment requires separate implementation and security work.
Verdict
Choose step-ca if you need a free, self-hosted CA that can automate both X.509 and SSH credentials across modern infrastructure and protect signing keys with cloud or hardware services. Look elsewhere if active revocation, certificate history, metrics, dynamic SCEP or managed operational support are central requirements.
The verdict
step-ca provides certificate issuance and automation for private X.509 and SSH use, with several options for protecting CA signing keys. Teams should weigh its documented gaps in revocation, metrics, and ACME support before adopting it.
What the maker publishes
- ACME server
- step-ca provides a private ACME server compatible with ACMEv2 clients and common HTTP-01, DNS-01 and TLS-ALPN-01 challenges. source
- API and SDK
- The project includes a Go wrapper and a command-line client, while a seamless infrastructure-as-code API is listed as a commercial-product feature. source
- Architecture
- step-ca is designed around a two-tier PKI with one offline root CA and one configured intermediate CA issuing end-entity certificates. source
- Automated renewal
- The system automates certificate enrollment and renewal and uses passive revocation for short-lived certificates. source
- Binary architectures
- Precompiled Linux binaries are published for amd64, arm64, armv6, armv7, mips, mips64, ppc64le and 386. source
- Certificate automation
- step-ca supports automated certificate issuance, renewal and passive revocation for clients, servers and Kubernetes workloads. source
- Company facts
- LinkedIn lists Smallstep as privately held, founded in 2016, headquartered in San Francisco and employing 11–50 people. source
- Company legal name
- Crunchbase lists the legal entity as Smallstep Labs, Inc. source
- Database backends
- State storage supports embedded Badger and BoltDB plus MySQL and PostgreSQL key-value backends. source
- Databases
- Its configurable database backends include Badger, BoltDB, MySQL and PostgreSQL. source
- Documentation depth
- Official materials include command references, configuration, provisioners, templates, production guidance, renewal, revocation, integrations and tutorials. source
- Funding
- Crunchbase lists a private Series A and seven investors, including boldstart ventures and Upside Partnership. source
- Independent technical assessment
- DEV.co characterizes deployment complexity as moderate and documentation as strong, while noting that root-key protection remains the operator’s responsibility. source
- Installation
- Official installation options cover macOS Homebrew, Windows Winget or Scoop, Linux packages and binaries, Kubernetes and Docker. source
- Integrations
- The integration ecosystem includes ACME, SCEP, OIDC, AWS/GCP/Azure cloud identity, Kubernetes cert-manager, Nebula and Envoy SDS. source
- Integrations
- Documented integrations include Kubernetes cert-manager, Envoy SDS, ACME clients, OIDC providers, PKCS#11, Google Cloud KMS, AWS KMS and YubiKey PIV. source
- Key algorithms
- Supported certificate key types include RSA, ECDSA and EdDSA, with configurable lifetimes. source
- Key protection
- It integrates with Google Cloud KMS, AWS KMS, Azure Key Vault, PKCS#11 HSMs, TPM 2.0 and YubiKey PIV for CA signing-key protection. source
- License
- The certificates repository is distributed under the Apache-2.0 license. source
- Limitations
- The project documents limited active revocation, limited legacy-protocol and device-attestation options, no certificate history or metrics, no dynamic SCEP and no ACME External Account Binding. source
- Limit: CA hierarchy
- Open-source step-ca supports one configured intermediate CA and does not support multiple issuing CAs or a single-tier PKI. source
- Limit: CLI-oriented workflow
- A self-hosted user describes issuing, downloading and revoking certificates through SSH and the CLI and seeks a phone-friendly interface. source
- Limit: data export
- There is no built-in easy data-export API, and embedded databases must be stopped before scripted export. source
- Limit: pricing
- G2 reviewers describe pricing as concerning or above budget, including a complaint that it is not free after 50 endpoints. source
Checked against the maker's pages on 14 Oct 2026.