How it works
How your natbox server connects
A NAT VPS shares one IPv4 address with other servers. Here is exactly what reaches yours.
Shared IPv4
Your server has no public IPv4 address of its own. It shares 5.189.155.145 / 5.189.142.51 / 92.242.190.191 with other servers and uses it for outgoing traffic too. Inbound IPv4 only reaches you on your own ports.
Your forwarded ports
Each plan gets a fixed block of ports (3 to 30). Both TCP and UDP are forwarded to the same port number on your server. The first port is SSH. Ports 80 and 443 are shared: link your domain and we route TCP HTTP by hostname and HTTPS by SNI, untouched. HTTP/3 (UDP 443) only works over IPv6.
Routed IPv6
A whole /80 is routed to your server: every address, every port, TCP and UDP, no forwarding. We do not filter it, so set up a firewall on your server (nftables, ufw or firewalld) for anything you do not want public. Visitors need IPv6 to use it.
What you get
- Root on a Linux container (Incus LXC): Debian, Ubuntu, Alpine or AlmaLinux
- A block of IPv4 ports, TCP and UDP, and a routed /80 of IPv6
- Your own domains on ports 80 and 443, with your own certificates
- Hard RAM and disk limits, a fair share of CPU (Box CPU gets one core reserved for it), 100 Mbit/s each way
- A monthly traffic allowance; above it you are slowed to 10 Mbit/s, never cut off
- Client area: power, reinstall, root password, domains, usage graphs, upgrades
- Optional Off-site backups ($0.50/month): 7 daily and 4 weekly copies you can open or restore from the client area
What you do not get
- A dedicated public IPv4 address, or any IPv4 port outside your block
- Outgoing mail on ports 25, 465 and 587 (use a mail API or a relay on port 2525)
- Docker or other nested containers, Windows, custom kernels or kernel modules
- Help with the software you install, or high availability
Where it runs
In the EU, in a Contabo data centre. Measured from our server on 30 October 2026 (30 pings each): about 5 ms on average, 3 ms at best, to Cloudflare DNS (1.1.1.1) and Google DNS (8.8.8.8). These are nearby network points, so this shows the server's connection, not your latency, which depends on where you are and on your ISP.
Network
100 Mbit/s per server each way on a shared uplink. IPv4 through our router, IPv6 routed straight to you. Status at status.natbox.io.
Storage
Local SSD on the host server (ZFS), not network storage. Add Off-site backups to any paid plan for nightly copies you can restore yourself. Without them, our nightly copies are for disaster recovery only, so keep your own backups.
Help and support
Open a ticket or email support@natbox.io. We reply within 24 hours. Report abuse on the abuse form.
Ready when you are.
Spin up your first server for $1, or try one free for a month.