Custom domains

On this page

Run your public roadmap on your own domain. feedback.yourproduct.com looks better in tweets, ranks separately in search, and keeps the roadmap inside your brand surface area. Automatic TLS via Let's Encrypt. No web-server config to write. Custom domains are a Team-plan feature; Agency adds a custom domain per project.

Setup

  1. Go to Settings → Domains in your dashboard.
  2. Click Add domain and enter the subdomain you want to use (for example

feedback.yourproduct.com).

  1. Prove ownership: the dashboard shows a TXT record

(shippulse-verify=<token>) — add it at your DNS provider and click Verify. Propagation usually takes under a minute, up to a few minutes depending on your provider's TTL.

  1. Point the traffic: add a CNAME for your subdomain to
TYPE   NAME       VALUE
CNAME  feedback   shippulse-routing.shippulse.dev
  1. Once DNS propagates, the first request provisions a Let's Encrypt

certificate automatically (typically within ~30 seconds) and your roadmap is live on the custom domain. Certificates renew automatically.

The dashboard shows the exact records with your values at every step — copy from there, not from this page.

What gets served

Your custom domain serves the project's public roadmap surface: the roadmap at the domain root, with individual roadmap items deep-linkable (and indexable) under it. The marketing site, login, and dashboard stay on shippulse.dev — your custom domain is a clean read-only surface for visitors.

Removing a domain

Settings → Domains → Remove. Routing stops on our end immediately; delete the DNS records at your provider on your own schedule.

Troubleshooting

  • Verification fails — the TXT record is missing or still propagating.

Check the exact name/value pair shown in the dashboard (watch for trailing dots and provider-added quotes).

  • Verified but the domain shows "not configured" — the CNAME does not point

at shippulse-routing.shippulse.dev yet, or routing is not activated for this domain in the dashboard.

  • Cert never issues — your DNS provider may have CAA records that block

Let's Encrypt. Allow letsencrypt.org.

Next