Sign code from your CI/CD pipeline — no hardware token required
eSigner for Code is SSL's cloud HSM-backed code signing service. Sign Windows executables, drivers, installers, and scripts directly from GitHub Actions, Jenkins, Azure DevOps, and other CI/CD platforms — using an EV-level cloud HSM, without shipping hardware tokens to build servers or developers.
Two eSigner products — make sure you're in the right place
| eSigner for Code | eSigner for Documents | |
|---|---|---|
| What it signs | Executables, drivers, installers, scripts | PDFs, contracts, official documents |
| How you use it | CI/CD pipeline via eSigner CKA | eSigner Express web app or CSC API |
| Certificate required | Code Signing (IV, OV, or EV) | Document Signing (IV, OV, or IV+OV) |
| You’re here if… | You’re a developer or DevOps engineer signing software releases ✅ | Go to eSigner for Documents → |
What is eSigner for Code?
Traditional EV Code Signing requires a physical USB hardware token — a problem for modern CI/CD pipelines. eSigner for Code solves this by hosting your private key in SSL’s FIPS 140-2 validated cloud HSM. You sign code via SSL’s signing API or the eSigner CKA (Crypto Key Adapter), which integrates directly with standard signing tools like signtool.exe.
eSigner for Code enables:
EV signing without hardware
Cloud HSM satisfies CA/B Forum EV requirements — sign with EV certificates in headless build environments, no USB token.
CI/CD native integration
eSigner CKA integrates with signtool.exe — works in any pipeline that supports standard Windows signing.
Authenticode-compatible formats
.exe, .dll, .msi, .cab, .sys, .ps1, and more — any format accepted by the Windows Authenticode toolchain.
Automated headless signing
Sign in fully automated build environments without user interaction — private key never leaves SSL's cloud HSM.
Key Benefits
No hardware token required
Private key stored in SSL's cloud HSM — no USB tokens, no shipping, no token management.
CI/CD native
eSigner CKA integrates with signtool.exe — works in any pipeline that supports standard Windows signing.
EV-grade signing in automation
Cloud HSM satisfies CA/B Forum EV requirements — sign with EV certificates in headless environments.
FIPS 140-2 validated HSM
Keys stored in a FIPS 140-2 validated cloud HSM operated by SSL.
Sign from anywhere
Sign from any internet-connected build environment — cloud, on-premises, or hybrid.
Any Authenticode-compatible format
.exe, .dll, .msi, .cab, .sys, .ps1, and more — all formats accepted by signtool.exe.
CI/CD Integrations
eSigner CKA is compatible with all major CI/CD platforms that support signtool.exe or standard signing APIs:
| Platform | Integration method | KB article |
|---|---|---|
| GitHub Actions | eSigner CKA + signtool.exe in workflow | Cloud Code Signing Integration with GitHub Actions |
| Jenkins | eSigner CKA in build step | Cloud Code Signing Integration with Jenkins CI |
| Azure DevOps | eSigner CKA as pipeline task | Azure DevOps Cloud Signing Integration Guide |
| CircleCI | eSigner CKA in orb or step | Cloud Code Signing Integration with CircleCI |
| GitLab CI | eSigner CKA in runner | Cloud Code Signing Integration with GitLab CI |
| TeamCity | eSigner CKA in build configuration | How to Integrate eSigner CKA with CI/CD Tools |
| Custom scripts | CSC API for direct REST integration | Cloud Code Signing Automation · Automate EV Code Signing with signtool.exe |
How It Works
1 — Purchase certificate
Buy an IV, OV, or EV code signing certificate from SSL.
2 — Enroll in eSigner
Enroll your certificate in the eSigner cloud signing service — a separate subscription.
3 — Install eSigner CKA
Install the eSigner CKA (Crypto Key Adapter) on your build server or in your CI/CD environment.
4 — Configure pipeline
Add a signing step to your CI/CD pipeline using signtool.exe with the eSigner CKA.
5 — Sign automatically
Every build triggers a signing request — private key never leaves SSL's cloud HSM.
Purchase & Pricing
1. Select Code Signing Certificate
2. Select Key Storage & Delivery
eSigner Cloud Signing
Sign anywhere using eSigner.com. No hardware required.Select the monthly or annual signature volume tier. Any unused signatures will roll over into the next month or year if there is an active certificate. Each tier provides a certain number of included credentials which are pre-selected based on the selected tier. Extra credentials can be purchased at $20 per month. New certificates will receive 30-days free of eSigner cloud signing. After the first 30 days, your monthly or annual subscription fees will be applied. For multi-year subscription discounts, high-volume signature packages and custom solutions, please contact sales.
YubiKey
Physical TokenStandard
3ā5 business days after validation (Continental US)Express + $329.00
1 day after validationBring Your own Cloud HSM
Self-managed infrastructureSSL.com must attest your key to your chosen provider before issuing the certificate. This fee is a one-time charge per order.
What is attestation? Before issuing your certificate, SSL.com verifies that your private key was generated and is stored inside your cloud HSM ā not exportable to software. This one-time attestation fee covers the verification process with your chosen provider.
Looking for a simpler option? SSL.com eSigner for Code provides cloud-based signing with no HSM to provision, no attestation fee, and a lower total cost for most teams.
Enterprise Solutions
SSL.com manages your HSM. Ideal for enterprise compliance.Managed HSM in a custom project. Please contact sales.
3. Validation Speed (optional)
Choose how quickly your organization or identity is validated before your certificate is issued.
Standard
3ā5 day validation Ā· 2ā3 day US shipping Validation completed after all agreements, entity info submitted, and a successful callback to a listed phone number. International shipping tracked; delivery subject to customs. IncludedExpedited
2 business day validation Ā· overnight US delivery 2 business days priority validation from first complete submission and callback. Token shipped overnight in continental US. +$599.00Order Summary
Compliance & Standards
CA/B Forum EV Code Signing
Cloud HSM satisfies FIPS 140-2 requirement for EV private key storage — accepted by all major CAs.
FIPS 140-2
SSL's cloud HSM is FIPS 140-2 validated. Keys generated and stored in certified hardware, never exported in plaintext.
CSC API
SSL implements the Cloud Signature Consortium API for programmatic signing integration and enterprise automation.
Frequently asked questions
Yes — eSigner is a signing service that works with a code signing certificate. You purchase the certificate (IV, OV, or EV) first, then enroll it in eSigner separately.
Yes — this is a primary use case. eSigner's cloud HSM satisfies the FIPS 140-2 hardware requirement for EV private key storage, so you get full EV-grade trust without a physical USB token.
eSigner CKA is a Windows component that wraps signtool.exe. For Linux-based signing, use the eSigner CSC API directly. Contact SSL for guidance on cross-platform signing workflows.
No — you want eSigner for Documents. It supports PDF signing via the eSigner Express web app and high-volume automated signing via eSealing.
IV (Individual Validated), OV (Organization Validated), and EV (Extended Validation) code signing certificates from SSL are all compatible. EV is the most common choice for CI/CD pipelines as it provides instant SmartScreen reputation.
Ready to sign code from your pipeline?
Related products
EV Code Signing
Instant SmartScreen reputation and kernel-mode driver signing — most commonly used with eSigner for Code.
OV Code Signing
Organization-validated code signing compatible with eSigner for Code — ideal for standard software distribution.
eSigner for Documents
Sign PDFs, contracts, and official documents via eSigner Express or automate at scale with eSealing.