Serious DDoS protection for exposed infrastructure, critical services and network operators
Peeryx protects exposed services with a readable model: volumetric mitigation, protected IP transit, clean traffic delivery and integration that matches your real architecture.
Core offers
Each offer fits a concrete need: protecting live prefixes, keeping your own filtering logic or adding a specialised layer for selected public gaming services.
Protected IP Transit
From €1/MbpsBGP, clean traffic, readable handoff and network integration for exposed prefixes or IPs.
Anti-DDoS Router VM
From €99/mo*Keep your own XDP, eBPF or routing logic behind a first volumetric protection layer.
Anti-DDoS Dedicated Server
From €149/mo*Build your own filtering stack behind upstream protection.
Gaming Reverse Proxy
From €29/mo*For selected public gaming services that need a specialised layer.
What a technical customer needs to understand before buying
The subject is not only displayed capacity. You also need to know where the attack is stopped, how clean traffic comes back and what remains under your control.
Where saturation really happens
The first breaking point is not always your server. It can be the transit, the port, the stateful firewall or the delivery model itself.
How clean traffic gets back
The handoff must be explicit: BGP, tunnel, cross-connect or an intermediate VM depending on your architecture and latency constraints.
What logic stays on your side
Peeryx can remain the first volumetric layer while you keep your own XDP, proxy, eBPF or application logic behind it.
Which offer matches the actual need
Protected transit, router VM, protected dedicated server and specialised proxy do not solve the same problem. These differences need to be explicit for the customer.
Which model fits which use case
Peeryx covers several deployment patterns without forcing every customer into the same product.
Protected IP transit
Best when you already work with prefixes, BGP and network handoff and want a readable service for an existing production environment.
Upstream layer in front of your stack
Best when you want to keep your own filtering or routing logic behind a first volumetric mitigation layer.
Specialised gaming layer
Relevant when a public game service needs filters and handling that go beyond generic network mitigation.
Dedicated filtering server
Relevant when you want to keep or build an advanced customer-operated filtering stack.
Public exposure
Prefixes, IPs or public services already exposed.
Peeryx mitigation edge
Volumetric mitigation, network decisions and attack reduction.
BGP / GRE / VXLAN / cross-connect / router VM
Delivery depends on your level of control and your existing topology.
Customer production
Servers, edge, proxy or in-house filtering behind already-cleaned traffic.
Blog
Peeryx FAQ
Does Peeryx always replace my own filtering logic?
No. Peeryx can stay as the upstream volumetric layer while the customer keeps XDP, eBPF, proxy or application logic behind it.
Do I need to migrate my whole infrastructure?
No. Depending on the case, clean traffic can be returned via BGP, GRE, VXLAN, cross-connect or a router VM.
Why focus so much on handoff?
Because a credible Anti-DDoS service is not only about absorbing an attack. It must also re-inject traffic that remains usable in production.
Are the displayed prices final?
They are entry-level references. Final pricing depends on delivery model, commits, ports and the required hardware.
Describe your exposure, your network and your clean-traffic return model
Peeryx will come back with a credible design: protected transit, tunnel, router VM, dedicated server or another model that actually matches your architecture.