No. You keep your current host and server. Traffic is routed through Sterile first and delivered to your server over a GRE tunnel.
One installer, on the server you already run
Download the installer from the dashboard and run it as root. It checks the server, brings up the GRE tunnel and registers a service so the tunnel survives a reboot. This is what it prints.
What you need
- Root access on a Linux server
- A kernel that can load the ip_gre module
- Your SSH port added to a profile in the dashboard first, or the install can cut your session
Your host's protection and Sterile
| Typical host protection | Sterile | |
|---|---|---|
| When an attack is too large | Your IP is null-routed | The attack is filtered |
| Your server's address | Public | Hidden behind a Sterile IP |
| When filtering starts | After detection | Always on |
Watch it from the dashboard
Clean traffic, blocked traffic and every attack on your server, as it happens.

Built for a single server
- Works with your current host
- You keep your provider, your server and your setup. The only requirement is that the server can run a GRE tunnel.
- VPS or dedicated
- The same protection covers a small VPS and a large dedicated server. You size it by traffic, not by hardware.
- Always-on filtering
- Mitigation runs continuously, so there is no detection delay to sit through when an attack starts.
- Hidden origin
- Your server's real address stays out of public view. Only clean traffic from our edge reaches it.
- Filtering you can tune
- Start from a premade profile and adjust the rules for your ports and traffic.
- Live analytics
- See clean traffic, blocked traffic and attack history for your server in the dashboard.
Questions about protecting a server
What people ask before putting a VPS or dedicated server behind DDoS protection.
Yes, as long as the server can run a GRE tunnel. Some container-based VPS plans do not allow that, so check with your host if you are unsure.
Host protection is often built to protect the host's network. When an attack is larger than it handles, the usual response is to null-route your IP, which takes you offline. Sterile filters the attack instead, so your server keeps answering.
A little, because traffic takes one extra hop through our edge. How much depends on the distance between your users, our edge and your server. Read the latency guide
You choose the reserved speed, clean traffic and protected IPs you need, and pay monthly for that. View pricing
Keep your server online
Add protection to the server you already run, and be filtered before the next attack arrives.
