CDN for Remix
Keep Remix loaders honest. Cache what they can share.
Remix documents and assets are requested on every navigation. Public marketing and content routes can be cached; session loaders cannot.
Cache hashed build assets globally. Cache anonymous document GET responses. Bypass loader output that depends on cookies or session.
Why teams use Aptranet
What CDN for Remix 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.
Build assets at 210+ PoPs
Hashed JS and CSS from the Remix build are cached with long TTLs.
Public documents from cache
Anonymous content routes can be served from the edge after the first loader run.
Session loaders stay private
Authenticated documents bypass cache so Remix session guarantees hold.
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.
- 1Pull the Remix origin
Connect the Node or hosting origin that serves the Remix app.
- 2Cache assets and public documents
Long TTL for hashed files. Conditional cache for anonymous HTML.
- 3Bypass cookie-specific routes
If a loader varies on session, do not cache that document.
- 4Purge on deploy
Invalidate HTML when a new Remix release ships.
Outcomes
What changes once the hostname is on Aptranet.
- Remix static assets are global
- Public documents can be cached
- Session routes remain origin-dynamic
- Deploys purge document HTML
Keep reading
Related pages
More CDN use cases on the same Cloud CDN footprint.
Frequently Asked Questions
Only when the JSON is identical for every anonymous client. Resource routes with user data must bypass cache.
Let Remix set headers per route, then honour them at Cloud CDN. Add purge for deploys.
Yes. Cloud CDN fronts whichever origin adapter you run.
Actions are not cached. Only safe GET document and asset responses are.