Certum cloud code signing
Code Signing Certificates
Identify your software’s publisher and help users verify that signed code has not been changed. Compare Standard and EV options for your release workflow.
Standard from $99/year
Verified publisher
Identity verification before issuance.
Cloud signing key
SimplySign access without a shipped USB token.
Check your release workflow
Windows Authenticode and Java signing with compatible tools.
Standard or EV: choose for your requirements
| Requirement | Standard | EV |
|---|---|---|
| Applicant | Eligible individuals or organizations | Organizations requiring extended validation |
| Identity checks | Subscriber and applicable organization checks | Extended organization and representative checks |
| Signing key | Certum SimplySign cloud service | Certum SimplySign cloud service |
| SmartScreen | Reputation warnings can still occur | Reputation warnings can still occur |
| Typical decision | General software distribution | EV procurement or hardware-program requirements |
| One-year service | $99 USD | $299 USD |
Read the EV versus OV comparison · EV product details and requirements
Choose your code signing service
Prices below are total service-term prices in USD. Certificate issuance requires CA approval.
Standard Code Signing
For eligible individual developers and organizations.
$99 USD total / 1 year
- Identity verification before issuance
- Certum SimplySign cloud signing
- No USB token shipped
- Windows Authenticode and Java workflows
Applicable taxes and the final payable amount are shown at checkout. 30-day refund policy.
EV Code Signing
For organizations that need extended validation.
$299 USD total / 1 year
- Extended organization verification
- Certum SimplySign cloud signing
- No USB token shipped
- Timestamp compatible signing
Applicable taxes and the final payable amount are shown at checkout. 30-day refund policy.
All service terms and prices
Who can buy, how it is delivered and how long it takes
A Standard code signing certificate from My-SSL is a Certum certificate for eligible individual developers and organizations and costs $99 USD for a one-year service term; the EV code signing certificate is issued to organizations only and costs $299 USD for one year. Both certificates are delivered through Certum’s SimplySign cloud service: the signing key stays on a virtual cryptographic card in Certum’s cloud, the SimplySign mobile app generates the access code and SimplySign Desktop connects your computer to that card, so no physical card or reader is needed and no USB token is shipped.
Before it issues a code signing certificate, Certum verifies the applicant’s identity; for an organization it also asks for a company registration document when the company is not listed in a registry. As of October 2026, Certum’s listed issue time is 1–5 days for a Standard and 1–7 days for an EV code signing certificate; incomplete or inconsistent documents can extend it.
- What an individual sends. For an individual applicant, Certum’s document list names identity verification, with automatic verification as the recommended method, and a utility bill issued to the applicant.
- Signing limit. Certum sets a usage limit of 5,000 signatures per month for cloud code signing certificates, Standard and EV alike, and says that exceeding it may lead to contact about the excess and to the product being blocked for that month.
From order to your first signed release
- Choose the applicant and term. Check individual or organization eligibility and your distribution requirements.
- Complete verification. Supply the requested identity and organization documents. Incomplete or inconsistent records can delay issuance.
- Activate SimplySign. Set up the required applications and authorized operator access after issuance.
- Sign, timestamp and verify. Test the signature on your release artifact and the target platform before distribution.
Publisher identity and SmartScreen reputation
A valid signature identifies the verified publisher and helps detect changes to signed code. Both Standard and EV signed files can still receive SmartScreen reputation warnings. EV does not guarantee a warning-free first download.
Check the format and distribution platform
| Distribution | What to check |
|---|---|
| Windows applications | Authenticode signing for formats such as EXE, MSI and DLL, using a compatible signing tool. |
| Java packages | JAR signing uses Java tooling and the receiving environment’s trust policy. |
| Native macOS distribution | Requires Apple’s Developer ID and notarization workflow; this certificate does not replace it. Apple requirements. |
| Linux and Android packages | Use their package ecosystem’s signing and trust requirements; a commercial certificate is not universally required. |
The operating system used to sign a file is different from the platform that will trust that file. Read the macOS guide.
Cloud signing and release automation
Certum SimplySign keeps the signing key in its cloud service. Its mobile and desktop applications connect an authorized operator to the certificate. You do not receive an exportable PFX or a USB token with this cloud offer. Confirm your build runner, operator access and authentication requirements before purchasing for unattended CI/CD.
Service term, reissues and timestamps
A two- or three-year purchase covers a service term, not one certificate valid for that entire period. Certum limits individual code signing certificates to 459 days from 27 February 2026 and provides reissues within longer product terms. Complete each reissue before the current certificate expires.
A trusted timestamp can allow a signature made while the certificate was valid to remain verifiable after expiry. Revocation, algorithms and platform trust policies still matter. Renew or reissue before signing new releases after expiry.
Confirm the fit before you buy
Tell us your country, applicant type, signing tool, build runner and release deadline. We can help you check the order requirements. Country eligibility, validation timing and automation constraints should be confirmed for your case.
Frequently Asked Questions
Answers to common questions about certificates and our services.
Should I choose Standard or EV code signing?
Choose based on applicant eligibility and the requirements of your customers or distribution platform. Standard is available for eligible individual developers and organizations; EV requires extended organization verification. Neither option guarantees removal of SmartScreen warnings.
What is included in the price?
The listed USD amount is the total for the selected Certum cloud code signing service term. SimplySign provides cloud key access without shipping a USB token. Longer service terms require certificate reissues. Review the final amount, applicable taxes and billing terms at checkout.
How quickly can I start signing?
Certificate issuance follows identity and, where applicable, organization verification. Timing depends on complete documents and the issuing CA’s checks. Contact support with your country, applicant type and deadline before placing an urgent order.
Can I use this certificate for macOS applications?
This certificate does not replace Apple Developer ID or notarization for native macOS distribution. The operating system used to sign a file is different from the trust requirements of the platform where it is distributed.
Can I use the cloud certificate in CI/CD?
Check SimplySign client support and operator authentication against your build environment. Cloud key storage does not automatically mean unattended signing. Confirm your workflow and any usage constraints before buying.
How do I request support or a refund?
Contact My-SSL through the shop support ticket system and include your order number. Our published refund policy provides a 30-day request window; review that policy for the process and payment-provider details.