State of M&A Data Rooms — Q1 2026 Read the report →
Peony LogoPeony

Custom Domains (Business Tier)

Serve Peony data rooms from your own subdomain (files.yourcompany.com). DNS setup, common mistakes, SSL provisioning, and troubleshooting.

Last updated April 10, 2026

Serve Peony data rooms from your own subdomain — files.yourcompany.com or docs.yourcompany.com — instead of yourname.peony.ink. Counterparties see your domain, your logo, and your colors, with no Peony branding in the URL.

Available on the Business tier ($40/admin/month).

What It Does

  • Replaces yourname.peony.ink with your own subdomain (e.g. files.yourcompany.com, deals.yourcompany.com).
  • Gives you a branded URL for investor or client delivery. files.acme.com/series-a lands differently than acme-inc.peony.ink/series-a.
  • Lets you present Peony as an internal system — useful for M&A sell-side, client proposals, and any situation where the counterparty shouldn't need to know the vendor behind the scenes.

DNS Setup

  1. Enter your desired subdomain in Peony settings. Workspace settings → Branding → Custom Domain. Type the subdomain (e.g. files.yourcompany.com).

  2. Peony shows you a CNAME record to add at your DNS provider. Name is your subdomain, value is a Peony target hostname. Use the copy-to-clipboard button.

  3. Add the CNAME at your DNS provider (Cloudflare, Route 53, Namecheap, GoDaddy, etc.).

  4. Wait for DNS propagation. Usually 5 minutes to 1 hour. Edge cases with long TTLs can take up to 48 hours.

  5. Return to Peony and click Verify. Peony checks the CNAME and provisions an SSL cert in the background.

After verification, your data rooms serve from your custom domain automatically. Existing share links keep working on both the old *.peony.ink URL and the new custom domain.

Common DNS Mistakes

  • Mistyping the CNAME value. Always use the copy-to-clipboard button. A dropped character breaks verification silently.
  • Pointing an A record instead of a CNAME. Peony requires a CNAME. Underlying IPs change.
  • Leaving a conflicting record. If something already exists at files.yourcompany.com, remove it before adding the new CNAME.
  • Using an apex domain. Subdomains only. files.yourcompany.com, not the bare yourcompany.com.
  • Browser cache after propagation. Hard-refresh (Cmd-Shift-R) or test in incognito.

SSL and HTTPS

Peony auto-provisions an SSL certificate via Let's Encrypt as soon as DNS verification succeeds. No manual cert generation, upload, or renewal.

If SSL fails, the root cause is almost always DNS. Let's Encrypt needs a working DNS lookup first — re-verify the CNAME, wait a few minutes, and try again.

Renewal is automatic.

Troubleshooting

  • CNAME not verifying. Check with dig CNAME files.yourcompany.com or nslookup. The output should show the Peony target hostname. If not, the record is mistyped, not propagated, or pointed wrong.
  • Worked yesterday, now showing an error. Some DNS providers drop CNAMEs they think are unused. Re-add the record.
  • SSL warning in the browser. Usually the first 5-10 minutes after verification while the cert provisions. Wait and hard-refresh. Past 15 minutes, re-verify DNS and contact support.