FlyingCDN review: what the FlyingPress add-on CDN does, what it costs per domain and who needs it 

What is FlyingCDN, and why is it tied to FlyingPress?

FlyingCDN is a content delivery network sold by FlyingWeb LLC as an optional add-on to its FlyingPress WordPress performance plugin, and it is built on Cloudflare’s Enterprise network rather than on the vendor’s own servers. Where a conventional CDN like Bunny or the free tier of Cloudflare serves your images and scripts from edge locations, FlyingCDN also caches whole HTML pages at the edge, compresses and converts images to WebP in flight, routes traffic over Cloudflare’s Argo smart routing, and fronts the site with Enterprise DDoS protection and a web application firewall. The vendor’s own comparison table claims access to 330 points of presence with all of them unlocked, which is the Enterprise plan’s advantage over Cloudflare’s free and Pro tiers, where some regions are limited.

The reason it exists only for FlyingPress customers is integration, and the vendor says so in its FAQ: FlyingCDN is exclusively available to FlyingPress users to ensure optimal integration and performance. In practice that means the plugin knows when a page changes and purges it from the edge, and the CDN knows which cookies and query strings to ignore so that the cache-hit ratio stays high. A FlyingCDN review therefore has two prices to weigh, the $10 a month for the CDN and the $59 a year minimum for the plugin, and one question to answer: whether the Enterprise network is worth paying for when FlyingPress already ships a free integration with Cloudflare’s own edge cache.

The numbers on the vendor’s pages

The FlyingCDN homepage quotes 310 edge locations in 120-plus countries in its features section and 330 points of presence in its comparison table; both are Cloudflare Enterprise figures and the difference is the vendor updating one page and not the other. It promises a time to first byte under 50 ms worldwide, a free wildcard SSL certificate, cached pages even with items in a WooCommerce cart, cached pages for logged-in users, and a 7-day free trial with no card. The FlyingPress documentation, which is where the detailed FlyingCDN articles live, has ten of them covering setup, billing, SSL, DNS, WebP delivery and cache purging, dated May to October 2025.

How much does FlyingCDN cost, and what does the bill look like at real traffic?

FlyingCDN charges $10 per domain per month, which includes 100 GB of bandwidth, and $5 for every additional 100 GB, billed monthly in 100 GB increments. Bandwidth means all traffic through the CDN, both cache hits served from the edge and misses forwarded to your origin. A site is a root domain, so www, cdn and blog subdomains count as one site, but a second root domain is a second $10. Deleting and re-adding a site counts as a new site and may trigger a new charge. Usage and charges are visible in the FlyingCDN dashboard, and the bill resets every month. On top of that you need a FlyingPress licence: $59 a year for one site, $109 for three, $229 for 25 or $279 for unlimited.

FlyingCDN rates from the vendor’s billing documentation and homepage on September 4, 2026; the per-year and total columns are our multiplication. The 1 TB row assumes ten 100 GB increments: $10 plus nine times $5.

What a real site uses

A content site with 100,000 page views a month and an average page weight of 1.5 MB moves roughly 150 GB, which lands in the $15 tier. A WooCommerce store with 30,000 visits and heavy product imagery may use less, because the WebP conversion cuts image weight by a large fraction before it leaves the edge. A site that already compresses images and serves 2 MB pages to a million visitors a month is at 2 TB and $105 a month, at which point Bunny’s $0.01 per GB in Europe and North America, about $20 for the same traffic, is the obvious comparison, minus everything Bunny does not include. The trial is the way to find out: seven days on the real site, then read the dashboard.

No refunds, and no PayPal

The refund policy page says it plainly: because payments cover upstream CDN providers, FlyingCDN cannot offer refunds, and requests are considered case by case through support at the vendor’s discretion. The FAQ adds that PayPal is not accepted because of the usage-based billing, so it is cards only. The 7-day trial with no card is the protection; use it on the production domain, not a staging copy, because the whole point is traffic. Read the billing documentation before the trial ends, and if the numbers work, activate FlyingCDN from the FlyingPress CDN tab.

What does FlyingCDN actually do that a normal CDN does not?

The feature half of this FlyingCDN review is short, because the difference between FlyingCDN and a static-asset CDN is one thing: FlyingCDN caches the HTML itself at the edge, and everything else on the feature list follows from that. The homepage lists twelve features: edge page caching, traffic spike handling by serving from the edge, image compression, WebP conversion without changing URLs, 310 edge locations, sub-50 ms TTFB, a wildcard SSL certificate, DDoS protection and firewall, browser caching headers, WooCommerce-aware caching with items in the cart, cached pages for logged-in users, and automatic ignoring of unnecessary cookies and query strings to keep the hit ratio high.

Edge page caching, and why WooCommerce matters

