Networking · Firewall
Only the traffic you allow.
A cloud firewall in front of your VPS that drops every inbound connection you have not opened. Write rules by protocol, port and source network, and change them from the console — at no extra cost.
Closed unless you open it
Inbound traffic no rule allows is dropped before it reaches the server.
Rules by protocol and port
Open TCP and UDP ports or ranges, and ICMP for ping.
Limit who can connect
Restrict a rule to an IPv4 network, such as your office or VPN.
Nothing to install
Rules live in the console, not in iptables or ufw on the server.
Available locations
The data centers that offer the cloud firewall today.
What teams use the firewall for
The rules most servers need on day one.
Lock down SSH
Allow port 22 only from your own address or VPN range.
Public web servers
Open 80 and 443 to everyone and keep every other port shut.
Private databases
Accept database connections only from your application servers.
Admin panels
Keep dashboards and control panels off the public internet.
Game and VoIP servers
Open the UDP port ranges your service needs and nothing else.
Fewer exposed services
Shrink what scanners can see on a freshly deployed server.
How it works
From an open server to a filtered one in three steps.
Create a firewall
Pick the VPS it protects, in the data center the server runs in.
Add inbound rules
Open the protocols, ports and source networks the server needs.
Adjust any time
Change rules from the console as your services change.
Supported providers
3 providers in 3 countries offer the cloud firewall today, with more joining as the network grows.
-
DCT Serbia
-
Elastx
-
PidginHost
Frequently asked questions
What teams ask about the cloud firewall.
Close the ports you are not using.
Put a firewall in front of your VPS and open only what it serves.