> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/getting-started/setup/4.-going-live.md).

# 4. Going Live

With a published journey selling your product set, the last step is making it reachable under your own brand and turning it on.

{% embed url="<https://youtu.be/H2_Xpu8BirY>" %}

**Point your branded domain**

By default your storefront runs on a PeakCommerce URL. To serve it under your own domain:

1. Go to **Settings → Domains** and add your hostname.
2. Map it to the surface it should serve — your storefront journey, or your account portal.
3. Follow the prompts to verify the domain.

**Activate**

Set your journey's status to **active** so it's live to customers, and confirm its pages are published. Pointing a domain and activating a journey are the load-bearing "go-live" steps — they change what real customers see, so do them deliberately.

**A quick launch checklist**

* Billing connected and catalog synced.
* Product set assembled with the right plans and add-ons.
* Journey points at the product set; pages published.
* Branded domain mapped and verified.
* Journey set to active.

**Learn more:** [Domains](/product/settings/organization/domains.md).

**You're live.** For ongoing help, see [Intro to Support](/product/getting-started/project-prep/4.-intro-to-support.md) — and explore the rest of the documentation to go deeper on pricing, self-service, rules, and more.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.peakcommerce.com/product/getting-started/setup/4.-going-live.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.