Every deployment serves HTTPS. There’s nothing to buy, upload, or renew.

How a certificate is issued

  1. You deploy an app or connect a custom domain.
  2. A certificate is requested and validated over DNS automatically.
  3. It’s installed on the service — typically within minutes of DNS resolving to the app.

Renewal is automatic too. No calendar reminders, no expired-certificate pages.

Certificate still pending?

Check in order:

  1. Is DNS pointing at the app? The certificate can’t validate until the domain resolves to your deployment.
  2. Has DNS propagated? Changes can take 24–48 hours when records were previously cached with long TTLs. Planning a switch? Lower the TTL to 300 a day in advance.
  3. Still stuck after propagation? Open a support ticket with the domain name.

The rest of the stack

Transport encryption is one layer. Connections use TLS 1.2 or higher, stored data is encrypted at rest, and your workloads run isolated from every other tenant’s. The security page covers the full picture. Report suspected vulnerabilities through a support ticket or contact form — privately, before any public disclosure.