Tutorials

Custom Domain for Your Changelog

Run your changelog on your own domain like changelog.yourapp.com. Step-by-step DNS setup, SSL, and branding benefits.

Why use a custom domain?

A custom domain like changelog.yourapp.com keeps your brand consistent and your SEO juice flowing to your own domain — not a third-party platform.

Setup in 4 steps

Step 1 — Choose your subdomain

Pick a subdomain that makes sense for your brand. Common choices: changelog.yourapp.com, updates.yourapp.com, or news.yourapp.com.

Step 2 — Add a CNAME record

In your DNS provider, add a CNAME record pointing to Deplyd:

Type:  CNAME
Name:  changelog
Value: deplyd.dev

Step 3 — Configure in Deplyd

Go to your project settings in the Deplyd dashboard and enter your custom domain. Click verify — Deplyd will check the DNS record.

Step 4 — Wait for SSL

Deplyd automatically provisions a free SSL certificate via Let's Encrypt. This usually takes a few minutes.

SSL and security

All custom domains get a free SSL certificate, automatically renewed. Your changelog is always served over HTTPS — no configuration needed.

Benefits

  • Brand consistency — Your changelog lives on your domain, matching your brand identity.
  • SEO value — All backlinks and page authority stay on your domain.
  • User trust — Users see your domain, not a third-party service.
  • Full control — You can change providers anytime — the URL stays yours.

FAQ

How long does DNS propagation take?

Usually under 5 minutes for CNAME records. In rare cases, it can take up to 48 hours depending on your DNS provider and TTL settings.

Can I use a subdomain of a subdomain?

Yes. Something like changelog.docs.yourapp.com works fine — as long as you can create the CNAME record.

Can I migrate from another changelog tool?

Yes. Just update the CNAME to point to deplyd.dev and configure the domain in your Deplyd dashboard. The transition is seamless.

Ship changelogs that get read

Try Deplyd free — 1.8KB widget, REST API, and email notifications included.

Start free now