Enterprise
Custom domains
Serve your workspace from a domain you own. You keep the domain at your registrar; two DNS records point it at FeatureParity, and your apps appear at yourdomain/<app>.
Pick a hostname#
We recommend a subdomain of your company domain, like tools.yourcompany.com. It needs one CNAME record and leaves your main website alone. A dedicated domain works too, like www.mycompanytools.com or the bare mycompanytools.com.
A workspace can have up to 3 domains; all of them serve the same apps. Wildcards aren't supported.
Add it to your workspace#
In the workspace console, open Domains, enter the hostname, and click Add domain. You can paste a full URL; we keep only the hostname. The console then shows the exact records for your domain.
Add the DNS records#
At your DNS provider (often your registrar, or Cloudflare, Route 53, Google Cloud DNS, and so on), add:
| Type | Name / host | Value | Purpose |
|---|---|---|---|
| TXT | _featureparity.tools.yourcompany.com | featureparity-verify=<your token> | Proves you control the domain |
| CNAME | tools.yourcompany.com | cname.vercel-dns.com | Routes a subdomain to your workspace |
| A | mycompanytools.com | 76.76.21.21 | Routes a bare domain instead (no CNAME) |
Use the CNAME for a subdomain (including www) or the A record for a bare domain, not both. Copy your token from the console.
The host field
Most providers want only the part before your domain in the host or name field. For _featureparity.tools.yourcompany.com you'd enter _featureparity.tools; for tools.yourcompany.com, enter tools; for a bare domain, enter @. If you're not sure, check that the full name your provider shows matches the table.
Provider notes
- Cloudflare: set the CNAME's proxy status to DNS only (gray cloud). With the orange-cloud proxy on, certificates can't be issued and requests may loop.
- Squarespace, GoDaddy, Namecheap: use the short host form (
tools,_featureparity.tools). Some won't take a CNAME on@; use the A record there. - Route 53, Google Cloud DNS: they take full names. TXT values may need quotes; that's fine.
- CAA records: if your domain has any, add one allowing
letsencrypt.org, or HTTPS can't be issued.
Verify#
Back on the Domains tab, click Verify. We look up the TXT record; once it matches, the domain is yours in FeatureParity and we route it to your workspace and request an HTTPS certificate. New records usually show up within minutes, but some providers take up to a few hours. Click Verify again any time; it's safe to repeat.
After verifying, the domain card shows one of:
- Routing and HTTPS are set up. Visit the domain. You're done.
- DNS doesn't point to us yet. The CNAME or A record is missing, wrong, or still propagating.
- One more TXT record is needed. The domain is also registered with our hosting provider (Vercel) under another account, usually an old project of yours. Add the extra record the card shows, then click Re-check.
Nothing is public until the plan starts
A verified domain serves your apps only while the workspace's plan is in its trial or active. Otherwise it shows a paused page to signed-in members and the sign-in page to everyone else. See Plan and billing.
One domain, one workspace#
Any workspace can add a domain, but only the first to verify it gets it, and only someone who can publish its TXT record can verify it. If another workspace already verified your domain, contact us.
Removing a domain#
Click Remove on the domain card. It stops serving immediately and is released for reuse. Delete the DNS records at your provider afterwards. Your apps keep working on your other domains and in the console.
Troubleshooting#
| Symptom | Likely cause |
|---|---|
| “We couldn't find the TXT record yet” | The record isn't published or hasn't propagated. Check the name (host field form) and that the value has no extra spaces. |
| The domain shows a 404 page | It isn't verified yet, or it was removed. Domains serve nothing until verified. |
| Certificate or “not secure” warning | The CNAME/A record isn't live yet, a Cloudflare proxy is on, or a CAA record blocks Let's Encrypt. |
| Too many redirects | A proxy in front of the domain (often Cloudflare) is rewriting HTTPS. Switch it to DNS only. |
| Someone can't sign in | Their email isn't a member. See Members and sign-in. |
To check records yourself: dig TXT _featureparity.tools.yourcompany.com and dig CNAME tools.yourcompany.com.