CDN edge caching
Last updated 2026-06-14
Definition
CDN edge caching keeps a copy of responses close to you on a content network, so requests do not always travel to the origin server. The result is faster page loads and less load on Quri itself. The cache is keyed by who you are, so one workspace never serves its cached response to another.
How to do this in Quri
- Use Quri normally — edge caching runs underneath the pages you load.
- Notice that repeat loads of the same view feel quick because the edge already has them.
- Trust that the cache is keyed to your session, so your responses stay yours.
- Use the refresh control when you want to skip the cached copy and pull fresh.
Frequently asked
- Could another customer see my cached response?
- No. The edge cache is keyed by your authenticated session, so a cached response belongs to your workspace alone. One tenant never receives another tenant’s cached data from the edge.
- What does edge caching actually do for me?
- It serves repeat responses from a location near you instead of the origin every time. Pages that you load again come back faster, and the origin handles less work, which keeps Quri responsive under load.