One click clears the whole cache
You published a change and the old one still shows: purge the zone and the new content reaches every edge node.
The CDN lives in the same panel as your site and inside the same plan: it provisions itself, it's encrypted from second one and it purges in one click when you publish something new.
It isn't another product to buy: you switch it on from the site's CDN tab and the zone is serving within seconds.
The configuration we provision your CDN with, identical on every plan and with nothing for you to decide.
The panel tells you whether the zone is serving, how much work it's taking off your server and where you stand on your plan.
You published a change and the old one still shows: purge the zone and the new content reaches every edge node.
Every zone serves WebP and AVIF to browsers that accept them, so your images weigh less without you editing a single one.
It's on from the moment the zone is created: everything the CDN serves is encrypted, with nothing for you to remember.
POST requests are blocked at the nodes: the CDN delivers your content and never becomes a vector for abuse.
If your site's domain doesn't resolve yet, we stop the creation and tell you what's missing in DNS before going on.
If your organization runs out of allowance the CDN pauses; upgrade the plan and it reactivates on its own, no ticket needed.
Any member can clear the cache and read the stats; creating and deleting zones stays reserved for administrators.
No tickets, no advanced settings: the panel talks to the network and hands you the zone ready.
It's inside the hosting site panel you already use. Nothing separate to buy and no other account to create.
Before creating anything we verify over DNS that your site's domain resolves. If it isn't ready yet, we tell you.
It's created with its regions, forced HTTPS, WebP and AVIF, POST blocked and its traffic ceiling, with nothing for you to pick.
One click clears the cache on every node. On Pro and Business, purging the site cache also clears the CDN's.
The CDN is part of the plan, not a separate bill. Between plans the zones and included traffic change, not the features.
| Feature | Starter | Pro | Business |
|---|---|---|---|
| Capacity | |||
| CDN zones | 1 | 3 | 10 |
| Traffic included per monthPer organization, across all your zones | 50 GB | 200 GB | 1.000 GB |
| Technical ceiling per zoneSafety net against a spike or an external hotlink | 75 GB | 300 GB | 1.500 GB |
| Charges for excess trafficAt the cap the zone pauses; there's no extra invoice | — | — | — |
| Delivery | |||
| Edge regions | NA · EU · SA | NA · EU · SA | NA · EU · SA |
| Full purge in one click | ✓ | ✓ | ✓ |
| Purge chained with the site cacheRequires site acceleration, included from Pro | — | ✓ | ✓ |
| Automatic WebP and AVIF | ✓ | ✓ | ✓ |
| Forced HTTPS | ✓ | ✓ | ✓ |
| POST request blocking | ✓ | ✓ | ✓ |
| Control and usage | |||
| Today's requests and cache hits | ✓ | ✓ | ✓ |
| Zones used against the plan | ✓ | ✓ | ✓ |
| Email alerts before the limit | ✓ | ✓ | ✓ |
| Automatic reactivation on upgrade | ✓ | ✓ | ✓ |
| CDN in the usage summary | ✓ | ✓ | ✓ |
| Team and access | |||
| Create and delete zones | Admin | Admin | Admin |
| Purge cache and read stats | Todo el equipo | Todo el equipo | Todo el equipo |
| Per-organization isolation | ✓ | ✓ | ✓ |
| Separate cost for the CDNIt's inside your plan, never billed separately | — | — | — |
The CDN requires an active or trialing plan and today it's switched on from each hosting site's panel. We're still completing the module: connecting your own CDN domain and seeing the traffic history are on the way, right below.
The module works and we keep completing it. Here's what comes next, with its real horizon.
Every service talks to the others and lives in the same plan.
Pluxion's five core services, today paid separately — in a single plan.
7-day trial · No charge today · Free migration