Deno Deploy Cloaking
TypeScript edge filtering without a backend — and the intelligence layer you'll still need.
Cloaking in a V8 isolate
Deno Deploy runs TypeScript directly on V8 isolates at the edge — no containers, no cold starts, native Web APIs. For developers, it's one of the fastest ways to stand up a request-inspecting proxy: exactly what a cloaker is at its core.
A minimal DIY cloaker
Deno.serve(async (req) => {
const ip = req.headers.get('x-forwarded-for');
const ua = req.headers.get('user-agent') ?? '';
const geo = (req.headers.get('x-geo') ?? '').split(',')[0];
if (await isBot(ip, ua, geo))
return Response.redirect(SAFE_URL, 302);
return Response.redirect(MONEY_URL, 302);
});
Twenty lines and you have a link cloaker. What you don't have is isBot() — the function that actually matters. Filling it with static lists means it's outdated within weeks. Filling it with real-time lookups means building (and paying for) an intelligence pipeline that ad platforms force you to update forever.
Calling Cloaker.net from Deno
The pragmatic pattern: keep your Deno Deploy script as the thin execution layer, and let Cloaker.net be isBot() — a real-time classification API backed by:
- ✔Continuously refreshed ad-platform bot databases (Google, Meta, TikTok, native networks).
- ✔AI behavioral & fingerprint classification for headless browsers.
- ✔Geo/ISP/rule engine and full visit logs you can pipe into your own tooling.
Deno developers love composable primitives — and that's exactly how the modern stack looks: your code for routing, Cloaker.net for knowing who's who. Skip the years of database maintenance and start from the layer that's already been battle-tested on billions of visits: cloaker.net.
TypeScript speed, advertiser intelligence
Edge filtering with Cloaker.net's API — build in hours, not years.
Start with Cloaker.net →
