Cloud CDN
CMS and commerce
- CDN for WordPressMake WordPress feel local in every market.
- CDN for WooCommerceA faster aisle, without moving checkout.
- CDN for ShopifyAdd an edge you control in front of Shopify.
- CDN for MagentoTake Magento static content off the application nodes.
- CDN for DrupalLet Drupal render. Let the edge repeat.
- CDN for JoomlaPublic Joomla traffic should not wait on the CMS host.
- CDN for GhostPublishing should be fast for readers, not only for editors.
- CDN for WebflowKeep Webflow for design. Add an edge you operate.
- CDN for SquarespaceGive Squarespace sites an edge you can measure.
- CDN for WixA delivery layer beside the Wix site builder.
- CDN for PrestaShopMove PrestaShop media and theme traffic to the edge.
- CDN for BigCommerceAn edge for BigCommerce storefronts you control.
- CDN for StrapiKeep Strapi as the CMS. Let the edge deliver.
- CDN for ContentfulA delivery edge in front of the Contentful stack.
- CDN for SanitySanity for content. Cloud CDN for delivery.
- CDN for HubSpotCampaign pages deserve the same edge as the product.
- CDN for Craft CMSCraft renders. The edge repeats the result.
- CDN for SitecoreA global delivery layer in front of Sitecore.
Cloud CDN
Frameworks and runtimes
- CDN for Next.jsPut Next.js in front of a global edge, not a single region.
- CDN for NuxtNuxt builds. Cloud CDN delivers the result worldwide.
- CDN for RemixKeep Remix loaders honest. Cache what they can share.
- CDN for AstroAstro already ships static HTML. Give it a global edge.
- CDN for GatsbyGatsby generates the files. Cloud CDN places them next to readers.
- CDN for HugoHugo is fast to build. Make it fast to fetch as well.
- CDN for AngularAngular bundles should load from the nearest edge.
- CDN for ReactReact ships JavaScript. The edge should ship it first.
- CDN for VueVue apps should not wait on a single static origin.
- CDN for SvelteKitSvelteKit prerender is better with a global cache.
- CDN for LaravelLaravel should render. The CDN should repeat.
- CDN for DjangoTake staticfiles and media off the Django workers.
- CDN for Ruby on RailsLet Rails run the app. Let Cloud CDN run the assets.
- CDN for PHPPHP should run application code, not static files.
- CDN for Node.jsKeep Node busy with application work, not CSS.
- CDN for static sitesStatic files still need a global edge.
Cloud CDN
Workloads
- CDN for imagesOne source image. Every layout, at the edge.
- CDN for videoVideo should start from the nearest edge, not the origin disk.
- CDN for live streamingLive audiences should not all land on the encoder.
- CDN for APIsNot every API response needs to hit the application.
- CDN for software downloadsInstallers should not all pull from one origin disk.
- CDN for game downloadsLaunch day should hit the edge, not the build origin.
- CDN for websitesEvery website still has an origin. Visitors should not.
- CDN for web applicationsThe app origin should see users, not every CSS file.
- CDN for mobile appsMobile clients are already global. The origin should not be the bottleneck.
- CDN for large filesBig objects need an edge, not a bigger origin pipe.
- CDN for SPAsThe SPA shell is static. Treat it that way.
- CDN for web fontsSelf-host fonts on an edge you control.
- CDN for landing pagesAd traffic should land on an edge, not a CMS.
- CDN for documentationDocs are static. Readers are not in one region.
Cloud CDN
Capabilities
- CDN image optimizationTransform images at delivery time, not in a batch job.
- CDN Origin ShieldThe origin should see one miss path, not every PoP.
- HTTP/3 CDNModern transport on every point of presence.
- CDN DDoS protectionThe public hostname should fail closed at the edge, not at origin.
- CDN cache purgeCache is only useful if you can invalidate it.
- CDN WebSocketsOne hostname for static assets and live sockets.
- CDN Brotli compressionText should not travel uncompressed from a global edge.
- CDN custom SSLCertificates live with the distribution, not on a box you patch.
- CDN token authenticationA cached object can still be gated.
- CDN BYOIPKeep the addresses. Change the delivery network.
Also on this network
Cloud CDN and Cloud DNS share 210+ locations. Delivery and authoritative routing are separate products with their own landing pages.
Browse DNS use cases