Origin offload: keep PHP, Node and storage off the public path

Origin offload is cache hit ratio plus Shield plus hiding the origin IP. How Cloud CDN reduces worker and bandwidth cost.

Get started Performance

Offload is the share of work the origin no longer does. It is why CDN spend can be cheaper than another app node: CSS, images and anonymous HTML never needed PHP or Node in the first place.

Bytes and requests

Measure origin bandwidth and request rate before and after. A campaign that used to melt PHP should mostly land on cache and Shield.

Hide the origin

If clients can still hit the origin IP, offload is optional. Restrict origin to Cloud CDN pull and validate TLS.

Workers versus disks

WordPress and Laravel offload CPU. VOD and installers offload disks and egress. Both are origin offload; the cache policy differs.

Serve-stale is offload during failure

When origin is down, eligible stale objects keep the site up. That is offload you only notice on a bad day.

Continue on Aptranet

Frequently Asked Questions

Will offload reduce my hosting bill?

It reduces origin egress and compute for reusable traffic. You still pay for the application and for Cloud CDN usage.

Can I offload APIs?

Public identical GETs yes. Authenticated APIs no. See the API caching guide.

Is offload the same as hit ratio?

Hit ratio is the edge metric. Offload is what origin CPUs and disks experience. Shield sits between them.