Most CDNs, including Cloudflare’s free plan without APO, pass HTML through to your server on every request and only cache the images, CSS and scripts around it. That leaves time to first byte at the mercy of your hosting and the distance to it. FlyingCDN serves the cached page from the nearest edge, which is what the sub-50 ms claim rests on, and it does so for logged-in users and for shoppers with items in the cart, which the vendor’s comparison table marks as unsupported on Cloudflare, RocketCDN and Bunny. For a store, that is the feature: the moment a visitor adds a product, most page caches bypass and the site slows down exactly when it matters.

The Enterprise extras

Argo smart routing, which Cloudflare sells as an add-on from $5 a month, is included. Enterprise DDoS protection and the Enterprise WAF are included. Image optimization equivalent to Cloudflare’s Polish, which requires the $20 a month Pro plan, is included. HTTP/3, Brotli compression and TLS are standard. The same-URL design means images and pages keep their original addresses, so there is no cdn.example.com subdomain to configure and no risk of duplicate-content URLs in search results.

How is FlyingCDN set up, and what can go wrong with DNS and SSL?

Setup is a DNS change, not a plugin toggle, and that is the part of this FlyingCDN review most likely to save you an evening. The documented steps are four. Add the site in the FlyingCDN dashboard using the root domain without www and your server’s IP address. Update DNS: add a new CNAME record for the wildcard SSL validation, and point the root domain’s A record at the IP that FlyingCDN provides; if the domain is on Cloudflare, switch the proxy off for those records so they are DNS only. Copy the FlyingCDN API key into FlyingPress under the CDN tab. Verify by loading the site in a private window and checking for a flyingcdn-cache: HIT response header. The vendor’s Flying TTFB tool then shows time to first byte by region, with the second run showing the cached result.

Where it sticks

Two status messages cover most support tickets. “Pending validation” means the SSL validation CNAME has not been detected; the documented causes are the record being proxied through Cloudflare, being a TXT instead of a CNAME, an old TXT record at the same name, CAA records on the domain, or Cloudflare’s Universal SSL still enabled, which conflicts with external certificate validation. “DNS update in progress” means the A record has not propagated or the Cloudflare proxy is still on. Both resolve automatically once the records are right, usually within a minute, and the vendor points you to a public DNS lookup to confirm.

SSL renewals and your origin certificate

FlyingCDN issues and renews its wildcard certificate with a DNS-01 challenge through that CNAME, so as long as the record stays in place, renewals need no action. Your origin server keeps its own certificate, and the vendor recommends a standard HTTP-01 certificate there, not a wildcard, because FlyingCDN bypasses the .well-known path to let it validate. Miss that detail and the origin certificate can lapse behind the CDN. Follow the setup guide rather than winging it; the steps are short and the order matters.

How does the image optimization work, and when does it skip an image?

Images are compressed and converted to WebP at the edge without changing their URLs, and the documentation is unusually clear about when that does not happen. The conversion is skipped, with a reason exposed in a Cf-Polished response header, when the input is too large or complex (the vendor suggests staying under 10 MB and within 1,000 to 2,000 pixels), when the original is already fully compressed, when the WebP version would be bigger than the original, when the file is corrupt, when the format is unsupported such as BMP or TIFF, or when another plugin is altering the image. A server sending a Vary header with anything other than accept-encoding also blocks optimization. To check delivery, open the network tab and look for content-type: image/webp on an image request.

This is separate from the image optimization inside FlyingPress itself, which since version 5.3 converts JPEG and PNG originals to WebP or AVIF on the vendor’s cloud servers and saves them into your uploads folder. The plugin’s version changes the files on disk; the CDN’s version changes what leaves the edge. Running both is allowed, and the documentation notes that already-optimized originals are simply passed through. A site that has already converted its library with the plugin gets less from the CDN’s image layer and more from the page caching.

FlyingCDN or FlyingPress’s free Cloudflare integration: which one do you need?

This is the decision most FlyingPress users actually face, and the one a FlyingCDN review has to settle, because since version 5.1 in August 2025 the plugin can cache full pages at Cloudflare’s edge on a free Cloudflare account, with automatic zone detection and API token support, and without paying for APO. That integration costs nothing beyond the licence. FlyingCDN costs $10 a month. The vendor’s own FAQ answers the question of why you would pay: the free path gives you page caching, and FlyingCDN gives you the Enterprise network with every point of presence unlocked, Argo routing, Polish-grade image optimization, caching with cart items, caching for logged-in users, and automatic purging with no extra plugins.

Feature attributions from the FlyingCDN homepage comparison and FAQ, and Cloudflare’s own plans page for the Pro, APO and Argo prices, on September 4, 2026.

The practical rule: a regional business site or blog already on Cloudflare should use the free integration and stop. A WooCommerce store, a membership site with logged-in readers, or a publisher with a global audience gets the things the free path cannot do, and $10 a month is less than the cheapest Cloudflare Pro plan that would give you Polish alone.

