AS216394 · WireShield

Product Update

What is white-label DDoS protection? A guide for hosting providers and MSSPs

White-label DDoS protection lets you offer a protection service to your customers under your own brand. Learn about reseller, multi-tenant and self-hosted options and what to check when choosing.

White-label protection: one brand manages multiple customer panels

White-label DDoS protection is a model that lets you offer a protection service developed by another company to your own customers under your own brand. For hosting companies, internet service providers, cloud providers, agencies and managed security service (MSSP) companies, it creates a new revenue line and stronger customer loyalty without building the infrastructure from scratch. This guide explains the difference between white-label and reseller models, who needs them and what to look for when choosing.

What is white-label DDoS protection?

Three related concepts are often confused:

ModelWhat it meansWhose brand?
ResellerYou sell the provider's service to your customers, often through the provider's account systemUsually the provider's
White-labelYou offer the service under your own brand; the customer does not see the provider, or not prominentlyYours
Multi-tenant managementYou manage many customers from one panel, with quotas and permissionsVaries by model

A real need is usually a mix of the three: each customer has their own panel, you manage all customers from one place and you deliver the service under your own brand.

Who is it for?

  • Hosting and data center companies: To sell additional security to the customers they host.
  • Internet service providers: To protect customer networks.
  • MSSPs and IT service companies: As part of their managed security offering.
  • Agencies and software houses: To protect their clients' websites.

What to look for in a white-label protection provider

  1. Branding. Can your logo and texts appear on pages customers see, such as the challenge page?
  2. Multi-tenant structure. Are each customer's data and visibility separate? Are there quotas, permissions and usage tracking?
  3. Billing and usage data. Can you see usage per customer and base your own pricing on it?
  4. API and integration. Can you open accounts, manage rules and receive notifications from your own systems?
  5. Infrastructure control. Do you use the service in the cloud, or install it on your own servers and run the nodes yourself?
  6. Feature parity. Are the features the same in the cloud and on your own infrastructure?
  7. Support model. Is it clear who you work with, and how, when technical issues come up?

White-label and reseller options with WireShield

WireShield has two different structures for two different layers:

Web Protection (HTTP/L7): Web Protection is used in two ways, and the features are exactly the same in both.

  • Cloud: Your customer gets protection right away by pointing DNS records to WireShield. You can open reseller accounts and offer the protection to your own customers; WireShield runs the infrastructure.
  • On-premise / self-hosted: You install it on your own servers and use and sell it as white-label under your own brand. You manage your own nodes and create reseller accounts for your customers.

The challenge page customers see can also be customised: you can show your own logo and texts.

Network protection (L3/L4): For providers that protect many customers, the MSSP & Partners platform offers a multi-tenant operator portal:

  • Customers (tenants), quotas, protection groups and permissions are managed in one place.
  • Each customer gets their own Customer Portal, where they see their own attacks and reports.
  • Usage and billing are tracked in the same place.
  • Monthly summaries and SLA reports can be scheduled; notifications arrive by e-mail, webhook and, for operators, Telegram, syslog and SNMP trap.
  • The REST-based Customer API and MSSP API let you integrate with your own systems.

The two structures complement each other: you can offer your network with Remote or Inline protection and your customers' web applications with Web Protection in the same portfolio. To choose between the models see inline or remote.

Steps for launching a white-label service

  1. Define the target customer. Website owners, network owners, or both?
  2. Choose the model. Cloud reseller gives a fast start; self-hosted gives more control and branding.
  3. Set your price structure. The number of domains, traffic volume and policy needs shape the price.
  4. Run a technical assessment. Share domains, traffic volume and the number of customers you expect.
  5. Start a pilot. Begin with a few customers and settle the processes.
  6. Write down the support process. Who handles what, and in what time?

Frequently asked questions

Is white-label the same as reselling?

No. In reselling you mostly sell the service under the provider's brand. With white-label you offer it under your own brand. In practice the two are often used together.

Will my customers see WireShield?

In Web Protection you can show your own logo and texts on the challenge page, and with the self-hosted option you can use it under your own brand. We clarify details in the technical discussion.

Are features missing in the self-hosted option?

No. Web Protection features are exactly the same in the cloud and on-premise options.

How many customers can I manage?

The operator portal is designed to manage many customers with quotas and permissions. Share the scale you expect in the technical discussion and we will plan together.

How is pricing decided?

It depends on the domains and applications to protect, traffic volume and policy needs. After a technical assessment we prepare an offer that fits.

Next step

If you want to offer the service under your own brand, describe your customer profile and the scale you expect. You can look at the cloud and on-premise options on the Web Protection page or talk to the technical team.

All posts

Let’s review the right protection model for your network together.

Contact our team to talk through your technical needs.