Domains and HTTPS
An address at the first deploy, and your domain when you want
Every app gets a suracloud.app address. On paid plans, point your own domain: once verified, it answers right away, with HTTPS.
The documentation is in Portuguese for now.
www.minhaloja.com.br
HTTPS on
Records to create in your DNS
| Type | Name | Value |
|---|---|---|
| TXT | _sura-challenge.www | sura-verify=7f3c… |
| CNAME | www | minhaloja.suracloud.app |
What comes with it
suracloud.app address
Each app answers at name.suracloud.app, on a domain separate from the dashboard, so an app can never touch your account cookies.
Your domain, no new deploy
Create the TXT and CNAME records, click Verify and the domain starts answering right away.
Proof of ownership
A domain is only wired after the TXT record proves it. Pointing DNS at Sura is not enough to take anyone’s domain.
HTTPS on every domain
Each domain gets its own certificate, so a slow DNS does not hold the others back.
Routes between apps
Send your site’s /api to the backend app, on the same address and with no CORS.
Checked every day
Sura checks the TXT record every 24 hours. A domain that changed hands stops being served to the old owner.