The only scaled security vendor built channel-native from day one -- competing on features with Cloudflare instead of owning the embedded infrastructure category.
Web security is consolidating around a handful of mega-vendors -- Cloudflare, Akamai, Imperva -- all built around direct enterprise relationships. Their go-to-market assumes a buyer who actively searches for security solutions, evaluates vendors, and procures through a security budget. This model works for enterprises. It does not work for the millions of SMB websites that need protection but will never have a security team, a security budget, or a reason to evaluate a WAF vendor.
Hosting providers manage those millions of websites. They are the natural distribution layer for security -- the same way payment processors became the natural distribution layer for fraud detection. The hosting provider already has the customer relationship, the billing infrastructure, and the traffic visibility. Security bundled into the hosting stack is a revenue uplift for the provider and a zero-friction adoption path for the end customer.
Blackwall, an Estonian company backed by a EUR45M Series B, built its entire product and go-to-market around this channel insight. Their GateKeeper platform is designed to be embedded inside a hosting provider's infrastructure and resold -- not retrofitted as a partnership program. Sign one hosting provider, protect tens of thousands of downstream sites. Unit economics that enterprise-direct models structurally cannot match. The product has already reached 2.3 million websites across 30+ countries. The positioning has not caught up with the structural advantage.
The web security market has five relevant players, but only one of them approaches the market through the channel that matters for this analysis.
Cloudflare dominates direct-to-customer web security with a massive free tier, global edge network, and brand recognition among developers. Their "Cloudflare for Platforms" initiative signals awareness of the channel opportunity -- but it moves slowly against established hosting partnerships because Cloudflare's architecture is cloud-distributed by design. On-premises deployment is structurally difficult for them. Every hosting provider that deploys Cloudflare's tools is also directing traffic through Cloudflare's network -- a data sovereignty issue for providers in regulated verticals.
Imperva and Kasada are enterprise-direct security vendors. Strong products, strong brands, zero channel motion for hosting providers. They sell to enterprise security teams, not infrastructure operators. The hosting provider who wants to bundle Imperva-grade protection into their stack has no path to do so.
HAProxy operates in an adjacent lane as open-source infrastructure tooling. Engineers use it; nobody is buying it as a white-label security product for downstream customers.
| Dimension | Blackwall | Cloudflare | Imperva | Kasada | HAProxy |
|---|---|---|---|---|---|
| GTM Model | Channel-native (hosting) | Direct + platform | Direct enterprise | Direct enterprise | Open-source infra |
| On-Prem Deployment | Yes -- built for it | No (cloud-distributed) | Limited | No | Yes |
| Target Buyer | Hosting provider CTO | Enterprise security | Enterprise security | Enterprise security | Engineers |
| White-Label Ready | Core to the model | Partial | No | No | No |
| Partner Revenue Uplift | 30-40% per customer | N/A | N/A | N/A | N/A |
Blackwall occupies a position none of these companies have built for. The entire product architecture assumes channel distribution: on-premises deployment for data sovereignty, white-label branding for the hosting provider's customer-facing experience, and infrastructure-grade integration at the traffic layer that makes switching costs structural, not contractual. The competitive risk from Cloudflare for Platforms is real but moves slowly -- adapting a cloud-distributed architecture for on-premises channel deployment is not a product update. It is a different deployment model.
A- Believability. DigitalOcean, Vultr, AWS, cPanel, Plesk, Deloitte. 2.3 million websites protected. Revenue impact testimonials citing 30-40% uplift per customer. These proof points speak directly to hosting provider buying criteria. The evidence infrastructure is strong and specific to the actual buyer.
B+ Clarity. The hero framing -- "Designed for Service & Hosting Providers, Engineered for Engineers" -- correctly filters the audience. A hosting provider CTO landing on this page immediately knows the product is built for their use case. The sub-headline, however, is jargon-heavy, and "gold standard performance" is the kind of unverifiable superlative that technical buyers dismiss on sight.
B Differentiation. This is where the channel identity crisis shows. Blackwall's homepage includes feature comparison tables and detection rate claims -- the standard enterprise security pitch. None of which explains why a hosting provider would choose Blackwall over building their own WAF or integrating Cloudflare. The structural advantage -- channel-native architecture that mega-vendors cannot replicate without cannibalizing their direct sales -- is not leading the story. It should be the story.
The core tension: Blackwall does not sell to enterprises. It sells through hosting providers. Millions of websites get Blackwall protection before the site owner ever thinks about bot traffic. That is not a feature difference. It is a structural GTM advantage that is almost impossible to replicate from an enterprise sales model. And yet the messaging competes with Cloudflare on features -- feature comparisons, detection rate claims -- instead of owning the narrative that makes the channel model defensible: "The security layer trusted by the infrastructure that powers millions of businesses."
"Trusted by the infrastructure that powers millions of businesses" -- with DigitalOcean, Vultr, cPanel, and Plesk logos front and center above the fold. This is not a conventional logo wall for social proof. It is the positioning itself. Blackwall's credibility is borrowed from the infrastructure partners who chose to embed it. When a hosting provider sees that DigitalOcean trusts Blackwall at the traffic layer, the vendor evaluation is effectively over. The partner ecosystem is not supporting evidence for the product. The partner ecosystem is the product's authority. Treating it as a footnote on the homepage, below feature comparisons and detection rate statistics, inverts the persuasion hierarchy that actually drives deals. Every other security vendor can list enterprise customer logos. Only Blackwall can list infrastructure partners who embedded the product into their stack.
The difference between "bot protection for hosting providers" and "embedded security infrastructure" is the difference between a point solution in a commoditizing market and a category-defining infrastructure layer. Blackwall is not a vendor that hosting providers buy. It is infrastructure that hosting providers build into their stack -- comparable to how payments infrastructure became table-stakes for any commerce platform. The on-premises deployment capability opens regulated verticals and data-sovereign markets that cloud-only vendors architecturally cannot serve. This is not a feature gap that Cloudflare can close with a product update. It requires a fundamentally different deployment model. The narrative needs to own this category before a mega-vendor defines it for them.
A third opportunity involves building hosting provider success tooling -- SMB-facing dashboards, provider analytics, co-branded customer security notifications -- that deepen integration and raise switching costs at every partner touchpoint. A fourth concerns the BotGuard/GateKeeper brand architecture, where both products appear as parallel direct-sales channels, creating channel conflict that dilutes the B2B2C motion. Both require deeper understanding of Blackwall's current partner operations and product roadmap.
ProductBeacon monitors product leadership signals across European tech companies. Blackwall appeared on our radar through a combination of a EUR45M Series B announcement and product leadership hiring activity that suggested the company was entering a phase where the go-to-market strategy needed to evolve beyond its initial channel positioning. This analysis was created without any contact with the company, using only publicly available information (website, LinkedIn, press releases, job postings, and industry databases).
Analyst: Yohay Etsion, Managing Director, ProductBeacon. 17 years leading product organizations at NICE and Cognyte.
We build these analyses for companies whose structural advantage is more powerful than their positioning reflects. If the way you sell is harder to copy than what you sell, we should talk.
Request a Diagnostic