Bring your own accounts
Connect your existing Cloudflare and CDN accounts. Credentials are stored in Vault, so keys stay secret and never appear in code or logs.
Footprint-Free feature
CDN account pool
Pool your own Cloudflare and CDN accounts alongside ours, choose which account each site deploys to, let footprint-aware balancing spread sites evenly, and purge cache across every account from one control.
- 600,000+PBN sites hosted worldwide
- 99.99%Uptime assurance
- 8CDN providers supported behind one driver
- Yours + oursaccounts in one pool, balanced together
- 106WordPress footprints managed automatically
- One clickpurge across every account at once
- $0extra for using your own accounts
One pool, your accounts and ours
Add your own Cloudflare or CDN accounts, use the accounts we provide, or mix both. Every account sits in one pool you control, with keys held in Vault and never exposed.
Use our accounts too
Draw on the accounts Zinn Digital® provides alongside yours. There is no lock-in either way, so you can lean on ours, yours, or both.
Per-site account selection
Choose exactly which account each site deploys to. Every CDN account tracks its live site count, so you always see where sites sit.
Eight providers, one driver
The CDN driver speaks to eight providers behind a single interface, handling cache purge, HTTPS, certificates and DNS record sync uniformly.
Footprint-aware balancing
For Footprint-Free hosting, spreading sites thin across many accounts is the moat. The pool does the maths for you.
With many accounts in the pool, balancing rotates and spreads a user's sites across them to minimise footprint, so no single account carries a tell-tale cluster of related sites.
Balance is recomputed from live account state at deploy time, and deleted sites are counted, so the spread stays even rather than drifting as sites come and go. For mainstream hosting the same pool serves whichever CDN tier you switch on for a site, or your own account, with no rotation needed.
Global cross-account cache purge
- Purge cache across every account in the pool from a single control in the panel, no account-by-account clicking.
- The same purge control coordinates with the server-side cache layer, so CDN and origin caches clear together.
- Purge hooks fire back to the panel on content change, keeping cached pages fresh as sites are edited.
- Free migrations bring existing sites and their accounts into the pool without downtime.
Why a pool rather than one account
A CDN account is a fingerprint. Put a hundred sites behind one account and you have told anyone who looks that those hundred sites are run by one person — the nameservers match, the certificate issuance matches, the response headers match, and none of that is visible to you until somebody else notices it.
Pooling is the answer, and it only works if the pool is big enough and varied enough. That is why your own accounts are welcome in it and why there is no charge for bringing them: a pool made only of our accounts is a smaller, more uniform pool, which is worse for you and worse for everybody else in it.
The balancing is not a setting you tune. The platform places each site to spread the signals that actually correlate — account, nameserver pair, certificate authority and issuance timing — and rotates when a pattern starts to form.
No lock-in
Bring your own accounts, keep your own keys
Your Cloudflare account stays yours. You add it, we place sites in it, and you can take it back at any time — the sites move rather than break, because the platform holds the zone configuration and can rebuild it anywhere.
That is the same principle as everything else here: no external dependency we cannot swap, and none you cannot take with you.
- Your accounts and ours, balanced as one pool
- No charge for bringing your own
- Take an account back and the sites move, not break
FAQ
Can I use my own Cloudflare accounts?
Yes. Connect any number of your own Cloudflare or CDN accounts, use the accounts we provide, or run both together in one pool. Credentials are held in Vault and never exposed in code or logs.
How does footprint-aware balancing work?
With several accounts in the pool, sites are rotated and spread across them to minimise footprint. The balance is recomputed from live account state at deploy time, counting deleted sites, so the spread stays even instead of drifting over time.
Can I choose which account a specific site uses?
Yes. Per-site account selection lets you pick exactly which account each site deploys to, and every account shows its live site count so you can see the distribution at a glance.
How does cache purging work across many accounts?
A single control in the panel purges cache across every account in the pool at once. It coordinates with the server-side cache layer as well, so CDN and origin caches clear together rather than separately.
Is there any vendor lock-in?
No. The pool works with your accounts and ours behind a swappable driver covering eight providers, and free migrations move sites in. You can leave with your own accounts intact whenever you choose.
Related
Pool your accounts, spread your footprint
Start a card-free 14-day trial with a 30-day money-back guarantee, free migrations and no vendor lock-in.
Start free