# WHMCS CDN Integration

> Sell Cloudflare, Bunny.net or KeyCDN as a WHMCS product, with zones created on order and removed on termination.

CDN reselling in WHMCS: provisioning module for Cloudflare, Bunny.net or KeyCDN, client-area cache and DNS controls, suspension rules and optional usage billing.

- **Price:** Starting at $149
- **Billing:** One-time, fixed scope
- **Category:** Modules & integrations
- **Quote turnaround:** Fixed-price quote within 24 hours
- **Start a project:** https://whmcspilot.com/start-project
- **Details:** https://whmcspilot.com/services/whmcs-cdn-integration
- **Last updated:** 2026-11-05

## Overview

WHMCS has no built-in CDN product, so offering Cloudflare, Bunny.net (BunnyCDN) or KeyCDN to your customers needs a provisioning module that creates the zone when an order activates and removes it when the service ends. We set that up for web hosts and agencies who want CDN on their price list, starting at $149. This page is about CDN sold to customers. If the goal is a faster WHMCS client area for your own visitors, [WHMCS speed optimization](/services/whmcs-speed-optimization) covers that.

## Provider options

ProviderHow customers connect a siteWhat the WHMCS module handlesCloudflarePoint the domain's nameservers to Cloudflare. CNAME (partial) setup is limited to Cloudflare Business and Enterprise plans.Zone creation by API token, DNS records, cache purge, SSL mode, plan changesBunny.netAdd a CNAME from their hostname to the pull zonePull zone with origin URL, custom hostname with a free certificate, purge, deletion on terminationKeyCDNAdd a CNAME to the zone, set up as a zone aliasPull zone, alias, purge, deletion on termination

For Cloudflare we normally use our [WHMCS Cloudflare Integration Module](/modules/whmcs-cloudflare), which provisions zones on order and gives customers DNS record editing (A, AAAA, CNAME, MX, TXT, SRV, CAA), cache purge by URL, tag or full zone, page rules, Flexible, Full or Strict SSL modes and, on Pro and Business zones, WAF rules. Upgrading a zone's Cloudflare plan raises a WHMCS invoice. If you only want to offer DNS hosting without the CDN features, the lighter [DNS Management (Cloudflare) module](/modules/dns-management-cloudflare) is enough.

Bunny.net and KeyCDN have well-documented APIs but no module shipped with WHMCS. Where a maintained third-party module fits your version, we install and test it. Where none does, we write a small provisioning module against the provider's API, quoted separately under [module development](/services/whmcs-module-development).

## The lifecycle we wire up

1. **Create.** The order activates, the module creates the zone or pull zone with the customer's origin, and the welcome email lists the CNAME or nameservers they need to set.
2. **Manage.** The client area service page shows zone status and offers cache purge, plus DNS editing for Cloudflare. Admins get the same actions as module buttons on the service.
3. **Suspend and unsuspend.** We agree the behavior per provider, for example pausing the zone or disabling it where the API allows, so an overdue invoice does not leave free CDN running.
4. **Change package.** Moving between your plans changes the zone settings or Cloudflare plan and bills the difference.
5. **Terminate.** The zone or pull zone is deleted at the provider, so you stop paying for traffic on a cancelled service.

## Selling by traffic

Bunny.net and KeyCDN charge you per GB delivered, so flat-rate plans need a sensible cap. When the provider's API returns traffic per zone, the module can report it to WHMCS, and the product's overage settings bill usage above the included allowance. We decide with you whether to sell fixed bundles, metered plans or both, and set product names that make the limits obvious.

## If your own WHMCS sits behind Cloudflare

Proxying the WHMCS site through Cloudflare is common, and it has one known side effect: unless Cloudflare's addresses are in the Trusted Proxies list on the Security tab at Configuration &gt; System Settings &gt; General Settings, staff and customers get logged out early and WHMCS logs the wrong client IPs. System Health flags it with a Cloudflare Proxy Check warning. We fix that while we are in the install.

## What to have ready

- An account with the CDN provider and an API token or key with zone permissions
- A WHMCS admin account; 8.13 and 9.x both work, on PHP 8.1+ and PHP 8.2+ respectively
- The plans you want to sell, with prices and any traffic allowance
- A test domain or site we can put through the full order and termination cycle

## Handover

CDN products in your catalog, a tested order that created a working zone, a tested cancellation that removed it, welcome email text with the customer's DNS steps, and a short admin note covering suspension rules and usage billing.

## Prices by scope

ScopePriceCloudflare through our module, or Bunny.net or KeyCDN through an existing module: products, lifecycle test, welcome emailFrom $149Usage reporting and overage billingFixed quoteCustom provisioning module for a provider without oneFixed quote after reviewing the API

## Not part of this job

Provider fees and Cloudflare plan charges, module license fees, tuning your customers' origin servers or WordPress caching plugins, and DDoS incident response. To discuss a provider not listed here, start at [the project form](/start-project).

## What's included

- CDN products for Cloudflare, Bunny.net or KeyCDN added to your WHMCS catalog
- Zone or pull zone created automatically when the order activates
- Welcome email with the nameserver or CNAME steps for each provider
- Client area cache purge, plus DNS record editing for Cloudflare zones
- Admin module buttons for purge and status checks
- Suspend, unsuspend, package change and terminate behavior agreed and tested
- Zone deleted at the provider on termination
- Optional usage reporting with overage billing for metered plans
- Trusted Proxies fixed if your own WHMCS runs behind Cloudflare
- Full order-to-cancellation test on a real domain

## Business outcomes

- CDN becomes a recurring product instead of a manual favor for customers
- Cancelled services stop costing you provider traffic fees
- Unpaid invoices suspend CDN the same way they suspend hosting
- Customers purge cache and edit DNS without opening a ticket
- Traffic-based plans are billed from real usage instead of guesses

## Frequently asked questions

### Does WHMCS include a CDN module?

No. WHMCS ships no CDN provisioning module, so Cloudflare, Bunny.net or KeyCDN needs a third-party or custom module. For Cloudflare we normally use our own WHMCS Cloudflare Integration Module.

### Do customers have to change their nameservers?

For Cloudflare, usually yes, because CNAME setup is limited to Business and Enterprise plans. Bunny.net and KeyCDN only need a CNAME record, so nameservers stay where they are.

### What happens to the zone when a customer stops paying?

The service suspends with the rest of their account, and the zone is paused or disabled according to the rule we agree for that provider. On termination the zone is deleted at the provider.

### Can I bill CDN by bandwidth?

Yes, when the provider's API reports traffic per zone. The module sends usage to WHMCS and the product's overage settings invoice anything above the allowance, quoted as an add-on.

### Is this the same as making my WHMCS faster?

No. This service sells CDN to your customers. Front-end and page load work on your own WHMCS is a separate speed optimization service.

### What does CDN setup cost?

From $149 for the setup with an existing module. Module licenses and provider fees are separate, and a custom module is quoted after we review the provider's API.
