Regions
Reference Easel edge delivery and Function compute regions.
Easel distinguishes edge delivery locations from Function compute regions.
Edge delivery
Requests enter Easel through its delivery network. Static assets and cacheable responses may be served from an edge location without invoking application compute.
Do not interpret the number of edge locations as the number of places where Functions run.
Function compute
Dynamic routes run in Function compute regions supported by the platform.
| Region ID | Location | Available for Functions | Selection |
|---|---|---|---|
iad | US East (Northern Virginia, USA) | Yes | Platform default; currently the only Function region |
Additional Function regions are not available yet. Region placement is fixed by the platform today. Do not rely on route-level or project-level region configuration examples until the product exposes them.
The delivery layer may attach the Function region on the request your application receives:
See Function regions and Request and response headers.
Data locality
Place latency-sensitive databases and APIs near the Function compute region. Edge delivery cannot remove the network trip between a Function and a distant data service.
Observability
Request and invocation records can expose edge and compute context separately where available. See Function observability.