> For the complete documentation index, see [llms.txt](https://argos-ci.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://argos-ci.com/docs/learn/deployments/urls-and-domains.md). # URLs and domains Every deployment is reachable through one or more URLs. The exact URLs depend on the deployment's environment and the project's configuration. All deployment URLs are served from the shared root domain `argos-ci.live`. ### Deployment URL Every deployment has an **immutable deployment URL** that always points to that exact build. It looks like: ``` https://--.argos-ci.live ``` For example: `https://storybook-gdhgxamjo-argos-ci.argos-ci.live` The deployment URL never changes and never moves. It's the safest URL to share when you want a stable reference to a specific build—for example, in a pull request review or a bug report. ### Branch URL In addition to the deployment URL, each deployment registers a **branch URL** that follows the latest deployment on that branch: ``` https://--.argos-ci.live ``` For example, on a branch named `fix-stripe`: `https://storybook-fix-stripe-acme.argos-ci.live` When you push a new commit on the same branch and re-deploy, the branch URL is updated to point at the new build. The previous deployment is still available at its own deployment URL. Branch names containing characters that are not URL-safe are slugified. {% hint style="info" %} Branch URLs are useful in pull request templates and review checklists: a reviewer can bookmark the same link and always see the latest version of a feature. {% endhint %} ### Production domain Production deployments are additionally served on the project's **production domain**: ``` https://.argos-ci.live ``` The production domain is shared across all production deployments. When a new production deployment is promoted, the domain immediately starts serving the new build—older production deployments stay reachable on their own deployment URLs. #### Configure the production domain The production domain slug defaults to your project name. You can change it in **Settings → Deployments → Production domain**.

Project Settings → Deployments → Production domain.

Rules for the slug: * Lowercase, up to 48 characters. * Must start and end with an alphanumeric character. * Dashes are allowed in the middle. The final domain is `.argos-ci.live`. {% hint style="warning" %} Changing the production domain takes effect immediately. Any existing links that used the previous domain will stop resolving. {% endhint %} ### Summary | URL type | Stability | When it exists | | ----------------- | ------------------------------------------------------ | --------------------------- | | Deployment URL | Immutable — always points at one build | Every deployment | | Branch URL | Updates when a new deployment lands on the same branch | Every deployment | | Production domain | Updates when a new production deployment is promoted | Production deployments only | All URLs above appear in the **Deployments** tab of your project in Argos.

The Deployments tab shows the deployment URL, branch URL, and—for production—the production domain.

### Related * [Environments](/docs/learn/deployments/environments.md) — How preview vs production is decided. * [Access protection](/docs/learn/deployments/access-protection.md) — Restrict who can open these URLs. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://argos-ci.com/docs/learn/deployments/urls-and-domains.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.