CDN for Ghost
Publishing should be fast for readers, not only for editors.
Ghost blogs and publications ship large theme assets and images with every post. A single origin makes first-time readers in other regions wait on that host.
Cache the Ghost theme, content images and public post HTML at Cloud CDN. Keep Ghost Admin and members-only content on the origin unless it is truly shareable.
Why teams use Aptranet
What CDN for Ghost 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.
Posts served from the nearest edge
Public post HTML and theme assets are cached on 210+ PoPs with 30 ms average latency.
Featured images without extra storage jobs
Convert and resize Ghost images at the edge instead of generating every size in content storage.
Memberships stay dynamic
Members-only posts, admin and Stripe-related routes bypass cache so access control stays in Ghost.
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.
- 1Point Cloud CDN at the Ghost origin
Pull the Ghost host, including /content/images and theme assets.
- 2Cache public reading paths
Cache anonymous posts, tags and the homepage. Bypass Ghost Admin and member sessions.
- 3Purge on publish
Invalidate the post URL, homepage and tag pages when a story goes live.
- 4Attach the publication domain
Map the custom domain and certificate after a successful test hostname.
Outcomes
What changes once the hostname is on Aptranet.
- Readers hit cached posts and images worldwide
- Ghost Admin remains on the origin
- Members-only content is not shared through cache
- Publish can purge the reading path immediately
Keep reading
Related pages
More CDN use cases on the same Cloud CDN footprint.
Frequently Asked Questions
Yes for anonymous readers. Purge the homepage when a new post is published so it appears immediately.
Bypass cache for authenticated member responses. Public teasers can still be cached.
Use Cloud CDN when you control DNS for the reading domain and can pull from the Ghost origin.
Public images referenced by posts and pages are cached. Transactional mail remains a Ghost concern.