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

Enter your desired subdomain in Peony settings. Workspace settings → Branding → Custom Domain. Type the subdomain (e.g. files.yourcompany.com).
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.
Add the CNAME at your DNS provider (Cloudflare, Route 53, Namecheap, GoDaddy, etc.).
Wait for DNS propagation. Usually 5 minutes to 1 hour. Edge cases with long TTLs can take up to 48 hours.
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.

Provider-Specific Notes

A few DNS hosts have quirks that trip up the setup. The fixes below are what we walk customers through most often in support.

Cloudflare

Disable the proxy on the CNAME. The Cloudflare cloud icon next to your record must be gray (DNS only), not orange. Cloudflare's proxy intercepts the request before it reaches Peony and breaks the SSL handshake, so verification fails even with a perfect CNAME value.
After adding the CNAME, click the orange cloud icon to toggle it gray, save, then click Verify in Peony.
Cloudflare's DNS dashboard shows your full DNS table; the only record that needs to change is the new CNAME. Leave existing MX, TXT, and other records alone.

Vercel

Vercel-managed domains require two records: the CNAME Peony shows you, plus a TXT verification record. Add both before clicking Verify.
A common error message is DEPLOYMENT_NOT_FOUND after the CNAME resolves. That means the CNAME is correct but the TXT verification is missing or hasn't propagated. Re-check the TXT record at your DNS provider, then re-verify in Peony's Domain Settings.
Vercel's own dashboard sometimes auto-suggests an A record for apex domains — ignore it. Peony only supports CNAMEs on subdomains.

GoDaddy / Namecheap / Route 53

Use a CNAME on a subdomain (files.yourcompany.com) — never on the apex (yourcompany.com). Most apex CNAMEs are silently rewritten to ALIAS or A records, which Peony's verifier can't follow.
Leave the TTL on default (usually Auto or 1 hour). Lowering the TTL doesn't speed up the first verification — it only makes future changes propagate faster.
If the provider has a "DNS validation" or "redirect" feature, leave it off. Peony handles SSL via Let's Encrypt directly once it can resolve the CNAME.

Still stuck?

Run dig CNAME files.yourcompany.com (or use dnschecker.org). The output should show Peony's target hostname. If it returns nothing or shows your old record, the change hasn't propagated yet — wait 5–60 minutes (occasionally up to 48 for legacy TTLs).
Most DNS issues resolve within an hour. If it's been longer than that with the right CNAME in place, email deqian@peony.ink with your domain and the screenshot of your DNS panel — we'll trace it from our side.

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.

Custom Branding — logos, colors, cover images
Plans and Pricing — Business tier required