Publisher security / In Development
IVTB
An edge traffic-intelligence product with a dashboard, policy controls and explainable decisions.

Public website · captured 13 November 2026. Figures shown within the interface belong to the source website.
01 / PROJECT NOTES
The publisher problem
Publishers need to understand suspicious requests and choose a proportionate response. A single opaque block decision is difficult to operate: it can hide the reason for a result and make troubleshooting legitimate visits harder. IVTB frames that work as traffic intelligence and policy control.
02 / PROJECT NOTES
My engineering contribution
I work across the Cloudflare Worker API, React dashboard and site integration. Tenant configuration, request decisions and operational coordination have distinct responsibilities. This case study covers the SaaS platform; the standalone WordPress plugin has its own case study.
03 / PROJECT NOTES
The request boundary
The documented flow begins with a verified publisher site and versioned client integration. A Worker checks the site and policy, reuses an applicable decision where possible and consults IP intelligence when required. Durable Objects coordinate parts of the runtime; D1 stores application configuration and operational records.
04 / PROJECT NOTES
Engineering trade-offs
Traffic protection must account for provider failure as well as a suspicious signal. The implementation distinguishes cached decisions, provider paths and explicit customer policy. Those are separate responsibilities: obtaining a signal should not silently redefine the action a publisher selected.
05 / PROJECT NOTES
From request decisions to operations
The dashboard and billing integration bring policy management and account operations into the product. Ongoing hardening focuses on browser behaviour, provider handling, billing and operational checks.
06 / PROJECT NOTES
Product scope
The public website introduces the product and its approach to traffic intelligence. The dashboard examples shown there are illustrative. This case study focuses on the platform architecture and engineering work.
Explore the boundaries.
A simplified view of the application. Select a component to explore its role.
Simplified architecture study · NOT A LIVE SYSTEM
The integration identifies the publisher site and its origin.
A Worker evaluates context, applicable saved decisions and selected policy.
Provider intelligence, Durable Objects and D1 support distinct runtime responsibilities.
Project summary & sources.
- An edge API, publisher dashboard and site integration.
- Policy configuration separated from intelligence-provider signals.
- A documented architecture supporting ongoing product hardening.
THE PUBLIC EXPERIENCE / TWO VIEWPORTS
One product.
Different contexts.
Desktop and mobile views of the public website.
Open desktop capture ↗Open mobile capture ↗