Skip to content

Go to the docs contents

HTTPS address

Each public web service gets its HTTPS address, certificate included, as soon as it is deployed.

Updated November 21, 2026.

View as Markdown

Automatic HTTPS address for every web service: the closed padlock and the TLS certificate set on the app, with nothing to configure

You, to your AI: Give me the app’s address.

When to use it

Each public web service has one, without doing anything.

How it works

Every public web service gets its HTTPS address, certificate included: https://<project>.while.cloud for the main service in production, https://<project>-<service>.while.cloud for the others, and -<environment> at the end outside production.

What to know

The main service keeps the project’s address, even when another public service arrives. Two addresses that would collide (the project “shop-api” and the api of the project “shop”): the second gets a four-character suffix, and get_app_status says so.

The visitor’s address: X-Real-IP, set by while’s edge (a client’s own is replaced), or the first entry of X-Forwarded-For, which the edge replaces too; the following ones, in varying number, are while’s proxies. Forwarded is rebuilt by while from them: a client’s own does not arrive.

Your agent’s MCP tools

Your agent handles it with the get_app_status tool.

Guides

Give your AI the message, and it takes care of the rest

Give this to your AI

Read while.sh/agents and help me get started with while.

Copy the message

In 3 minutes, with no sign-up, the tool has its own address. To keep it, create your account.

For a company project, write to the while team: hello@while.sh