Code signing for developers and software teams worldwideVerified publishers.   Trusted releases.
Developer guide

Plan your certificate renewal before the next release

Keep validation, private key protection and build configuration in view.

Certificate lifecycle

Plan around the next release.

Certificate lifecycle planning should include expiry dates, applicant verification and the time needed to prepare the signing environment.

Separate subscription and certificate validity.

A multi-year subscription may involve reissuing individual certificates within the subscription period. Confirm the provider’s process rather than assuming one certificate covers the entire subscription term.

Test updated signing credentials.

When a certificate or signing client changes, verify a test release before relying on the new configuration in production.

Renewal checklist.

  • Track the certificate validity period
  • Check updated organization information
  • Prepare provider verification documents
  • Confirm key protection and client compatibility
  • Verify a newly signed test artifact
Explore certificate options ↗