Eight providers
Cloudflare, Bunny CDN, CDN77, KeyCDN, Fastly, Gcore, Amazon CloudFront and Akamai, each on your own account.
Your own CDN
Put your sites on your own CDN
Already pay for a CDN? Connect your own Cloudflare, Bunny CDN, CDN77, KeyCDN, Fastly, Gcore, Amazon CloudFront or Akamai account, and a site's CDN tab can move the site onto it, purge its cache and change its settings. We test the key's permissions before we save it.
What it is
A connection to the CDN account you already hold. You create a key with your provider, paste it into Integrations, and we check exactly what it is allowed to do before anything is saved.
Once connected, the account is available on a site's CDN tab: move the site onto your CDN, purge its cache and change its settings from the dashboard. The CDN contract and bill stay with your provider.
What you get
Eight providers, one set of controls.
Permissions tested first
Before saving, we check what the key can do: read zones, read a zone's detail, purge the cache, change zone settings and manage geo rules. You see each result, so a missing permission is caught when you connect, not in the middle of a change.
Move a site onto your CDN
A site's CDN tab can put the site behind the account you connected.
Purge from the dashboard
Clear a site's cache on your CDN without opening your provider's control panel.
Change CDN settings
Adjust a site's CDN settings from the same tab.
Kept encrypted, deleted on disconnect
A key that passes is stored encrypted in our secrets vault, and disconnecting deletes it.
Step-by-step guides
Each guide shows where to create the key on the provider's side, what it needs, and how to connect it in the dashboard.
Bring your own accounts: the overview
Read the guide →Cloudflare
Read the guide →Bunny CDN
Read the guide →CDN77
Read the guide →KeyCDN
Read the guide →Fastly
Read the guide →Gcore
Read the guide →Amazon CloudFront
Read the guide →Akamai
Read the guide →How it works
Connect once, then use it site by site.
Create a key with your provider
Create an API key or token in your CDN account. Each provider's guide lists the permissions it needs.
Connect it in Integrations
Paste it in. We test its permissions and show you what passed before saving it.
Use it on a site
Open a site's CDN tab to move the site onto your CDN, purge its cache or change its settings.
Pricing
Using your own CDN account is not an add-on.
We charge nothing for the connection. Your CDN provider bills you directly, on your own account, for the traffic it serves. Your Zinn Digital® hosting plan is billed as normal.
Bandwidth, request and feature prices are your provider's, on your account. We never add to them.
Why it is built this way
Many teams already have a CDN contract, negotiated rates or settings they trust. Asking them to give that up to host with us would be the wrong trade, so the dashboard drives the account they already have.
Testing permissions before saving is the difference between a connection that works and one that fails the first time you purge in a hurry. A key that cannot do the job is refused while you still have your provider's page open.
Questions people ask before they buy
Which CDNs can I connect?
Cloudflare, Bunny CDN, CDN77, KeyCDN, Fastly, Gcore, Amazon CloudFront and Akamai, each on your own account.
What permissions does my key need?
Enough to read zones and a zone's detail, purge the cache, change zone settings and manage geo rules. We test each of these before saving and show you the result, so you know what the key can and cannot do.
Who pays for the CDN traffic?
Your CDN provider bills you directly, on your own account. We charge nothing for the connection, and your hosting plan is billed as normal.
How is my key stored?
Only after it passes the permission test, and then encrypted in our secrets vault. Disconnecting deletes it.
What happens if I disconnect?
The stored key is deleted, so we can no longer purge or change settings on that account. Your CDN account, and everything configured in it, stays with your provider.
Help with this
Step-by-step guides from our knowledge base, written for exactly this.
Deploy a site to your own CDN account
Connect your own Cloudflare account, put a site on it, and move a site between accounts without taking it down.
Read the guide →Giving clients their own CDN and DNS
Pools, bring-your-own accounts, and why footprint separation needs more than one account.
Read the guide →Putting a site behind a CDN
Whether you need to do anything at all depends on which product your site is on — on one of them the CDN is already there.
Read the guide →Connect your CDN account
Create an account, open Integrations and paste in a key from your CDN provider. You will see its permissions tested before it is saved.
Get started