How does FlyingCDN compare with Cloudflare APO, Bunny and RocketCDN?

The vendor publishes its own comparison table, and most of it checks out against the rivals’ pricing pages, with one figure out of date.

Prices from each vendor’s own page on September 4, 2026. The FlyingCDN comparison table still lists RocketCDN at $8.99; WP Rocket’s RocketCDN page shows $7.99.

On raw bandwidth Bunny wins by a wide margin: 100 GB of European and North American traffic is $1 there and $10 on FlyingCDN. But Bunny is a static CDN on a separate domain with no HTML caching, so your time to first byte still depends on your host, and its optimizer is a separate charge. Cloudflare Free with APO at $5 is the closest functional match for the page caching and is half the price, but images stay unoptimized without the $20 Pro plan, cart and logged-in pages are not cached, and you are on the plan-limited network. RocketCDN Pro at $7.99 is the cheapest of the four, is static only, and needs WP Rocket rather than FlyingPress. The honest summary is that FlyingCDN is not the cheapest CDN; it is the cheapest way to get the Enterprise feature set, and only if you already pay for FlyingPress.

Where does FlyingCDN fall short?

The gaps this FlyingCDN review found are structural, and the vendor does not hide them.

Locked to FlyingPress

You cannot buy FlyingCDN alone. The minimum entry is a $59 FlyingPress licence, so the first-year cost for one small site is $179, not $120. If you are happy with WP Rocket or a host-level cache, this product is not available to you.

You give up your Cloudflare configuration

The records that point to FlyingCDN must be set to DNS only, and the FAQ states that with the proxy off, the rules and settings in your own Cloudflare account no longer apply. Page rules, firewall rules, redirects and Workers you built there stop working for that traffic. FlyingCDN’s Enterprise WAF replaces some of that, but you do not configure it.

No refunds, usage billing, cards only

The refund page says payments cannot be refunded because they fund upstream providers, with exceptions at the vendor’s discretion. Bandwidth is billed in $5 steps per 100 GB with no cap you can set from the documentation, and PayPal is not accepted. A traffic spike is served from the edge, which is the point, and billed, which is the consequence.

Setup is DNS work

A CNAME for validation, an A record change, the Cloudflare proxy off, Universal SSL off, CAA records removed if present, and the right certificate type on the origin. None of it is hard, all of it is the kind of thing that generates the “Pending validation” ticket the vendor wrote an article about. A November 2024 one-star review of FlyingPress on Trustpilot complains that the CDN failed and a support agent was unhelpful; the company’s reply lists the configuration steps that were missed. Both can be true.

Small vendor, two documentation homes

FlyingCDN has its own site with a features list, pricing and FAQ, but the operational documentation lives on the FlyingPress docs site, and the two disagree on the point-of-presence count. The support address is the plugin’s. For a service that sits in front of your entire domain, that is a smaller company than Cloudflare or Bunny to depend on.

Who should buy FlyingCDN, and who should not?

FlyingCDN fits a FlyingPress site whose audience is global, whose pages change per visitor, or whose images are the weight. Three cases make it concrete.

Scenario one: a WooCommerce store with customers on three continents

The store already runs FlyingPress Starter. Cart pages and logged-in account pages bypass every ordinary cache, so shoppers get origin speed from the moment they add a product. FlyingCDN caches those pages at the edge and converts the product images to WebP in flight. At 150 GB a month the bill is $15, plus the $59 licence, $239 for the year. Compare that with Cloudflare Pro at $20 a month for Polish alone, with no cart caching. This is the case where FlyingCDN through FlyingPress is the cheapest option that does the job.

Scenario two: a publisher with 500,000 page views a month

Roughly 750 GB at 1.5 MB per page, so $45 a month, $540 a year, plus the licence. That is a real cost, and the alternative is Bunny at about $8 for the same traffic with a separate image optimizer, or Cloudflare Free plus APO at $5 with no image optimization. The publisher should run the seven-day trial, read the dashboard, and decide whether the sub-50 ms time to first byte in every region is worth the difference. For an ad-funded site where Core Web Vitals move revenue, it often is.

Scenario three: a local service business on shared hosting

One region, 5,000 visits a month, no logins, no cart. Use FlyingPress’s free Cloudflare integration for page caching and the plugin’s built-in image optimization for the library, and keep the $120. FlyingCDN would work; it would also be $10 a month for a network the site does not need.

Who should not buy

Do not buy FlyingCDN if you do not use FlyingPress, if you rely on Cloudflare rules or Workers you cannot give up, if you need PayPal or a refund window, or if your bandwidth is measured in terabytes and you serve mostly static files, where Bunny’s per-gigabyte pricing is a tenth of the cost.

Common buying mistakes

