Addresses, subdomains and HTTPS on blitz.cloud

How your blitz.cloud address and app subdomains work, the naming and rename rules, automatic Let's Encrypt certificates, and the status of custom domains.

Every blitz.cloud account gets one free main address, <name>.blitz.cloud, and each app gets a subdomain under it, like blog.<name>.blitz.cloud. HTTPS is automatic: a Let's Encrypt certificate covering your address and all its subdomains is ordered when you claim the address and renewed without you doing anything. Custom domains are not available yet.

Your main address

You claim it once, during onboarding.

Rule	Value
Length	3 to 30 characters
Allowed characters	`a-z`, `0-9` and `-`
Hyphens	Not at the start or end, never two in a row
Reserved	Platform, mail and DNS words, brand names and some profanity
Per account	One

The field checks availability as you type.

Subdomains for apps

Each app lives on its own subdomain: <app>.<name>.blitz.cloud. You can have as many as you have apps, and one app can use the main address itself instead.

Subdomain names are 1 to 30 characters: lowercase letters, digits and hyphens, not starting or ending with a hyphen and never two in a row. A short list is reserved because we may serve something there for you later or because it would look official: www, api, mcp, admin, login, auth, status, mail, db, database and a few more. The dashboard tells you when you pick one.

You can rename or move an app's subdomain on the app page. The old one stops answering right away.

Renaming your main address

You can rename your main address at most once every 14 days, counted from when you claimed it or last renamed it. So the earliest first rename is 14 days after signup.

When you rename:

Your apps move to the new name automatically. A certificate for the new name is ordered at the same time and, like the first one, takes a little while to be ready.
The old name stops answering. Links other people saved will fail rather than reach someone else's app.
The old name is held for 30 days. Nobody else can claim it, and you can take it back in that window.

HTTPS and certificates

Each account gets one wildcard certificate from Let's Encrypt for <name>.blitz.cloud and *.<name>.blitz.cloud. It is requested with a DNS-01 challenge when you claim your address, and cert-manager renews it before it expires.

All HTTP requests are redirected to HTTPS.
Getting the first certificate takes a little while. Until it is ready, a browser shows a certificate warning, and the Domains page says whether yours is live yet.
You don't upload or configure anything. There's also no way to bring your own certificate.

Custom domains

Not yet. Connecting a domain you own, with DNS verification and an automatic certificate, is planned. The free plan will include one custom domain. See what's live for the order things are shipping in.

Until then, a common workaround is a redirect from your own domain to the blitz.cloud address at your DNS provider or registrar.

Advanced DNS records

Adding your own A, CNAME, TXT or MX records under your blitz.cloud address is also planned and not available yet.