Deliver without the distance
Bring static assets closer to your audience. A distributed delivery layer reduces the work between a request and a response.
WEBSITES · APPS · STATIC ASSETSYour content. Less distance.
A simpler way to deliver websites, assets and applications from the edge to your users.
GET /assets/hello-world.js200 OK · served from edge cacheKeep your origin focused on what it does best. Let the edge handle the journey to your users.
Bring static assets closer to your audience. A distributed delivery layer reduces the work between a request and a response.
WEBSITES · APPS · STATIC ASSETSChoose what stays at the edge and for how long. Use explicit cache rules and targeted invalidation to keep content fresh.
CACHE RULES · TTL · PURGESee the difference between origin traffic and cached delivery. Turn request patterns into better decisions for your application.
REQUESTS · CACHE HITS · BANDWIDTHPoint your delivery configuration to the server that hosts your content.
Set a lifetime for your assets and keep dynamic routes uncached.
Keep your own hostname at the front of the experience.
service: "my-website" hostname: "cdn.example.com" origin: url: "https://origin.example.com" cache: path: "/assets/*" ttl: 3600 respect_origin: true delivery: compression: "auto" https_only: true
Content is cached near your audience. A cache hit serves an asset from the edge; a cache miss retrieves it from the origin. Cache rules determine when that asset is refreshed.
Explore a cleaner way to put your content at the edge.
Discover the workflow