Turning it on before trying the free Cloudflare integration. Leaving the Cloudflare proxy on and waiting days for validation. Running the trial on a staging domain that gets no traffic and learning nothing about the bill. Forgetting that the origin needs its own certificate. Paying $10 a month for a regional site whose visitors are all within 500 km of the server.

FlyingCDN pros and cons

FlyingCDN

• Cloudflare Enterprise network with Argo routing, Enterprise DDoS protection and WAF, for $10 a month per domain, less than Cloudflare’s own Pro plan.
• Full HTML caching at the edge, including pages with cart items and for logged-in users, which Cloudflare APO, Bunny and RocketCDN do not cache.
• Image compression and WebP conversion at the edge without changing URLs, with the skip reason exposed in a response header.
• Wildcard SSL issued and renewed automatically through a single DNS record, and purging wired into FlyingPress so a page edit clears the edge.
• Seven-day trial with no card, subdomains included in one site, and a clear billing document with worked examples.

• Only available to FlyingPress customers, so the real entry price is $179 in year one for one site.
• No refunds by policy, usage billing in $5 steps per 100 GB, and no PayPal.
• Your own Cloudflare rules, firewall and Workers stop applying once the proxy is off for FlyingCDN records.
• Setup is DNS work with several documented failure modes, and origin SSL must be configured the vendor’s way.
• Per gigabyte it is far more expensive than Bunny, and the free Cloudflare integration in FlyingPress already covers page caching for many sites.

Frequently asked questions

What is FlyingCDN?

FlyingCDN is an optional add-on CDN for the FlyingPress WordPress plugin, built on Cloudflare’s Enterprise network. It caches full pages and assets at the edge, compresses images and converts them to WebP, includes Argo smart routing, Enterprise DDoS protection and a WAF, and issues a wildcard SSL certificate. It costs $10 per domain per month with 100 GB included.

How much does FlyingCDN cost?

$10 per domain per month including 100 GB of bandwidth, then $5 for each additional 100 GB, billed monthly in 100 GB steps. Bandwidth counts cached and uncached traffic. Subdomains belong to the same site. You also need a FlyingPress licence, from $59 a year for one site, because FlyingCDN is not sold separately.

Can I use FlyingCDN without FlyingPress?

No. The vendor’s FAQ states that FlyingCDN is exclusively available to FlyingPress customers. The plugin supplies the cache purging, the API key connection and the settings screen, so the CDN has no standalone dashboard workflow for other setups.

Does FlyingCDN replace Cloudflare APO?

Yes. The vendor’s FAQ says APO is not needed with FlyingCDN, which serves pages from the edge in the same way. FlyingCDN adds the Enterprise network, Argo routing, image optimization, cached pages with cart items and for logged-in users, and automatic purging from FlyingPress, none of which APO provides on its own.

Do I have to change my DNS?

Yes. You add a CNAME record for SSL validation and point your root domain’s A record to the IP FlyingCDN gives you. If your DNS is on Cloudflare, those records must be set to DNS only with the proxy off, and Universal SSL must be disabled. Your existing Cloudflare rules stop applying to that traffic.

Is there a free trial or a refund?

There is a 7-day free trial with no card required, cancellable at any time. There are no refunds by policy, because payments fund upstream providers; the vendor considers requests case by case through support. PayPal is not accepted because of usage-based billing.

Why are some images not served as WebP?

The edge skips conversion when an image is too large or complex, already fully compressed, would be bigger as WebP, is corrupt, is in an unsupported format such as BMP or TIFF, is being altered by another plugin, or when the server sends a Vary header with values other than accept-encoding. The reason is shown in the Cf-Polished response header.

Is this FlyingCDN review saying it beats Bunny?

Not on price per gigabyte: Bunny charges $0.01 per GB in Europe and North America with a $1 minimum, a tenth of FlyingCDN’s rate. FlyingCDN wins on what is included, HTML at the edge with cart and logged-in caching, image conversion, Argo and Enterprise security, none of which Bunny’s standard CDN provides. Choose by whether you need those.

Which should you choose?

The conclusion of this FlyingCDN review: buy it if you run FlyingPress and your site is a store, a membership site or a global publication, because nothing else puts Cloudflare Enterprise page caching, Argo, image conversion and cart-aware caching in front of a WordPress site for $10 a month. Run the seven-day trial on the live domain, watch the bandwidth figure, and price the FlyingPress licence into the decision, because the two are sold together.

Do not buy it if your visitors are in one region, if you already lean on Cloudflare rules you cannot give up, if you need PayPal or refunds, or if you push terabytes of static files, where Bunny is far cheaper. For most FlyingPress users the right order is the free Cloudflare integration first, the plugin’s own image optimization second, and FlyingCDN only when a store, logins or a worldwide audience makes the Enterprise network earn its ten dollars.