> For the complete documentation index, see [llms.txt](https://docs.codewords.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codewords.ai/website-builder/get-started/publishing.md).

# Publishing

Publishing with CodeWords is a fast, conversational process. You do not need to manage servers, deployment pipelines, or hosting configuration manually.

\
When you are ready, you tell Cody to go live, and Cody handles the production deployment flow for you.

## The publishing process

1. **Finish and test in preview:** Use the in-product preview to click through the app, forms, and navigation.
2. **Tell Cody you are ready to go live:** When you want to publish, say so in chat or click the publish button.
3. **CodeWords handles it**: CodeWords runs the deployment process for you, including:

* Provisioning hosting for your live app at **your-name.codewords.run** on cloud.
* Building and deploying a production-ready version of what you shipped from chat.
* Serving it over HTTPS on that managed URL, without you configuring certificates for the default domain.
* Custom domain setup from the UI after publish (see [Custom Domain](/website-builder/features/custom-domain.md))

In most cases your app is live within minutes. Updates work the same way as building: tell Cody what to change, check the preview, then go live again when you are ready.

## Custom Domains

After your project is published, you can connect a domain you already own so your app is available at something like `app.yourbrand.com` instead of only `*.codewords.run`.

{% hint style="info" %}
Custom domains are a **paid feature**, available on the **Pro**, **Business**, and **custom** plans. Free plan users need to [subscribe to a plan](https://codewords.agemo.ai/account/wallet) first.
{% endhint %}

From the UI:

1. Click **Add custom domain** and enter your domain.
2. Add the DNS record CodeWords shows at your domain provider (GoDaddy, Namecheap, Cloudflare, and others).
3. Click **Verify** in CodeWords. Once verified, your app is live on that domain.

DNS propagation can take a few minutes, and in some cases up to 48 hours. For the full walkthrough, troubleshooting, and record examples, see [Custom Domain](/website-builder/features/custom-domain.md).

Typical records at your provider:

For a subdomain (for example `app.mycompany.com`):

* Type: `CNAME`
* Name: `app`
* Value: `cname.vercel-dns.com` (or the value shown in CodeWords)

For a root domain (for example `mycompany.com`):

* Type: `A`
* Name: `@`
* Value: use the exact value shown in CodeWords for your project

## Automatic SSL / HTTPS

SSL is provisioned automatically once your custom domain is connected.\
Traffic is encrypted by default. There is nothing extra to configure.

## Updating a live app

Publishing is not the end of editing.\
Describe the changes you want, review them in preview, then publish the updated version.\
There is no separate redeploy workflow outside that same preview → publish loop.<br>


---

# 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.codewords.ai/website-builder/get-started/publishing.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.