CDN for Strapi
Keep Strapi as the CMS. Let the edge deliver.
Strapi origins are often asked to serve every upload and many public REST or GraphQL reads. That collides with editorial work as soon as traffic grows.
Cache the uploads directory and eligible public API GETs at Cloud CDN. Put the front end on the same edge. Keep Strapi admin and mutations on the origin.
Why teams use Aptranet
What CDN for Strapi looks like on this network.
Cloud CDN caches and accelerates eligible content on 210+ points of presence, with Origin Shield when the origin must stay out of the way.
Uploads delivered globally
Media library files are cached and can be transformed per front-end layout.
Public API GETs at the edge
Cacheable content endpoints are served from 210+ PoPs so Strapi Node processes fewer repeat reads.
Admin stays private
Strapi admin and write APIs are not cached and need not be publicly exposed.
How to set it up
A cutover you can validate before DNS moves.
Create the Cloud CDN configuration, prove it on an Aptranet hostname, then point production DNS when the path looks correct.
- 1Put media on Cloud CDN
Use the distribution as the public uploads hostname.
- 2Cache safe API GETs
Set TTLs for public content types. Bypass authenticated and mutation routes.
- 3Purge on publish
Invalidate media URLs and content endpoints when editors publish.
- 4Front the website too
Point the Next.js, Nuxt or static front end at the same edge network.
Outcomes
What changes once the hostname is on Aptranet.
- Strapi uploads are served from the edge
- Public read APIs can be cached
- Admin and writes remain on origin
- Front-end assets share the same CDN
Keep reading
Related pages
More CDN use cases on the same Cloud CDN footprint.
Frequently Asked Questions
Cache GET-style or persisted queries that are truly public. Do not cache requests that include draft or user-specific data.
Draft preview must bypass cache. Only published content should be eligible.
Yes. Use the object-store hostname as an origin, or pull through Strapi and cache the public URL at Cloud CDN.
Yes. Cloud CDN supports secure token authentication for paths that should not be world-readable.