CDN for Astro
Astro already ships static HTML. Give it a global edge.
Astro output is mostly static, but a single object store or origin still makes every image and HTML file travel from one region.
Use the Astro build as a Cloud CDN origin. Cache HTML and assets globally, transform images at the edge, and keep server islands dynamic when they cannot be shared.
Why teams use Aptranet
What CDN for Astro 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.
Static HTML worldwide
Pages are served from 210+ PoPs with 30 ms average latency.
Content images on demand
Resize and convert Astro content images without rebuilding every breakpoint.
Server islands stay optional
Cache static routes. Bypass server islands that are user-specific.
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.
- 1Publish the Astro build to an origin
Use a files host, a VM or a static host that Cloud CDN can pull.
- 2Cache pages and hashed assets
Long TTL for fingerprinted files. Purge HTML on each build.
- 3Add image transformation
Convert hero and content images to WebP or AVIF at delivery time.
- 4Map the site domain
Attach a managed or custom certificate and cut over DNS.
Outcomes
What changes once the hostname is on Aptranet.
- Astro sites are cached on 210+ PoPs
- Builds purge HTML immediately
- Images can be adapted without extra build steps
- Hybrid server routes can stay dynamic
Keep reading
Related pages
More CDN use cases on the same Cloud CDN footprint.
Frequently Asked Questions
Yes. Cache static and shareable SSR output. Bypass personalised server routes.
You can still use Astro assets as origin files. Cloud CDN caches and can further transform them.
Purge HTML and any unhashed paths as part of the deploy pipeline.
Yes. Cloud CDN supports HTTP/3, HTTP/2 and Brotli or Gzip compression.