Contextual web personalization and inspection engine on Fastly's edge stack

Fcuervo1 pts0 comments

Edge Personalization Engine β€” Fastly Compute Demo

πŸ‡ΊπŸ‡Έ

Welcome

Personalized for ashburn, united states<br>&middot; English &middot; UTC-400

Tech & Innovation

Content tailored to your region via Fastly Compute geolocation

Edge Computing Guide

How sub-millisecond latency transforms real-time APIs and WebSocket connections across North American POPs.

πŸš€

Compute@Edge Performance

Benchmarking WASM execution at Fastly POPs vs traditional CDN edge workers.

πŸ”Œ

API Gateway Patterns

Route, transform, and authorize API traffic at the edge before it touches your origin.

Edge Inspection Dashboard

Live

🌍 Geolocation Headers

country_codeUS

country_nameunited states

cityashburn

regionVA

continentNA

latitude39.0300

longitude-77.4900

postal_code20147

utc_offset-400

as_namecloudflare inc.

conn_speedbroadband

conn_typewired

πŸ“± Device Detection

hardware_typedesktop

brandUnknown

modelDesktop

is_mobilefalse

is_desktoptrue

is_tabletfalse

is_touchscreenfalse

is_botfalse

client_ip172.70.38.184

layout_modedesktop

Client Request<br>Fastly POP<br>Geo Lookup<br>Device Detect<br>HTML Compiled<br>Response<br>Entire request lifecycle executes at the edge β€” no origin server involved

This HTML was compiled natively at the Fastly edge using Compute services.<br>Geolocation and device data were resolved at the POP in sub-millisecond time β€”<br>zero origin latency , zero round-trips, zero cold starts.

edge fastly compute geolocation origin device

Related Articles