Your site's temporary domain
Every environment gets its own address under avaloi.com, with HTTPS. Open the site before you point a domain at it, and rename the address to any free name.
Parts of this feature are still being built. The Not yet section lists them.
Every environment gets a temporary domain when Avaloi creates it. You can open the site there before you add your own domain, and staging gets its own.
What it looks like
The temporary domain is your site's name followed by .avaloi.com. For example, a site called Elric gets elric.avaloi.com, and its staging environment gets elric-staging.avaloi.com.
If another site already has that name, Avaloi adds a hyphen and four letters or digits, such as elric-7k2p.avaloi.com. Every address is unique across all sites. Avaloi never hands out names such as www, api, app, mail, docs, or staging on their own.
Open it
- Choose Sites in the sidebar and open the site.
- On Info, choose Visit site. The site opens in a new tab over HTTPS.
The Domains tab and the environment details on Info show the same address. On the Domains tab it is the first row of the table, marked Temporary.
Rename it
You can change the temporary domain to any free name under avaloi.com, with no random suffix.
- Open the site, then Domains.
- Open the menu of the Temporary row and choose Rename temporary domain.
- Type the new name, such as
gallery. The form shows the full address before you save. - Choose Rename.
The name must follow these rules:
- 3 to 40 characters.
- Lowercase letters, digits, and hyphens. It cannot start or end with a hyphen.
- Not a reserved name, such as
www,api,app,mail,docs,status, orstaging. - Not used by any other site. If the name is taken, Avaloi says so and changes nothing.
Renaming is a job. Avaloi adds the new name to Cloudflare DNS, orders a certificate for it, and routes it to your site. It then releases the old name: the DNS record, the routing, and the edge settings for the old name go away, and Avaloi stops managing the old certificate. The old name stops working when the job finishes, and Avaloi does not redirect it. Update any links you shared.
You can rename an environment up to 5 times in 24 hours, because each new name needs its own certificate. You need the permission to manage domains. You can rename a live environment only.
HTTPS
Each temporary domain has its own certificate from Let's Encrypt, and Cloudflare serves it. A new site can take a few minutes to answer on HTTPS while the certificate is issued. The certificate job appears in the job drawer with its own steps.
When you delete an environment
Avaloi removes the address with the environment. A new environment gets a new address, never an old one.
Use the API
PUT /v1/environments/{id}/temp-hostname with { "label": "gallery" } starts the rename and returns the job. It answers 422 for a label that breaks the rules, 409 for a name that is taken, and 429 after 5 renames in a day. An API key needs the sites:write scope and confirm: true.
Add your own domain
The temporary domain stays after you add your own. See Domains to point your domain at the site.
Certificate
The temporary domain has its own Let's Encrypt certificate. Avaloi checks it once a day and orders a new one when less than 30 days remain, so you never renew it yourself.
Not yet
- Avaloi does not yet delete the old certificate files from the server after a rename. The server no longer answers on the old name, and the files expire on their own.
- The hosted MCP server has the same action as the tool
rename_temp_domain, which always asks you first. That server is not open to customers yet. - Test sites run on a simulated server, so their temporary domain does not answer on the internet.
Still stuck?
Email [email protected] with your site name and what you tried, or send us a message.