Accelerate content delivery globally
Serve cached content with fast response times. Reduce origin load and keep applications fast during traffic spikes.
Global content delivery close to users
Serve cached websites, APIs, and files from Azion's distributed architecture to reduce latency and absorb demand before it reaches your origin.
Faster responses with less origin work
Improve cache-hit performance while cutting repeated origin requests, infrastructure load, and bandwidth pressure during peak traffic.
Simple control over freshness
Configure TTLs, cache keys, stale content, and global purges so teams can keep content fast without complex CDN operations.
Configure smarter cache policies
Set browser and edge TTLs, enable tiered cache, and keep content fresh with stale revalidation. Azion Platform helps improve hit ratio, lower latency, and reduce origin bandwidth.
Azion CLI REST API Console UI Terraform
High-availability caching for critical traffic
Use protocol optimizations, persistent connections, and stale cache to keep serving the latest cached responses during origin failures or revalidation, so websites and APIs stay fast.
Stale cache Persistent connections Protocol optimization High availability
Fine-tune cache policies for your content
Configure caching policies that match your content strategy.
Learn More
Use cases
"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
Frequently Asked Questions
What is Azion Cache?
Azion Cache is a distributed caching solution for accelerating websites and APIs. Key features include: lower origin traffic, fast 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 short cache TTLs?
To set short CDN cache TTL values, 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).
What is the difference between Azion Cache and standard CDNs?
Azion Cache is integrated with the Azion Web Platform, providing unified management for caching, security, and compute. Unlike standalone CDNs, it works seamlessly with Functions for dynamic cache manipulation, WAF for protected caching, and Application Accelerator for advanced TTL control.
How does Cache integrate with other Azion products?
Cache integrates with Rules Engine for conditional caching policies, Application Accelerator for short TTLs, Image Processor for optimized image caching, and Functions for programmatic cache key manipulation. This unified approach reduces complexity compared to multi-vendor solutions.
A full-stack platform that scales instantly
Access to all features.