Chapter 1
What is Blankitt Edge?
An introduction to eCDN observability and why it matters.
Jump to section
The problem
Salesforce B2C Commerce ships behind an eCDN powered by Cloudflare. The eCDN handles caching, DDoS protection, and global delivery -- but it provides no anomaly detection or alerting for traffic abuse.
When a scraper sends 5.7 million requests in 12 hours, or a competitor systematically crawls your product catalogue, or a botnet hammers your origin until performance degrades -- the eCDN doesn't flag any of it. You're blind until something breaks.
What Edge does
Blankitt Edge ingests the raw HTTP request logs from your eCDN (via Cloudflare Logpush), aggregates them into time-series metrics, and runs eleven detectors that surface anomalies the eCDN misses:
- Traffic spikes from a single network
- Client-closed connections (the scraper signature)
- Cache bypass patterns (origin abuse)
- User-agent rotation (bot evasion)
- Gradual escalation over weeks (the slow squeeze)
When a detector trips, Edge opens an alert, sends you an email, and shows the incident on your dashboard with all the context you need to take action.
How it's different
Edge is not a WAF and does not block traffic inline. It's an observability and detection layer that tells you what's happening and gives you the data to feed your existing WAF rules. Think of it as the alarm system -- it watches, it alerts, and it gives you evidence.