Create a NAT Gateway from the Deploy page in my.cubepath.com. It attaches to a private network and gives every server on it shared outbound internet through one public IP — there's nothing to SSH into.
NoteYour account must be verified before you can deploy.
How it works
The gateway gets a public IPv4 and IPv6 plus a private IP inside your network, and a default route (0.0.0.0/0) pointing at that private IP is added to the network automatically.
From then on, servers on the network send outbound packets to the gateway, which rewrites the source address to its own public IP (source NAT) and forwards them out. Replies come back the same way. Many private servers share one public address for egress, and nothing from the internet can reach them.
When to use it
- Private servers need outbound access — package updates, external APIs, git repositories, webhooks — but shouldn't be reachable from the internet.
- You need one stable egress IP to whitelist on a third-party API, a partner's firewall or a SaaS provider. Every server behind the gateway appears as the same address, so you register one IP instead of one per server.
- You don't want to pay for, and expose, a public IP on every VPS.
The standard shape is a private database or application tier, locked-down CI machines, or any fleet you want off the public internet without cutting off its outbound access.
Deploy
- 1Select a private networkPick the private network the gateway will serve. Each network can have only one NAT Gateway, and the region is set by the network you choose.
- 2Choose a planPlans differ by vCPU, RAM, storage and bandwidth (Mbps). Available plans depend on the network's location; pricing is per hour, shown with a monthly estimate.
- 3Name your gatewaySet a name (letters, numbers and hyphens) and an optional label describing its purpose.
- 4Review and deployConfirm that one public IPv4 and one IPv6 will be assigned and billed, then click Deploy NAT Gateway.
The gateway starts in deploying and flips to active once provisioning finishes. Servers on the network then reach the internet automatically — no configuration needed on them.
NoteIf deployment is rejected, the message says why: insufficient balance, a suspended organization, or no public IPs available in that location right now.
What it doesn't do
ImportantA NAT Gateway only allows outbound traffic. Unsolicited inbound connections from the internet are blocked — only replies to outbound requests come back. To expose a service, use a Load Balancer or attach a Floating IP directly to the server.
- It isn't a load balancer. It gives servers a shared way out; it doesn't distribute traffic coming in.
- It isn't port forwarding. There's no way to publish a private server's port through it.
- One per network, one location. Each private network gets one gateway, serving that network in that location. Different networks need their own.
Billing
Billing is hourly or monthly, following your project's billing type, and accrues from creation until you delete the gateway. The public IPv4 and IPv6 assigned to it are billed too.
A NAT Gateway also counts toward your combined VPS + Load Balancer + NAT Gateway resource limits.