WaymakerOS Help Center

Put your brand on your Waymaker-hosted apps. Custom domains include automatic SSL provisioning.

How It Works

Setup — Tell Waymaker which domain you want to use
DNS Configuration — Add CNAME and TXT records at your DNS provider
Verification — Waymaker checks your DNS records
SSL Provisioning — Automatic SSL certificate
Active — Your domain is live with full HTTPS

Step-by-Step Guide

1. Start Domain Setup

waymaker host domains setup <app-id> --domain portal.acme.com

This returns two DNS records you need to configure:

CNAME  portal           → customer-portal.waymakerapp.com
TXT    _waymaker-verify.portal  → waymaker-verify=abc123-def456

2. Add DNS Records

Go to your DNS provider (Cloudflare, Route53, GoDaddy, Namecheap, etc.) and add both records:

CNAME Record

Type: CNAME
Name: portal (or your subdomain)
Value: <app-slug>.waymakerapp.com

TXT Record

Type: TXT
Name: _waymaker-verify.portal
Value: waymaker-verify=<token>

3. Verify DNS

After adding records, wait 1-5 minutes for propagation, then verify:

waymaker host domains verify <app-id>

The response tells you:

cname_ok: true/false — Whether the CNAME record was found
txt_ok: true/false — Whether the TXT verification record was found

If both are true, SSL is automatically provisioned.

4. Check Status

waymaker host domains status <app-id>

Domain status values:

Status	Meaning
`inactive`	No custom domain configured
`pending_dns`	Waiting for DNS records
`pending_ssl`	DNS verified, SSL being provisioned
`active`	Fully live with SSL
`error`	Something went wrong (check error message)

Removing a Custom Domain

waymaker host domains remove <app-id>

This:

Removes the SSL certificate
Cleans up DNS verification records
Reverts the app to its *.waymakerapp.com subdomain

Supported Domain Types

Subdomains — app.yourdomain.com, portal.yourdomain.com
Root domains — yourdomain.com (requires CNAME flattening at your DNS provider)
Deep subdomains — app.staging.yourdomain.com

DNS Propagation

DNS changes typically propagate within 1-5 minutes, but can take up to 48 hours in rare cases. If verification fails:

Double-check the record values match exactly
Wait 5-10 minutes and try again
Use dig or nslookup to verify records are visible:

dig CNAME portal.acme.com
dig TXT _waymaker-verify.portal.acme.com

Troubleshooting

"CNAME not found"

Ensure you're creating a CNAME record, not an A record
Check the subdomain matches exactly (no trailing dot in some providers)
If using Cloudflare as your DNS provider, set the proxy status to "DNS only" (grey cloud)

"TXT not found"

Some providers require the full domain in the Name field: _waymaker-verify.portal.acme.com
Others only need the subdomain portion: _waymaker-verify.portal
Check your provider's documentation

"SSL provisioning failed"

This is usually temporary. Wait 2-3 minutes and check status again
If it persists, try removing and re-setting up the domain

Custom Domains