To sell DDoS protection as an add-on, include a base tier with every server, sell larger tiers per server per month, write down what happens when an attack exceeds the tier, and bill the add-on on the same cycle as the server. On hourly servers, charge the tier by the hour at its monthly price divided by 720.
This guide is for hosting providers packaging protection they buy from an upstream or build on their own network. It covers the commercial side: tiers, terms, activation and billing. The filtering itself happens in your network and your provider's, never in the billing system. WHMCS and Blesta details were read in their own documentation on 16 November 2026, at the time of writing (November 2026).
How do you sell DDoS protection as tiers?
Customers compare protection by one number: how big an attack it absorbs. Build the product around that number and keep everything else simple.
- Price per server, not per IP. One tier covering every IP on the server is easier to explain and to bill than a price per address. It also stops customers moving a target to an unprotected IP.
- Include a base tier. Every server ships with something, so nobody is unprotected on day one and the paid tiers read as upgrades rather than as insurance you forgot to buy.
- Name tiers by capacity and layer. Gbps or Tbps of Layer 3 and Layer 4 volume, and say plainly whether Layer 7 (HTTP) filtering is in a tier. Below that tier, HTTP floods are the customer's job, with rate limits, caching and connection limits in their own stack.
- Keep the ladder short. Five or six steps are enough. Each step should be a clear jump that matches a real cost step with your upstream.
- Offer it on every product that can use it. VPS, dedicated and game servers usually qualify. Leave it off products where your network cannot honour it, and say so on the product page.
What should a DDoS protection tier table look like?
The table below is an example. It mirrors a common market shape, an included base tier and paid steps up to a top tier that adds Layer 7, with illustrative prices. Set your own prices from what each step costs you upstream, plus your margin.
| Tier (example) | Layers | Example price per server per month | Hourly equivalent (monthly ÷ 720) |
| 100 Gbps | L3/L4 | Included | €0 |
| 500 Gbps | L3/L4 | €150 | €0.2083 |
| 1 Tbps | L3/L4 | €500 | €0.6944 |
| 2 Tbps | L3/L4 | €1,000 | €1.3889 |
| 5 Tbps | L3/L4 | €2,500 | €3.4722 |
| 10 Tbps + Layer 7 | L3/L4/L7 | €4,500 | €6.2500 |
Three details make a table like this work. Prices exclude VAT and say so. The hourly column uses four decimal places, because a rate such as €0.2083 rounds badly to cents. And the top tier is the only one that mentions Layer 7, so nobody reads HTTP filtering into a cheaper step.
What happens when an attack is bigger than the tier?
This is the part customers read after the first big attack, so write it into your terms before you sell the first tier. A policy that works in practice has three parts:
- A grace allowance. For example, the first few attacks in a calendar month that exceed the customer's tier are still mitigated at no extra charge. Count them per server and reset the count each month.
- A clear consequence after that. From the next over-cap attack in the same month, the targeted IP address is null routed until the attack ends or the server moves to a larger tier. Remote triggered blackholing, often signalled with the BLACKHOLE community from RFC 7999, drops traffic to that one address upstream so the rest of your network stays up.
- Scope. Only the targeted IP is affected, not the whole server and not the customer's other servers. Say this explicitly, because it is the difference between one site going dark and a whole business going dark.
Leave out promises you cannot measure. Do not publish detection or mitigation times, a fixed null route duration or a guaranteed uptime figure unless your upstream contract gives you the same commitment in writing.
Why should paid tiers be activated by your network team?
Raising a tier usually means a change at your upstream or on your own edge: a new profile for the customer's prefixes or a different mitigation policy. That is a network change, and it should be made and checked by a person, not flipped by the billing system the moment an invoice is paid.
So treat the add-on order as a work order. The billing system records the new tier and starts charging for it, and a ticket or task goes to the network team, who apply it and confirm. Tell customers in the order form and in your documentation to raise a tier a day before an expected event, such as a game launch or a ticket sale, and to open a ticket so the team can confirm it is active.
How do you bill DDoS tiers on hourly servers?
On an hourly server the tier is just another hourly line. Divide the monthly tier price by 720 (a 30-day month) and add it to the server's hourly rate for as long as the tier is active. A change applies from the next hour with no upfront invoice, and the customer pays only for the hours at each tier.
A worked example using the table above: a customer on an hourly VPS raises the tier to 500 Gbps for a three-day tournament. That is 72 hours at €0.2083, or €15.00, on top of the server's own hours. They drop back afterwards and stop paying for it.
On monthly servers, a mid-cycle change is a prorated difference: credit for the unused days of the old tier, a charge for the same days at the new one, and the renewal date stays where it was. Our post on WHMCS hourly billing covers how prepaid credit and hourly charging work in general.
How do you set up DDoS tiers in WHMCS and Blesta?
WHMCS calls this feature Configurable Options, under Configuration, System Settings, Configurable Options. You create a group, choose the products it applies to and add an option with sub-options for each tier. Dropdown or Radio types suit a tier list. Each sub-option takes a price for every billing cycle the product has enabled, and a retired tier can be marked Hidden so existing customers keep it. WHMCS's documentation separates these from product addons: configurable options change the price of the product itself, addons do not.
WHMCS prorates upgrades by the day: a credit for the unused part of the current cycle and a charge for the rest at the new price, with the due date unchanged. The configurable options documentation does not cover hourly pricing, so hosts that bill by the hour add a module such as ModulesGarden's Advanced Billing For WHMCS, listed at $35.95 a month at the time of writing.
Blesta also calls them configurable options, managed under Packages, Options. Options sit in option groups that you assign to packages. Blesta states that paid service changes are processed and prorated automatically. Its package terms go down to a day, so there is no hourly tier price.
In both, the option group is attached product by product. If you sell twenty VPS and dedicated plans, you attach the group to twenty products and remember to attach it to the twenty-first.
How does FluxBilling handle a DDoS add-on?
In FluxBilling a DDoS tier is a product option, defined once with its price. Because a tier is a charge plus a task for your team, you set it as billing only, with no resource grant. Billing-only options can be offered on whole product categories, so one option covers every product in your VPS and dedicated categories, including products you add later. A product that should not carry it can hide the option on its own pricing tab.
Turn on configurable choices to list the tiers, each with its own monthly price, and mark the included tier as the default. Quarterly and annual prices fill in from the monthly price. On hourly services the charge is always the monthly price divided by 720, taken from the customer's credit each hour along with the server.
Customers pick a tier at checkout or add one later from the Service Options card on their service page, and change its size there. On a monthly service the prorated difference is invoiced and the change applies once that document is paid. On an hourly service there is no proration: the new rate applies from the next hourly charge. The upgrades and downgrades guide shows the arithmetic, and the hourly billing guide covers credit, warnings and suspension.
FluxBilling bills the tier. It is not in the traffic path and does not filter or null route attacks, as its DDoS protection page explains, so mitigation stays with your upstream and your own edge. Plans on the pricing page start at €4.95 a month for 10 clients and reach €25 for unlimited clients on Business, which is also the only tier that can be self-hosted, for a €50 one-time fee, by registered businesses.
DDoS add-on FAQ
Should DDoS protection be priced per IP or per server?
Per server is simpler for most hosts. One price covers every IP on the server, customers cannot dodge the tier by moving a target to another address, and the billing system needs one option per service.
Should Layer 7 filtering be in every tier?
Only if your network actually filters HTTP at every tier. If it does not, keep Layer 7 in the top tier only and tell customers below it to handle HTTP floods with rate limits and caching.
Can customers raise a tier just before an attack?
They can order it, but a person has to activate it. Ask customers to raise the tier a day ahead of a known event and to open a ticket so your network team can confirm it is active.
How do I choose the prices?
Start from what each capacity step costs you upstream per server, add your margin, and check the top tier still pays for the support time a large attack takes. Recalculate when your upstream contract changes.
Next step
If your current billing system makes you attach the same option to every plan by hand, or cannot bill a tier by the hour, compare it on our WHMCS alternative page.
WHMCS, Blesta and ModulesGarden are trademarks of their respective owners. FluxBilling is not affiliated with or endorsed by any of them.