CDN & Caching

Your documentation needs to load fast. Poliage delivers assets through a high-performance global network.

Architecture

Edge Caching

Requests hit our edge network first. If the image is cached, it's served in milliseconds.

Smart Routing

If the cache is stale (you just approved a new version), we route through our high-speed Redis layer to find the new image path immediately.

Instant Invalidation

When you click "Approve" in the dashboard, we instantly purge the old version from the edge. No waiting for TTLs to expire.

Global Coverage

Assets are served from edge locations worldwide:

Performance

Cache Behavior

Default Cache

Assets are cached at the edge for 24 hours by default.

On Approval

When you approve a new version:

1. CDN cache is purged globally (< 1 second)
2. Next request fetches the new image
3. New image is cached at all edges

Cache Headers

Assets are served with appropriate headers:

Cache-Control: public, max-age=86400
ETag: "abc123..."

Using with Your Own CDN

If you're using BYOS with S3 or R2, you can put your own CDN (Cloudflare, CloudFront) in front:

{
  "storage": {
    "type": "s3",
    "bucket": "my-assets",
    "publicDomain": "https://cdn.mycompany.com"
  }
}