Domains and plain HTTP
Every app gets an address as soon as it is created. You choose, per app, between our domains and your own.
During the early beta apps get
https://<name>.apps.beta.kaviris.com.kaviris.appandkaviris.cloudare coming: the routing, certificates and cookie separation for them are built, but the domains are not live yet. Your own domain is being switched on during the beta too.
Which address an app uses, and whether plain HTTP is allowed, is a field in
its contract (hostname, plainHTTP). You pick one of:
<name>.kaviris.app: HTTPS only. The right choice for almost every app.<name>.kaviris.cloud: HTTPS by default, plain HTTP if you opt in.- Your own domain, such as
www.example.com, pointed at Kaviris.
Our domains
| Domain | Address | HTTPS |
|---|---|---|
kaviris.app |
https://<name>.kaviris.app |
Always. Browsers refuse plain HTTP for every .app address |
kaviris.cloud |
https://<name>.kaviris.cloud |
By default; plain HTTP can be allowed |
The name is one label (recipes, not shop.recipes). It is the one you
chose when you created the app, and it stays yours; a name another app
already holds, or one Kaviris keeps for itself, is refused. Certificates are
handled for you.
Apps on our domains are kept apart from each other: an app cannot set
cookies for the whole kaviris.app or kaviris.cloud domain, so one app
cannot read or overwrite another app's cookies.
Your own domain
Point your domain at Kaviris and your app answers on it, with a certificate made automatically.
- Add the domain to your app (in the portal, or ask your agent).
- Kaviris shows you the DNS records to create:
- For a name like
www.example.com: aCNAMErecord to the target Kaviris gives you (<id>.domains.beta.kaviris.com). - For a bare domain (
example.com), which can't have a CNAME: aTXTrecord_kaviris.example.comwith the value Kaviris gives you (kaviris-verify=<id>), plus anALIAS,ANAMEorArecord pointing at Kaviris (some DNS providers call it "CNAME flattening").
- For a name like
- Once the records resolve, Kaviris gets a certificate and the app is live on your domain over HTTPS.
The records prove the domain is yours. Because they name your account, no one else can claim your domain on Kaviris, even if it already points at us. Once verified, Kaviris doesn't check again, so a short DNS hiccup won't take your site down. If a domain changes hands, ask support to release it.
Your own domain is a separate site, so the cookie separation above is not needed there and not applied.
Custom domains will be a paid feature after the beta.
Plain HTTP
By default every app is HTTPS only: a visitor who types http:// is
redirected to https://. That is what you want for almost every app.
Some devices can't do HTTPS: old hardware, some microcontrollers, a few
embedded clients. For them you can allow plain HTTP on an app, on
kaviris.cloud or your own domain (never on kaviris.app). It is a field in
the contract, plainHTTP: true, and turning it on counts as a
change that needs approval. On kaviris.app the setting is ignored, and the
app's status says so.
Without plain HTTP, a visitor on http:// is redirected, and browsers are
told to use HTTPS for a year (HSTS). With it, http:// serves the app and
that instruction is left out.
With plain HTTP anyone on the network path can read and change the traffic. Never allow it for an app with logins, personal data or payments.