Multi-CDN aggregated edge
Use Cloudflare, CloudFront, EdgeOne, ESA and other CDNs as site supplies scheduled with your own nodes: config sync, schedule-only, one-click import.
What it solves
With only your own nodes, a full uplink or a data-centre outage takes your sites down with it; using several cloud CDNs means configuring each one in its own console. Aggregated edge turns a cloud CDN into one more supply for a site, scheduled together with your own and subscribed nodes: change a site once in the control plane and it syncs to every vendor, and traffic moves away from whichever vendor is unhealthy.
The accounts are yours: you bind your own vendor account (Cloudflare's free plan is enough), the credentials are encrypted in your own control plane and never pass through the market or the licence server, and the vendor bills you directly. The platform offers no shared accounts.
| Vendor | Config sync | Schedule-only | One-click import |
|---|---|---|---|
| Cloudflare | Yes | Yes | Yes |
| AWS CloudFront | Yes | Yes | Yes |
| Tencent Cloud EdgeOne | Yes | Yes | Yes |
| Alibaba Cloud ESA | Yes | Yes | Yes |
| Other vendors (Fastly, Akamai, your own edge…) | No | Yes | No |
- Config sync: the control plane creates the domain, origin, certificate and cache rules in your vendor account, keeps them in sync when you change the site, and detects drift made on the vendor side.
- Schedule-only: you set up the domain in the vendor console and enter the vendor's CNAME in the control plane. It never touches the vendor's configuration and needs no credentials; it only probes and switches DNS.
- One-click import: reads the configuration of a site that already exists at the vendor and maps it into a site view without changing anything; settings that do not map are listed one by one. Imported sites do not join cross-CDN scheduling until you run the migration wizard and confirm the DNS change.
Turning it on
Aggregated edge is an official, free module of the commercial edition, included in the default licence of a new commercial control plane. The community edition does not include it.
- An administrator opens Aggregated edge → Accounts, picks the vendor, creates an API token or key scoped to the target site in the vendor console as the page describes, and clicks Bind and verify. If verification fails, add the missing permissions and verify again.
- Under Third-party CDN access, open an access point with a bound account (config sync), or enter the vendor's CNAME (schedule-only; "Other" works as the vendor).
- Under Sites and lines, bind sites to the access point as primary or backup and choose a scheduling strategy (the three strategies are explained under cross-CDN scheduling).
- Sync status shows whether the configuration reached the vendor; Switching history lists every switch with time, line and reason.
To bring over sites that already run at a vendor, use Import and migrate. Site users can bind their own Cloudflare account or enter their own CNAME under Account → Third-party CDN when their plan allows it.
Main settings
| Setting | What it does |
|---|---|
| Credentials | Sent only to this control plane and shown as a fingerprint afterwards; rotate, disable or delete (deleting removes the binding only, nothing in the vendor account) |
| Domain limit | Defaults to the vendor's free quota; creation stops before you exceed it |
| Access mode | Config sync or schedule-only, fixed once created; open a new access point to switch |
| Origin | Optional; the site's own origin is used when empty |
| Probe headers | Optional, up to 8, such as a check header the vendor requires |
| Line | Default, or per line: China Telecom, Unicom, Mobile, overseas (needs a DNS provider with line support) |
Typical uses
- Own nodes in China, Cloudflare overseas: bind a Cloudflare access point to the overseas line and leave the other lines on your line group.
- A cloud CDN as backup: own nodes as primary, the CDN as backup; traffic moves over when the primary is unhealthy and back after the minimum stay.
- Sites with complex rules already set up at a vendor: use schedule-only and treat the vendor as a scheduling target and backup.
Limits and notes
- Third-party CDN supplies serve your own sites only; they cannot be listed on the node market or combined into resold offers.
- Vendors differ: settings a vendor does not support are listed before publishing, and vendors such as ESA require site domains under their site's main domain.
- Site users can currently bind Cloudflare accounts only, and the user console marks third-party CDNs "untested": check on the vendor side at small scale first.
- When the DNS provider has no line support, only global primary/backup works, with no split by region or carrier.
- When the licence lapses, sync, observation and automatic switching stop, DNS keeps its last state and resources in your account stay; after renewal a full reconciliation runs before automation resumes.