Fastly Compute@Edge Cloaking
VCL, WASM, and high-performance traffic routing at the edge — plus the easier way.
Fastly: the performance purist's edge
Fastly built its reputation on speed — VCL-based config at the CDN layer and, more recently, Compute@Edge, which lets you run compiled WASM at every PoP. For cloaking, that combination is attractive: sub-millisecond decisions, full request inspection, and custom routing logic without origin round-trips.
Two DIY routes
📜 VCL
Classic approach: match client IP ranges, User-Agents, and geo in VCL and synthetic or restart to a safe page. Fast, but static — every list update is a config redeploy.
🦀 Compute@Edge (WASM)
Rust/Go/JS compiled to WASM: richer logic, external lookups, better fingerprint handling. But you still own the intelligence — the data that decides human vs bot.
The gap Fastly can't close
Fastly gives you the world's fastest execution surface. It cannot give you:
- ✖Live databases of Google / Meta / TikTok review-bot ranges, updated as they rotate.
- ✖AI models trained on billions of classified visits.
- ✖Behavioral fingerprinting for headless-browser detection.
- ✖Per-visit audit logs for compliance-minded teams.
Fastly + Cloaker.net
The clean division of labor: Fastly (or your origin of choice) serves pages at maximum speed; Cloaker.net sits in front as the classification layer, sending only verified human traffic down the pipe. Ad traffic goes through a Cloaker.net link or domain integration — bots and reviewers never touch your Fastly config, your logs stay clean, and your safe page serves exactly who it should.
Whether you're a DevOps-heavy team that lives in VCL or a media buyer who's never heard of WASM, the outcome is the same: fast pages, clean traffic, accounts that survive. That's the Cloaker.net promise.
Fast pages. Clean traffic.
High-performance cloaking for serious infrastructure — Cloaker.net.
Try Cloaker.net →
