Runex

Feature · Network & security

Automatic SSL certificates, issued and renewed for you.

Automatic SSL means your host gets, installs, and renews TLS certificates without you touching them. Every Runex app is served over HTTPS on *.runex.cloud, and custom domains get their own certificate once DNS points to Runex.

Start deploying →How it works
  • HTTPS from the first deploy
  • Custom domains included
  • Renewal is automatic
shop.acme.com
domain
shop.acme.com
dns
CNAME → cname.runex.cloud
certificate
issued
renewal
automatic
http
redirects to https
automatic sslrunex

Definition

What is an automatic SSL certificate?

An automatic SSL certificate is a TLS certificate the platform provisions and renews for your domain, with no manual steps.

SSL, technically TLS today, encrypts traffic between browsers and your app. Browsers flag sites without it as “Not secure”.

Normally you generate a certificate, install it on a server, and remember to renew it before it expires. On Runex that whole loop is handled for you.

TLS is handled at the Runex edge, so your app only serves plain HTTP on its port inside the container, no certificate files in your code.

How it works

How does Runex issue SSL certificates?

Point DNS, and HTTPS follows.

  1. Runex

    HTTPS URL by default

    Each app gets https://<slug>.runex.cloud.

  2. You

    Add a custom domain

    Create a CNAME to cname.runex.cloud.

  3. Runex

    Issue a certificate

    DNS is verified and a certificate issued.

  4. Runex

    Renew automatically

    Certificates renew before they expire.

Benefits

Why use automatic SSL?

No expired certificates, ever.

Nothing to renew

No calendar reminders or renewal scripts.

HTTPS from day one

Even preview and test apps are encrypted.

Custom domains included

Your own domain gets a certificate too.

Trust and search

Browsers and search engines favor HTTPS.

Compare

Automatic SSL vs manual certificates: what's the difference?

Automatic SSL is set-and-forget; manual certificates are a recurring chore.

Automatic SSL vs manual certificates: what's the difference?
Automatic SSL on RunexManual certificate
SetupPoint DNS, doneGenerate, validate, install on a server
RenewalAutomaticYou track expiry dates
Custom domainsA certificate per domain, includedIssue or buy each one
Failure modeNo surprise expirationsExpired cert = browser warning

Example

Example: moving a store to its own domain

A store moves from its runex.cloud URL to shop.acme.com with HTTPS on day one.

  1. The app is live at https://storefront.runex.cloud
  2. Add shop.acme.com in the Runex dashboard
  3. Create a CNAME to cname.runex.cloud
  4. Runex verifies DNS and issues a certificate
  5. https://shop.acme.com serves the store
  6. Renewals happen automatically from then on
automatic-ssl
before
storefront.runex.cloud
after
shop.acme.com
record
CNAME → cname.runex.cloud
tls
active
renewal
handled by Runex
illustrative namesrunex

FAQ

Questions developers ask

Short answers about automatic ssl. More in the documentation.

Is SSL the same as TLS?

In everyday use, yes. TLS replaced SSL years ago, but certificates are still commonly called SSL certificates.

Do I have to pay for an SSL certificate?

Not on Runex. Certificates for *.runex.cloud URLs and custom domains are included at no extra cost.

Why does my site say “Not secure”?

The page is loading over plain HTTP, or the certificate is missing or expired. On Runex, check that your domain's CNAME points to cname.runex.cloud so a certificate can be issued.

How long does it take to get an SSL certificate?

Usually minutes after DNS resolves correctly. DNS changes themselves can take longer to spread, depending on your provider.

Next step

Ship with automatic ssl today.

Sign up, install the GitHub App, and deploy your first app. It's free to start.

Deploy with Runex →Getting started guide