Chapter 1
What is Blankitt Edge?
The security and operations console for Salesforce B2C Commerce storefronts. What it watches, what it explains, and what it never does without you.
Jump to section
The problem
Salesforce B2C Commerce ships behind an eCDN that handles caching, DDoS protection, and global delivery. What it does not give you is a working view of who is hitting your storefront and what they are doing: no anomaly detection, no alerting, no answer to "why did origin traffic double overnight".
When a scraper sends millions of requests in a night, a competitor walks your product catalogue, or a credential-stuffing operation quietly works your login page, nothing flags it. You find out when something breaks, or when your analytics stop making sense.
What Edge does
Blankitt Edge reads the request logs your eCDN already produces (via Logpush) and turns them into three things:
- Sight. Dashboards for every dimension that matters: networks (Offenders), URLs (Paths), individual clients (IPs), reconnaissance probes, bots and AI agents, and your TLS certificates. Over twenty detectors watch continuously and open alerts when something is wrong: traffic spikes, cache abuse, credential stuffing signatures, scanners, certificate problems, and more.
- Plain English. Every alert carries a short AI-written brief of what happened and why it matters, so the whole team can read an incident, not just the person who knows what a 499 ratio is. A weekly digest does the same for your traffic overall.
- Command. Alerts that map to a "stop this traffic" situation arrive with a ready-drafted eCDN rule. You can copy it and apply it yourself in Business Manager, or apply it from Edge in one click and roll it back just as fast. Every apply and rollback is recorded in a ledger.
What Edge never does
Edge sits out of band. It is not an inline WAF, it adds no latency to your storefront, and it never changes anything on your zone by itself. Nothing happens to your storefront that you didn't decide: every rule is applied by a person clicking a button, arrives challenge-first where possible, and can be removed in one click.
Where to start
- Setting Up Your First Logpush Source connects your storefront.
- Your First Batch explains what happens when data starts flowing.
- Detectors and Alerts covers what fires and when.