Configure a Custom Domain in Canny
Add the hostname in Canny custom-domain settings, then point that subdomain’s CNAME to cname.canny.io. Canny provisions HTTPS automatically.
Before you start: Have a paid Canny plan, Owner permissions for domain settings and access to your DNS provider. Choose an unused subdomain rather than moving an existing app hostname.
Worked example: Use feedback.example.com for the feedback site while www.example.com continues serving the marketing site. Keep a record of the previous DNS state before making the scoped change.
Step-by-step guide
Choose the exact hostname
Confirm feedback.example.com is available and that changing it will not interrupt another service. Use a subdomain suitable for a CNAME.
Register it in Canny
Open Canny’s custom-domain settings and add the chosen hostname before testing traffic against it.
Set the DNS record
Create a CNAME for feedback pointing to cname.canny.io. If using Cloudflare, disable proxying for this record as the Canny guide specifies.
Verify DNS and HTTPS
After DNS resolves, open the HTTPS address. Canny requests a certificate on the first request, so initial provisioning may take a short interval.
Check the complete user path
Open a post, sign in and return to the feedback site. Update navigation links only after the custom-domain flow works.
Common mistakes
Pointing at the wrong target
Use the documented cname.canny.io target, not a guessed workspace IP or a copied marketing-site address.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.