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 9, 2026.

View as Markdown

You, to your agent: 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

Connect your agent, it takes care of the rest

To paste into your agent

Read while.sh/agents, then deploy my app with while.

Copy the instructions

No account needed to try: your app is live right away. To keep it, sign in.

A project for your company? Talk to the team: hello@while.sh