The request:
Allow the Cloudflare Enterprise add-on to onboard a wildcard *.mydomain.com as a single custom hostname — so every existing and future subdomain of a customer's domain is served through the Enterprise edge automatically, without adding hostnames one by one.

The use case (growing fast in SEO publishing):
Many high-traffic content and software-download sites use a "keyword-first subdomain" architecture, where every article lives on its own subdomain (e.g. program-name.mysite.com). Sites like this create hundreds of new subdomains per month, automatically on publish. Individual hostname onboarding makes the Enterprise add-on unusable for this entire category of sites — there is no fixed list of subdomains to add.

Why it's technically feasible:
Cloudflare for SaaS already supports wildcard custom hostnames on Cloudflare Enterprise plans (the tier the Cloudways add-on is built on). This is an existing upstream capability — the request is to expose it in the Cloudways integration, even as an opt-in per application.

Business impact for Cloudways:
I run exactly this architecture. I wanted to pay for the Enterprise add-on, but after your support team confirmed wildcard onboarding isn't possible (ticket, Aug 2026), I migrated my DNS to a standard Cloudflare account where proxied wildcard records work on the free plan. Every publisher with a subdomain-per-page architecture will make the same choice — this limitation actively pushes revenue away from the add-on. Wildcard support would make the add-on the obvious choice instead.

Acceptance criteria:
- Add *.domain.com in Domain Management → Enterprise edge serves any subdomain with valid SSL, no per-hostname steps
- New subdomains work instantly when DNS resolves (no provisioning step per publish)