Publishing
Build, test and go live
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
Finish and test in preview: Use the in-product preview to click through the app, forms, and navigation.
Tell Cody you are ready to go live: When you want to publish, say so in chat or click the publish button.
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)
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.
From the UI:
Click Add custom domain and enter your domain.
Add the DNS record CodeWords shows at your domain provider (GoDaddy, Namecheap, Cloudflare, and others).
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.
Typical records at your provider:
For a subdomain (for example app.mycompany.com):
Type:
CNAMEName:
appValue:
cname.vercel-dns.com(or the value shown in CodeWords)
For a root domain (for example mycompany.com):
Type:
AName:
@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.
Last updated
Was this helpful?