How EdgeWrap Works
EdgeWrap is a distributed, low-latency API gateway and proxy that runs at the network edge. By placing itself between your clients and your primary API servers, EdgeWrap transparently injects security, performance optimization, and observability.
High-Level Architecture
EdgeWrap is built on a multi-region serverless proxy architecture. When a client makes an API request to your custom domain or EdgeWrap subdomain, the request is routed to the nearest EdgeWrap edge node.
The 15-Step Request Pipeline
Every single request processed by EdgeWrap passes through a strictly ordered pipeline at the edge. The pipeline handles tasks sequentially and can exit early (for example, if a request is blocked by WAF or served directly from the cache).
For a visual timeline of this process, see the Request Pipeline page.
Edge Security First
DDoS shield, WAF analysis, and threat intelligence act at the outer edge, protecting your origin server from load and scraping.
Instant Caching
Cache hits bypass your origin completely, resolving in single-digit milliseconds and dramatically reducing database loads.
Intelligent Routing
Requests are automatically load-balanced across your healthy origins, with circuit breakers preventing cascades if an origin fails.
Real-Time Analytics
Every request event, block, and latency measurement is logged instantly to provide you with comprehensive dashboard analytics.
Why Edge Routing Matters
By terminating SSL/TLS close to the client and using persistent connection pools to your backend origins, EdgeWrap cuts the time-to-first-byte (TTFB) significantly. Even on cache misses, WAN optimization ensures that requests traverse the backbone network faster than typical public DNS routing.