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.

  • 100,000+PBN sites hosted across every niche
  • 99.99%Uptime assurance
  • 8CDN providers supported behind one driver

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.

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.

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 a CDN by default, or your own, 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.

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.

Pool your accounts, spread your footprint

Start a card-free 7-day trial with a 30-day money-back guarantee, free migrations and no vendor lock-in.

Start free