Certum Code Signing Certificates

Compare Certum Open Source, Standard and EV Code Signing certificates to choose the right validation level, price and signing method for your software.

Open SourceStandardEVSimplySign Cloud

€25 Open Source

€139 Standard

€329 EV

Current displayed starting prices. Delivery method, product term and signing infrastructure can change the final price.

Visit Certum

Three Certum Certificates, Three Different Use Cases

Certum's current range is easiest to understand by separating the certificate choice from the key management choice. Open Source, Standard and EV represent different validation and audience requirements, while a cryptographic card or SimplySign determines how signing credentials are protected and used.

OPEN SOURCE

Certum Open Source Code Signing

€25

Designed for eligible open source developers and project maintainers who need to sign distributed releases under a verified developer identity.

Explore Open Source Code Signing

STANDARD

Certum Standard Code Signing

€139

General purpose Code Signing for developers and organizations distributing commercial applications, Windows software and signed installers.

Explore Standard Code Signing

EXTENDED VALIDATION

Certum EV Code Signing

€329

Extended Validation for organizations that need a higher level of publisher verification and the additional assurance associated with EV.

Explore EV Code Signing

Certum Code Signing Pricing

The displayed starting prices vary according to whether you already have compatible cryptographic infrastructure, choose a Certum card or use SimplySign cloud signing.

Product	Electronic certificate	With cryptographic card	Cloud
Open Source	€25	€69	€49
Standard	€139	€169	€209
EV	€329	€359	€379

The electronic certificate option assumes the customer already has the required cryptographic infrastructure. Card based products include the applicable Certum cryptographic card, while cloud products use SimplySign.

Compare Code Signing Certificate Options

Compare validation levels, use cases and purchasing considerations before choosing a certificate for your software releases.

Compare Certificate Options

How the Certum Product Range Compares

The core difference is validation and intended audience. All three can support software signing, while EV provides the highest validation level in this Certum range.

Feature	Open Source	Standard	EV
Primary audience	Open source developers	Developers and organizations	Organizations
Validation	Open Source	Standard	Extended Validation
Starting price	€25	€139	€329
Cryptographic card	Available	Available	Available
Cloud signing	Available	Available	Available
SimplySign	Available	Available	Available
Software signing	Yes	Yes	Yes
Windows signing	Supported	Supported	Supported
Java signing	Supported	Supported	Supported
Highest validation level	No	No	Yes

SimplySign Changes How You Operate the Signing Key

SimplySign is Certum's cloud based signing option. It should be understood as a key storage and signing delivery method rather than a fourth certificate category.

Standard Cloud

From €209

Use SimplySign when Standard Code Signing needs to be available remotely without physically connecting a cryptographic card and reader to the signing machine.

EV Cloud

From €379

Use SimplySign when an EV signing workflow needs cloud based delivery and the operational convenience of remote signing.

Certificate type and signing method are separate decisions.

First choose Open Source, Standard or EV according to the validation requirement. Then choose a cryptographic card or SimplySign according to how your team needs to sign.

Physical Cryptographic Card or Cloud Signing?

Certum supports both traditional hardware based signing and SimplySign cloud signing. The better option depends on where signing occurs and how often software is released.

Cryptographic card

A physical card protects the signing credentials and is suited to developers and organizations that prefer hardware based signing. The operational tradeoff is that the card needs to be available whenever signing is performed.

SimplySign

Cloud signing removes the need to physically connect a card and reader to the signing machine. It can be more practical for remote teams, automated releases and distributed build infrastructure.

Certum Code Signing Validity in 2026

Longer product purchase terms should not be confused with the validity period of one individual Code Signing certificate.

Newly issued Code Signing certificates have a maximum validity of 459 days.

Certum can still sell products with longer purchase terms, but certificates must be reissued during the purchased term to comply with the applicable validity limit.

This distinction is especially important when comparing current Certum products with older pages that describe two or three year certificates as if one certificate remains valid for the entire purchase period.

Certum Code Signing for Windows

Certum Code Signing supports common Windows software signing workflows and can be incorporated into a standard release process using supported signing tools.

EXE

Sign supported Windows executable files and establish a verifiable publisher identity.

DLL and MSI

Protect supported libraries and installers with digital signatures before distribution.

CAB and other binaries

Use Code Signing across other supported Windows binary formats according to the signing requirements of your software.

BuildTestSignTimestampVerifyRelease

Certum's documentation provides signing guidance for tools including Microsoft SignTool.

Certum Code Signing for Java

Certum also supports Java signing workflows, making the product range relevant to teams distributing Java applications and other Java based software.

