01
Custom domains
Attach domains, route traffic, and keep SSL certificates active without manual web server drama.
Edge DeliveryGlobal routingCache-aware
Serve closer.Route smarter.Wake origin less.
Forgeon Edge Delivery puts your apps, domains, assets, SSL, and routes behind a fast edge layer that decides what should be cached, proxied, protected, or delivered instantly.
Edge atlas
domain → nearest edge → cache → origin
JKT
18ms
SIN
11ms
TYO
32ms
SYD
44ms
FRA
96ms
IAD
181ms
visitor
browser request
origin
runtime / storage
domain forgeon.app resolved to nearest edgecache hit /_next/static/chunk-a91f.jsssl certificate renewed for app.example.comorigin request coalesced for /pricingasset served from singapore edgeroute matched app-web productionpreview deployment mapped to deploy-v42domain forgeon.app resolved to nearest edgecache hit /_next/static/chunk-a91f.jsssl certificate renewed for app.example.comorigin request coalesced for /pricingasset served from singapore edgeroute matched app-web productionpreview deployment mapped to deploy-v42domain forgeon.app resolved to nearest edgecache hit /_next/static/chunk-a91f.jsssl certificate renewed for app.example.comorigin request coalesced for /pricingasset served from singapore edgeroute matched app-web productionpreview deployment mapped to deploy-v42
Request journey
Every request takes the shortest useful path.
The edge layer decides whether a request should be served from cache, routed to object storage, forwarded to runtime, or protected before it hits your origin.
cache firstorigin shielddomain awaressl ready
01edge entry
Request arrives
User opens your app from browser, domain, preview URL, or custom route.
02geo + health
Nearest edge selected
Forgeon resolves traffic to the closest healthy edge location.
03hit / miss
Cache checked
Static assets, images, and immutable files can be served without waking origin.
04protected
Origin shielded
Only uncached or dynamic requests pass through to runtime or object storage.
05delivered
Response delivered
Content is streamed back fast with headers, SSL, routing, and observability attached.
Cache behavior
Cache the obvious. Forward the important.
Edge Delivery should not treat every route the same. Static assets, image paths, dynamic APIs, and app shells each deserve their own delivery behavior.
RouteBehaviorTTLMode
/_next/static/*
Cache immutable assets
1 year
hit/images/*
Cache transformed images
30 days
hit/api/*
Bypass cache for dynamic calls
none
pass/
Serve app shell with smart revalidation
adaptive
edgeEdge event stream
delivery decisions in real time
domain forgeon.app resolved to nearest edge
01cache hit /_next/static/chunk-a91f.js
02ssl certificate renewed for app.example.com
03origin request coalesced for /pricing
04asset served from singapore edge
05route matched app-web production
06preview deployment mapped to deploy-v42
07Origin protection
Your origin should not carry every tiny request.
Let the edge serve repeatable assets, collapse duplicate requests, and only call your runtime or storage when the response truly needs origin work.
Lower backend pressure
Cache hits keep traffic away from runtime containers.
Faster global delivery
Users receive content from a nearby edge path.
Delivery surfaces
Not just CDN. The front door for your product.
Edge Delivery connects the parts users touch first: custom domains, SSL, static files, app previews, runtime traffic, and asset routes.
02
Static assets
Serve JS, CSS, images, uploads, and build artifacts closer to users with cache-aware delivery.
03
Runtime routes
Forward dynamic traffic to the right runtime service while keeping the edge layer in control.
Edge Delivery
Move the web closer to your users.
Route domains, serve assets, protect origin, cache smartly, and deliver your app through an edge layer that knows when to respond and when to forward.
cache hit → edge response → origin sleeps