Build
Cache
Accelerate websites and APIs with distributed caching on the Azion Web Platform. Control TTL, cache policies, and large file optimization to offload your origin and improve Core Web Vitals.
origin traffic reduction with smart caching
cache-hit response times globally
distributed locations serving cached content
Offload origin during traffic spikes
Serve repeat requests from cache to reduce origin traffic during peaks and keep response times stable.
Improve SEO with faster load times
Reduce TTFB on cache hits and improve Core Web Vitals—supporting better crawlability and page ranking.
Stay available during origin issues
Use stale cache and multi-level caching to keep content online while your origin recovers or revalidates content.
"I really like the depth of cache rules that I can apply at the edge. There are things that we would not be able to do using solutions from other vendors. In terms of performance, compliance to Contabilizei's rules and delivery standards, we are very satisfied with Azion's performance."
Marcelo Pacheco
DevOps Specialist at Contabilizei
Accelerate websites and APIs with distributed caching
Intelligent routing and origin offload
Route requests through Azion's distributed infrastructure and serve content from cache when possible.
Cache reduces origin load by serving repeat content from the distributed cache.
Distributed cacheOrigin offloadCache rulesFast delivery
High-availability caching for critical traffic
Keep websites and APIs fast—even when the origin is slow or unavailable.
Use protocol optimizations, persistent connections, and stale cache to continue serving the most recent cached responses during origin failures or cache revalidation.
Stale cachePersistent connectionsProtocol optimizationHigh availability
Documentation and examples
Frequently Asked Questions
What is Azion Cache?
Azion Cache is a distributed caching solution for accelerating websites and APIs. Key features include: 90% origin traffic reduction, sub-5ms cache-hit response times, tiered cache architecture, stale-while-revalidate support, and large file optimization. It improves Core Web Vitals and stabilizes latency during traffic spikes.
What's the difference between Browser Cache Settings and CDN Cache Settings?
Browser Cache Settings controls how long content is cached in the user's browser. CDN Cache Settings controls how long content is cached in Azion's distributed infrastructure. You can honor origin headers or override TTLs for each layer.
Can Cache honor Cache-Control and Expires headers from my origin?
Yes. You can configure both Browser Cache Settings and CDN Cache Settings to honor cache definitions sent by your origin through HTTP headers (Cache-Control and Expires).
How can I set cache TTL under 60 seconds?
To set CDN cache TTL values under 60 seconds, you must enable the Application Accelerator module.
How do I control what defines the cache key (cookies and query strings)?
Use Advanced Cache Key to customize caching behavior based on cookies and query strings. This helps you cache personalized or segmented content while keeping cache efficiency high.
How do I purge or invalidate cached content?
Use Real-Time Purge to expire cached content by URL, cache key, or wildcard. Purges are queued for execution and may take time to propagate across the distributed infrastructure.
What happens if my origin is slow or unavailable?
Enable Stale Cache to serve stale content when there is a problem with your origin servers, improving availability for end users during incidents.
How does Cache handle large files?
Large File Optimization splits large files into fragments with a default fragment size of 1024 kB. This improves delivery of large assets and allows caching of file segments.
Can I cache POST or OPTIONS requests?
By default, Cache caches GET and HEAD. You can enable caching for POST and OPTIONS, but these cache options require the request body to be part of the cache key and depend on Application Accelerator.
How do I keep long-lived assets cached longer with an additional cache layer?
Azion offers an additional cache layer called Tiered Cache designed for assets that can remain cached for long periods. It can be enabled on cache policies with a Maximum TTL in Tiered Cache of 2,592,000 seconds (default TTL 60 seconds).