We disclose this up front rather than burying it: today our VPS use a shared public IPv4 with NAT, and each VPS gets its own dedicated forwarded ports. For most workloads this is all you need.
Discord/Telegram bots, game servers (we forward the game port for you), trading bots, web scrapers, CI runners, dev boxes, app backends behind a reverse proxy, VPN for personal use — all work great on NAT.
Running your own mail server, needing your own :80/:443 with a bare IP, certain peer-to-peer setups, or strict reverse-DNS requirements. A dedicated IPv4 is on the roadmap — email us about your use case and we'll tell you honestly whether NAT covers it.
Straight answers.
Yes — run it behind your dedicated forwarded port, or ask us to forward 80/443 to your VPS. For a simpler path, our web hosting includes domains and SSL out of the box.
Email [email protected] with your service and the port you need. We'll map it and reply with the external port.
No — NAT doesn't cap throughput. Your VPS still gets the full 10 Gbps link.