What exactly is the Cloudflare Enterprise add-on?
A fully managed, per-domain integration that puts your website on Cloudflare's Enterprise network. Enterprise normally means a contract negotiated directly with Cloudflare at volume. xCloud already holds that contract, so you get global CDN acceleration, enterprise WAF and DDoS protection, edge caching, image optimization and real-time analytics for $5 a domain — with no negotiation, no minimum commitment and no Cloudflare account of your own.
Do I need my own Cloudflare account?
No. Cache rules, WAF toggles, purges, analytics and security events are all in your xCloud dashboard. Setup is smoothest if your domain already sits in a Cloudflare account that's connected to xCloud, because the configuration is then applied for you automatically — but that account is only ever used for your DNS records, not for the add-on itself.
How is $5 possible when Cloudflare Business is $250?
Because you're not buying a plan — you're joining one. xCloud holds an Enterprise contract with Cloudflare and the add-on attaches your domain to it as a custom hostname, so the cost is a share of a network already paid for rather than a new subscription. That is also why tiered caching and full-page edge caching are included here, when they're paid extras or hand-written rules on Cloudflare's own Pro and Business plans.
Is there a free trial?
Not at the moment. At $5 per domain with no contract you can enable it, run it on your own site and cancel whenever you want — but it starts billing straight away.
Is the add-on refundable?
No. Like every xCloud add-on, the Cloudflare Enterprise add-on is non-refundable once the subscription is activated. Add-on purchases are final, so check the domain, price and billing details before you subscribe. The full terms are in the xCloud Refund Policy.
Does the price per domain include subdomains?
One subscription covers the root domain and its www version. Other hostnames — shop.example.com, app.example.com, staging.example.com — are separate subscriptions at $5 per hostname per month, so you enable only the ones you need. Manage them together from the Addons page, and remove any single one without touching the rest.
Is bandwidth really unlimited?
Each domain subscription includes 100 GB of bandwidth per month, which covers the vast majority of WordPress sites — full-page edge caching means most requests are served from Cloudflare's edge without touching your server. Usage beyond 100 GB is billed at $0.02/GB, prorated, so a high-traffic site pays transparently for what it uses instead of hitting a hard cap or a forced upgrade. You can monitor your data transfer anytime in the Analytics tab of the addon.
Can I purge the cache from my WordPress dashboard?
You can purge per site from the xCloud dashboard today. A plugin to purge from wp-admin is planned as part of a central xCloud plugin — the purge capability is already built, it just needs wiring into WordPress.
How does rate limiting work, and can I change the threshold?
Rate limiting counts requests per IP in 60-second windows and applies a managed challenge above the threshold, which keeps bots, scrapers and brute-force traffic off your server. The default is 200 requests a minute and we're still tuning it across sites. It isn't a hard Cloudflare cap: if the default doesn't suit your site — a busy store, say — open a support ticket and we'll customise the threshold for your domain. Self-serve control is on the roadmap.
Is there still a 100-second timeout limit?
No. On Enterprise the timeout isn't fixed the way it is on the free plan. We currently run it at 200 seconds and can raise it further per use case — Cloudflare allows up to 6,000. If you have a legitimate long-running process hitting 524 errors, open a support ticket.
Does it work with WordPress and WooCommerce?
Yes, and the caching is aware of both. Full pages are cached at the edge, while edge page caching automatically bypasses logged-in sessions, wp-admin, wp-login, the REST API, WooCommerce and EDD carts, checkout, my-account, feeds and sitemaps — so shoppers never see someone else's basket. You can add your own bypass paths per site in the Cache Bypass Paths setting; anything under them is never cached at the edge and always loads fresh from your server. When you turn on Edge Page Caching, xCloud disables local page caching for that site so the two layers can't conflict.
Can I change the caching and security settings?
Yes. Early Hints, ScrapeShield, static caching, edge page caching, image optimization and the SSL cipher profile are all switchable, as are the WAF, rate limiting, browser integrity check, Under Attack Mode and AI crawler blocking. The defaults are already tuned; save after changing a toggle and xCloud persists it for the site.
What analytics do I get?
Request summary, cache performance and security events, over ranges from the last 30 minutes to the last 30 days, with your top pages, countries, devices and IPs — all in the xCloud dashboard rather than a separate Cloudflare console.
Will this affect my SEO?
It should help. Search engines weigh page speed and availability, and this improves both — pages come off the edge, and the WAF and DDoS mitigation keep the site reachable during attacks that would otherwise take your server, and the crawler, offline.