Jarsigner support

Certum documentation references Jarsigner for Java signing. This gives Java developers a supported workflow alongside Windows based signing tools.

Certum Code Signing and SmartScreen

A Code Signing certificate establishes publisher identity and allows software integrity to be verified, but it should not be presented as a guaranteed way to eliminate Microsoft SmartScreen warnings.

Do not market Certum EV as a guaranteed SmartScreen approval or warning removal mechanism.

SmartScreen reputation is a separate Microsoft security mechanism and can depend on factors such as software download and distribution history.

Certum Code Signing in a CI/CD Pipeline

Cloud based signing can become particularly useful when signing is part of an automated release process and build infrastructure is distributed across teams or environments.

Source CodeBuildAutomated TestsSecurity ChecksSignTimestampVerifyRelease

Frequent releases

Cloud signing can remove repeated physical card handling from high frequency release workflows.

Distributed teams

Remote signing can be more practical when developers and build systems operate across locations.

Automated deployment

SimplySign can fit workflows where signing needs to happen as part of an automated release process.

Enterprise infrastructure

Cloud based delivery can simplify signing operations across remote or centralized build environments.

Plan a Cloud Signing Workflow

If signing must run across remote teams or automated build systems, review the design and security considerations for cloud based code signing.

Explore Cloud Code Signing

Which Certum Certificate Should You Choose?

OPEN SOURCE

Choose Open Source

Choose this product if you maintain eligible open source software and need to sign releases under a verified developer identity.

STANDARD

Choose Standard

Choose Standard when you need general purpose Code Signing for software distribution and do not specifically require EV validation.

Choose EV

Choose EV when your organization needs Extended Validation and the additional assurance associated with the EV certificate category.

KEY MANAGEMENT

Choose SimplySign when remote signing matters

Choose the cloud option when you want remote signing and do not want to manage a physical cryptographic card and reader.

Frequently Asked Questions

What are the Certum Code Signing certificate types?

Certum's current range includes Open Source Code Signing, Standard Code Signing and EV Code Signing.

How much does Certum Code Signing cost?

Certum currently lists Open Source Code Signing from €25, Standard Code Signing from €139 and EV Code Signing from €329.

What is the cheapest Certum Code Signing certificate?

The Open Source Code Signing Certificate is currently the lowest priced option, starting at €25. It is intended for eligible open source developers.

How much is Certum Standard Code Signing?

Standard Code Signing currently starts at €139. The card based option starts at €169, while Standard Code Signing in the Cloud starts at €209.

How much is Certum EV Code Signing?

Certum EV Code Signing currently starts at €329. The card based option starts at €359, while EV Code Signing in the Cloud starts at €379.

Does Certum offer cloud Code Signing?

Yes. Certum provides cloud based signing through SimplySign, including Standard and EV Code Signing cloud products.

Do Certum Code Signing certificates require a physical token?

Not necessarily. Certum provides physical cryptographic card based products as well as cloud based signing through SimplySign.

How long is a Certum Code Signing certificate valid?

A newly issued Code Signing certificate can have a maximum validity of 459 days under the current 2026 rules.

Can I buy a two or three year Certum Code Signing product?

Yes, but the purchase term should not be confused with individual certificate validity. Certificates must be reissued during longer service terms to comply with the current maximum validity period.

Does Certum support SignTool?

Yes. Certum provides documentation for signing code with Microsoft SignTool.

Does Certum support Java Code Signing?

Yes. Certum's documentation includes Jarsigner based Java signing workflows.

Find the Certum Certificate That Fits Your Software

Use Open Source for eligible open source projects, Standard for general software signing, and EV when your organization requires Extended Validation. Then choose a cryptographic card or SimplySign according to how your team needs to protect and use the signing credentials.

View Certum Products

Related Code Signing Resources

Use these technical resources to review certificate fundamentals, platform requirements and signing workflows.

What Is Code Signing?

A foundation for understanding publisher identity, integrity and signature verification.

Open resource

Windows Code Signing Guide

Review the Windows signing workflow and supported signing tools.

Open resource

Microsoft Authenticode

Understand the Windows trust model and Authenticode signatures.

Open resource

Java Code Signing Guide

Review signing workflows for Java archives and related packages.

Open resource

Code Signing Timestamping

Understand how trusted timestamps affect signatures after certificate expiry.

Open resource

Automate Code Signing in CI/CD

Plan signing as part of a controlled software release pipeline.

Open resource

Code Signing Certificate Renewal

Understand renewal and reissuance considerations for certificate terms.

Open resource