Edge
Caching that keeps protected traffic fast
ArxLayer caches and accelerates content at the same edge that inspects and filters every request. Your visitors get fast responses; your origin gets fewer hits and a smaller attack surface.
The problem
Bolting a CDN onto security creates seams
When caching and protection run in different layers, requests are inspected twice, configs drift, and an attacker can sometimes reach cache or origin around the guard.
Two layers, two policies
A separate CDN and a separate WAF mean two control planes, two sets of rules, and gaps between them.
Cache that bypasses the guard
If the cache sits in front of enforcement, requests can be served or revalidated without ever being inspected.
Speed paid for in safety
Tuning a CDN for raw throughput often means turning protection down. Fast and safe should not be a trade-off.
What you get
Acceleration inside the protection layer
Caching is a supporting capability of the ArxLayer edge, not a separate product. Every cached or accelerated request still passes the same enforcement boundary.
Edge caching
Serve cacheable responses from the edge to cut latency and absorb load close to your visitors.
Origin offload
Fewer requests reach your origin, which lowers cost and shrinks your exposed surface.
Inspected, then served
Requests pass enforcement at the edge before any cache or origin response is returned.
Cache rules you control
Set what to cache, for how long, and what to bypass, per route, through the API-first control plane.
Fast purge and revalidation
Invalidate cached content when it changes, with versioned, reversible configuration.
One edge for both jobs
Protection and delivery share the same path, so there is no second hop and no policy drift.
How it works
Fast and protected from one edge
Route through ArxLayer once. Inspection and caching happen on the same request path.
Point your domain
Send traffic through ArxLayer Edge. Protection is on from the start, with sensible default cache behavior.
Inspect every request
Each request is evaluated at the edge before a cached or origin response is served.
Serve and offload
Cacheable responses return from the edge; the rest reach a lighter, better-protected origin.
FAQ
Questions, answered
- Is ArxLayer a CDN?
- No. ArxLayer is a protection platform with caching and acceleration built into its edge. Delivery supports protection; it is not the product.
- Does caching let requests skip the WAF?
- No. Enforcement runs at the edge before any cached or origin response is returned, so cached traffic is still inspected.
- Can I control what gets cached?
- Yes. You define cache and bypass rules per route through the API-first control plane, and every change is versioned and reversible.
- How do I clear stale content?
- Purge or revalidate cached content when it changes. Cache configuration rolls out as a new version you can review and roll back.
Keep protected traffic fast
Run protection and caching from one edge, so your visitors stay fast and your origin stays covered.