A free global CDN tier, included with your hosting — not sold back to you

The free tier costs nothing extra — there is no per-gigabyte charge and no separate account to open. It is an entitlement your plan either includes or does not, so your plan's own page is the answer for your plan: most of our hosting plans carry it, and a few do not. On the whole Footprint-Free (PBN) line the question does not arise, because the CDN is native to the product and always on. Where a plan does not include the free tier you can still add the Premium CDN for that site, connect a CDN account you already pay for, or point the domain at an edge you run yourself.

More cache capacity, and a choice of network. The Premium tier is a monthly per-site add-on; above it sits a metered tier served from Amazon CloudFront and charged per gigabyte against prepaid credit, which people buy for the distinct network rather than for raw speed. Alongside those are four monthly traffic plans with a fixed included allowance — 500 GB, 900 GB, 1.7 TB and 2.9 TB. You pick per site, from that site's CDN tab, and the current price of each is shown there.

Yes. Connect a Cloudflare, Bunny CDN, CDN77, KeyCDN, Fastly, Gcore, Amazon CloudFront or Akamai account under Connections and we drive it for you — the token is validated against the provider's own API before it is stored, and it is kept in Vault, and the account then appears as a destination any of your sites can be moved onto. For any other CDN, passthrough points your domain at the edge hostname you give us, so a network we have never integrated still works.

The tier is ours to set and the account is never disclosed — that is the product, not a limitation. Sites are spread across a pool of accounts so no two of your domains can be tied to each other through the edge they share, and origin IPs stay behind it. What you do choose is the network itself: picking the CDN for a site is yours on every line, Footprint-Free included. What you cannot see is which of our accounts inside that network the site landed on, because that is the fact the whole line exists to hide.

No. Purge is a button on the site's CDN tab for every tier and every account we drive. On WordPress, the Zinn® Cache plugin also purges the server's page cache by itself whenever content changes — a post edit clears that post and the listings it appears on, a comment clears its parent, a theme switch or a site-wide option clears everything. Under passthrough we hold no credential, so purging and certificates stay in your own provider's panel.

On the Footprint-Free line, yes — the CDN is part of provisioning and the site arrives behind it. On every other line a new site starts with the CDN off and nothing at your edge changes until you choose a tier. That is deliberate: turning a CDN on in front of a site somebody is mid-migration with is not a favour, and a cache you did not ask for is the hardest kind to debug.

Because it costs more to serve. A traffic plan's allowance is denominated in base-region-equivalent gigabytes: a gigabyte served in Europe or North America spends one, Asia and Oceania spend three, South America four and a half, and the Middle East and Africa six. The weighting is shown on the site's CDN tab beside the plans, so you can see what your own audience actually costs rather than discovering it on a bill.

We build the new zone first, point your domain at it, and only remove the old one once the change is live. Nothing is torn down on the strength of a request having been accepted. You can move between our network, one of your own connected accounts and an edge you run yourself, in any direction, from the same card.

Cache level — cache static files only, ignore query strings, or cache each query string separately. Page rules and firewall rules. Which address visitors are served on, apex or www, with the other permanently redirecting to it so search engines index one address instead of splitting between two. Always-use-HTTPS, and the certificate that covers both names. Plus a purge button, live edge traffic, and a spend budget for the metered tier.

Not necessarily. Some networks answer DNS and serve the CDN from the same zone, so one account can do both and we will offer that when it applies. Others need a DNS provider alongside them. A pairing we cannot provision is refused at the moment you choose it, with a message naming which of the two to change — we would rather say no than hand you a site that never resolves. You can also leave DNS exactly where it is and point a single record at the edge.

Nothing extra for the CDN itself — it is your account and your provider bills you directly. We hold the credential, build and manage the zone, purge it, set TLS and report its state alongside every other site you run with us. The difference between that and passthrough is whether we hold a credential at all: under passthrough we only point DNS, so we cannot purge your cache or manage your certificate.

Yes, while it is on: visitors resolve the edge, not the machine. On the Footprint-Free line that is enforced rather than incidental — origin records can never be changed to expose the server, because a single leaked origin IP would tie every site behind it together.