Trust signal
Keep your SaaS brand secure
Combine a customer-facing domain alias with a matching SSL certificate so visitors never get a browser warning when they open your SaaS application.
Why SSL + domain alias
Browsers still show our SaaS certificate if a domain alias lacks a matching cert, so visitors encounter NET::ERR_CERT_COMMON_NAME_INVALID. Upload a certificate that matches the alias to keep every session fully branded and warning-free.
- Let’s Encrypt renewals and custom certificates (even wildcards) are self-service in the customer center.
- Store the CSR and private key securely—without that key the certificate cannot be installed.
- Deliver the certificate, key, and CA chain together on the relevant product detail page.
Generate a CSR without a password so our platform can install the certificate later.
Order the certificate, validate the domain via email/Whois, and download the completed certificate.
ERR_CERT_COMMON_NAME_INVALID appears when the certificate does not match the alias.
Upload a custom certificate from the customer center to make the warning disappear.
Create CSR
Use a CSR generator (e.g., your provider’s form) to produce the CSR and private key. Never lose the private key—they are tightly linked to the certificate.
Order certificate
Paste the CSR into the provider form, confirm domain ownership via email/Whois, and download the issued certificate.
Upload files
Provide the certificate, private key, and CA/intermediate chain on the SaaS product page inside the customer center.
Certificate anatomy
When submitting a certificate, send us three elements so the installation is seamless.
- Domain certificate (matching the alias)
- Private key (generated with the CSR)
- CA certificate and any intermediate certificates
You can upload everything through the SSL section on the SaaS product page inside the customer center. We handle the rest and notify you once it’s live.