On this page
Key points
- Start with the covered serviceA licence, a protected connection and a game proxy include different resources.
- Separate recurring and variable costsCommit, options, traffic overage and engineering work need their own lines.
- Use the current quotePublic estimates describe new orders; existing agreements keep their own terms.
A price without a boundary is difficult to compare
“DDoS protection” can mean a feature on a hosted server, a managed application proxy, protected IP transit, a filtering appliance or software you operate on your own hardware. The monthly figures are not directly comparable until the protected resource and delivery path are clear. A low component price can be correct while leaving transport, equipment and operations outside the quote.
Begin with the service that users need to reach. A public Minecraft Java endpoint, a provider announcing several prefixes and an operator filtering on its own servers have different requirements. Decide which party supplies the network path, which runs the filter and which investigates a failure. The price comparison follows that division of responsibility.
Turn the desired outcome into a bill of materials
The same worksheet can compare a managed offer with an operated stack, provided ownership is explicit. Avoid combining the headline rate from one plan with the support or redundancy terms of another. Ask for missing costs rather than filling the gap with an unverified estimate.
| Cost layer | Examples to price | Common omission |
|---|---|---|
| Transport and delivery | Commit, access connection, tunnel or cross-connect and optional addressing. | Treating shared upstream capacity as bandwidth reserved for one customer. |
| Filtering platform | Software or appliance scope, supported interfaces and licensed capacity. | Assuming a licence includes the server, optics or network service. |
| Operations | Deployment, monitoring, escalation, updates and assistance. | Counting only the installation and no continuing maintenance. |
| Application delivery | Supported game or application, origin reachability and proxy requirements. | Assuming network mitigation is a universal application-layer proxy. |
Read the billing unit before multiplying anything
A commitment in Mbit/s, a monthly traffic allowance in TB, a per-port software charge and a per-instance game service are different billing units. Record the unit, period, tax treatment, included quantities and any setup or cancellation conditions. Note whether traffic accounting combines directions, takes a maximum or uses a different contractual method.
For a percentile model, first agree on sample interval, billing window, treatment of missing data and the direction calculation. A brief spike is not the same as the measured 95th percentile. Conversely, an apparently low average does not establish that a service stayed below commit. Use the billing method specified for the service rather than reconstructing a charge from an unrelated graph.
Separate commit selection from commit overage
A chosen commit is a commercial baseline. An overage calculation measures the chargeable excess according to the service’s billing rules. A recommended commit after a trial can also include headroom and a rounding policy. These three numbers should be shown separately, so that a recommendation does not appear to be the exact amount of observed traffic.
For example, a hypothetical 2.1 Gbit/s observation with 20% planning headroom produces 2.52 Gbit/s before rounding. A policy rounding that recommendation to whole Gbit/s would produce 3 Gbit/s. This explains a capacity choice; it does not by itself establish a monthly price or authorize a change to an existing contract.
Tiered pricing also needs an exact definition. A whole-commit volume rate applies the selected band’s rate to the entire commit; progressive pricing applies different rates to portions of it. Peeryx’s current public Transit calculator uses whole-commit volume bands. Compare the complete monthly result, especially around a band boundary, rather than multiplying a familiar rate from a different band.
Build a Peeryx estimate from the current catalogues
For a new protected Transit IP order, use the current commit calculator and select the actual delivery and optional features. The monthly IPv6 option is counted once per applicable tunnel configuration, even when several IPv6 settings are enabled. Physical delivery can require a separate setup quotation. Existing customer agreements are not rewritten by a public estimate.
Defense Fabric is a separate filtering-software offer. Its estimate depends on the licensed deployment and selected port capacity; compatible servers, interfaces, optics, hosting and external transport still need to be budgeted. An optional Peeryx transit line is priced separately from the software. A shared network-capacity statement is not a server throughput guarantee.
Flow Collector is a free telemetry and diversion tool in the published scope, but its VM, storage, telemetry transport, network service and operation can have costs. A Router VM has its own CPU, memory, port and traffic allowance model. FiveM and Minecraft Java delivery have application-specific terms. These products should not be added to a budget as if they were the same layer.
Compare two operating models without inventing a saving
Consider an operator that needs protected delivery and already owns a filtering server. In a managed-transit proposal, list the commit, delivery, address options and the agreed operating scope. In a software-led proposal, list the licence, usable server capacity, transport, redundancy and the people responsible for the service. Existing hardware is not free of power, replacement or maintenance costs.
Use the same normal traffic, packet workload, failure scenario and acceptance requirements for both proposals. If the software design needs another server to survive a node loss, include it. If physical delivery requires a cross-connect or a location change, include those charges too. The result may favor either approach; no general percentage saving can be justified without these inputs.
Avoid the comparisons that hide the real bill
Before approving the order, keep the estimate inputs, catalogue date, exclusions and acceptance conditions with the proposal. When traffic or deployment changes, recalculate the complete service. An explicit unknown is more useful than a precise-looking cost derived from an unverified assumption.
- Comparing an interface speed with a paid traffic commitment.
- Using peak attack bandwidth as if it were the billable percentile.
- Treating a free collector as free network capacity or inline filtering.
- Counting an IPv6 monthly option as a one-off activation fee.
- Leaving recurring port, hardware, colocation or support costs outside a software comparison.
- Assuming a trial, public calculator or sample scenario changes an existing customer contract.
Pricing questions
Why can two DDoS quotes differ so much?
They may cover different resources: a server feature, application delivery, protected transport, software or a complete operated service. Compare the boundaries and recurring costs first.
Is the 95th percentile the same as the commit?
No. The commit is selected commercially. A measured percentile, chargeable overage and post-trial recommendation can differ under the applicable rules.
Does Defense Fabric include the hardware and all network capacity?
No. Budget the licensed software separately from compatible hardware, hosting and transport. Any optional network service must appear as its own line.
