Documentation

Point your origin at CDNFlux and traffic is served from the nearest edge location. Most setups take under ten minutes.

1. Add your origin

Send us the hostname your content is currently served from and we provision a pull zone for it. CDNFlux fetches assets on demand and caches them at the edge.

zone:    assets.example.com
origin:  origin.example.com
scheme:  https

2. Update DNS

Point a CNAME record at the zone endpoint we assign. Propagation is usually complete within the TTL of your existing record.

assets.example.com.  CNAME  z4821.edge.cdnflux.xyz.

3. Cache behaviour

By default we honour Cache-Control from your origin. Responses without an explicit directive are cached for one hour. Override per path in the zone settings:

• /static/* — 30 days, immutable
• /api/* — bypass cache
• / — 5 minutes, revalidate

4. Purging

Individual paths or the whole zone can be purged through the purge API. Purges propagate to all points of presence within a few seconds.

TLS

Certificates are issued and renewed automatically for every zone. TLS 1.2 and 1.3 are enabled; older protocol versions are refused. HTTP requests are redirected to HTTPS by default.

Limits

Default zone limits are 10 zones, 200 GB of monthly transfer and 50 requests per second per zone. Higher limits are available on request.