A connected world. A closer edge.

Great content.
Delivered everywhere.

Bring your origin closer to your audience. Content delivery, intelligent caching and secure traffic infrastructure, built around the edge.

Explore the platform Discover our network
✓ HTTPS DELIVERY✓ ORIGIN CONTROL✓ EDGE CACHING
TELEMETRY / GLOBAL EDGEDELIVERY ARCHITECTURE
NORTH AMERICALATIN AMERICAEUROPEEAST ASIASOUTHEAST ASIAOCEANIA
REGIONAL FOCUS

Amsterdam · Europe

ORIGIN → EDGE → AUDIENCE
One origin. A global reach.Content delivery without borders
Web & applicationsKeep experiences close to users
Media & large filesDeliver content at the edge
APIs & dynamic trafficStay in control of your origin
Security by designProtect the path to your content
The delivery platform

Built for the way
the internet moves.

A practical delivery layer between your infrastructure and your audience. Start with content delivery, then shape the edge around your application.

01 / CONTENT DELIVERY

Less distance. More speed.

Cache static assets near your users and reduce repeated requests to your origin. Define how your content is stored, refreshed and delivered.

Explore edge delivery
02 / TRAFFIC SECURITY

A stronger first line.

Keep encrypted delivery, origin protection and request policies in the same architecture. Build a consistent boundary for public traffic.

Understand the architecture
03 / DELIVERY CONTROL

Your rules. At the edge.

Separate cacheable assets from dynamic requests. Plan cache lifetimes, preserve query parameters and keep application behaviour predictable.

Plan an integration
A global perspective

Think globally.
Deliver locally.

Regional delivery brings content closer to its destination. Explore the role of the European edge and the wider delivery architecture.

Design your delivery path
EUROPEAN EDGE

Amsterdam

A European delivery perspective, connecting your origin architecture with audiences across the region.

Delivery modelOrigin → Regional edge
Content policyCache-aware routing
TransportHTTPS
Integration, considered

Your origin.
A better delivery path.

01

Define your origin

Choose the HTTPS endpoint that serves your application or static assets.

02

Shape your cache policy

Keep static files cacheable and send private or dynamic content to the origin.

03

Validate before switching traffic

Check certificates, headers and content freshness before changing public DNS.

A local configuration preview. Your origin is not contacted.

DELIVERY-CONFIG.JSON
Use the preview to plan your origin and cache policy.
Good questions
Before you connect.
What is an origin?
An origin is the server that holds the authoritative version of your content. An edge layer can cache eligible responses and forward other requests to that server.
Should every response be cached?
No. Account pages, authenticated requests and private responses should follow a suitable bypass policy. Cache static public assets with explicit freshness rules.
How does HTTPS fit into delivery?
The browser connects to the delivery endpoint over HTTPS. The connection from that endpoint to the origin should also use a certificate and verification policy suited to the deployment.
When should I change DNS?
After validating delivery with a test hostname. Check TLS, content, redirects and cache behaviour first, then plan the DNS change and a rollback.


Bring your content closer.
Build a delivery architecture that moves with your audience.
Start with your origin