Development Toolchain

Apply for a developer certificate

Request authority to sign customer licenses for your software products.

Prepare CSR
Submit application
Verify email
Review and certificate delivery

1. Applicant details Request type Development Toolchain order or license reference

Required for new certificates, renewals and additional products. SIGCLEAR checks that this reference matches an active Development Toolchain entitlement for you or your organization before approval.

Existing developer or certificate reference Required for renewal or additional products.

NameEmail

Organization or developer name

2. Products and requested validity Product identifiers, one per line (up to 16)

For example, Acme Analysis Suite → acme.analysis-suite. Use your own lowercase vendor prefix; SIGCLEAR identifiers are reserved. For renewal or expansion, include all products requested for the resulting certificate.

Product names and purpose

Requested certificate expirationIntended customer-license duration

The requested expiration is 00:00 UTC at the start of the selected date. Customer licenses cannot extend beyond the developer certificate's expiration. Approved products and dates may differ from your request.

3. Certificate signing request

A CSR contains your public key and a signed request. Keep your private key and its password on your machine.

Provide exactly one PEM CSR with an ECDSA P-256 key, up to 64 KiB. Private keys and passwords must never be submitted.

Upload CSR file

Paste CSR instead

CSR in PEM format

Use either a file or pasted text, not both.

How to create a CSR

For a new signing key, run these commands in a new, empty private directory. Replace Your Organization and choose a key password when prompted.

umask 077
openssl genpkey -algorithm EC \
  -pkeyopt ec_paramgen_curve:prime256v1 \
  -aes-256-cbc -out developer-key.pem
openssl req -new -sha256 \
  -key developer-key.pem \
  -out developer.csr \
  -subj "/O=Your Organization/CN=License Issuer"

Upload developer.csr. Keep developer-key.pem private. For renewal or additional products, create a fresh CSR using your existing key with the openssl req command, or generate a replacement key in a new directory. Avoid overwriting an existing key.

4. Submit application

After submission, confirm your email to send the application for manual review. Keep your private application link for status updates.

Submission and email verification do not grant signing authority. End users need licenses for the SIGCLEAR products your package uses.

Back to Development Toolchain documentation