A protected dedicated server to build your own filtering stack behind volumetric mitigation
This offer is for customers who want a dedicated server with upstream volumetric protection and full freedom to run their own filtering, proxy or DPDK/XDP stack behind it.
What this offer really enables
The goal is not to sell another server. It is to place a credible volumetric layer in front of advanced filtering that you still want to operate yourself.
Build your own filtering stack
You can keep or develop your own XDP, DPDK, proxy or specialised classification logic without taking the full raw volumetric hit directly on the node.
Separate volumetric mitigation from fine-grained logic
The upstream layer reduces volume and pressure, while your server stays focused on more specific decisions.
Keep hardware and software freedom
The design is aimed at technical customers who want to decide how filtering happens after the first line of defence.
Create a credible defence chain
This is often more realistic than promising magical filtering on a single unprotected point.
When to choose a protected dedicated server
This model mainly fits teams that already know what they want to operate themselves.
Yes if you want your own filtering engine
XDP, DPDK, specialised proxy, custom analysis or a production-grade filtering lab.
Yes if you want to isolate fine-grained filtering
The server becomes the place where your advanced rules live, behind volumetric mitigation.
Less relevant if you only need protected transit
In that case, protected transit will often be simpler and more cost-efficient.
Relevant for in-house pre-filtering
Use Peeryx for the volumetric layer and your own logic for the rest.
Public traffic
The exposed service receives legitimate traffic and attacks.
Peeryx volumetric layer
The first layer absorbs and reduces the attack before it strikes your node directly.
Protected dedicated server
Your machine stays free for XDP, DPDK, proxy or specialised filtering.
Services or backend
Processed traffic continues to your applications or downstream servers.
Blog
Peeryx FAQ
Does this replace protected transit?
Not necessarily. It primarily addresses the need for a dedicated node where your own filtering logic runs behind mitigation.
Can I deploy my own code and filters on it?
Yes. That is the point of the offer.
Does the displayed price include exact hardware?
It is an indicative starting point. Hardware, ports and capacity still need project validation.
Tell us what kind of stack you want to run yourself
Peeryx will guide you toward the right server, handoff model and upstream protection layer.