Public Gateway

A single & secure entrance to your infrastructure.

Easily allow connectivity for internal resources

Route traffic to the internet for your VMs without compromising their privacy and security

Define a single and reliable access point

Decrease outside exposure and reduce IP reservation costs. Your infrastructure will share a single external IP address.

Trust a fully managed Gateway

Setup, administration, failover & updates are covered for maximum reliability and minimal impact on your traffic.

Available zones:
Paris:PAR 1PAR 2
Amsterdam:AMS 1AMS 2
Warsaw:WAW 1WAW 2

Technical details

  • NATEnable access between your private network and the internet using dynamic and static rules.

  • BastionEnable and control SSH connections for your developers and system admin tasks

  • Gateway to Private NetworksUp to 8 Private Networks per Public Gateway.

  • EgressEgress included

Popular use cases

Use the Bastion to allow or deny access in SSH to the servers inside your Private Network, so as Lead Developer you are able to control who has access to the right VMC

Allow only the machines in your private network to have access to an external network and answer the request on that network

Optimize your IP usage by having a public gateway to mutualize the frontal IP for multiple VMs

Managed by Scaleway from €0.0199 ex. VAT/hour

Go to pricing

Get started with tutorials


Frequently asked questions

Public gateways sit at the border of private networks. They deal with traffic entering and exiting the network (NAT).

A public gateway can be attached to up to 8 private networks and up to 50 Public Gateways are supported per Organization.

The public gateway can be configured through the console or the API.

No, it doesn’t. A public IPv4 address (aka flexible IP) must be assigned to the public gateway when you create it, but you can detach it and delete it afterward if you don’t want to use the NAT feature.

No, you don’t. The Public Gateway will communicate automatically with all the instances in place within the Private Network thanks to the DHCP server

Yes, it can. With NAT enabled, the public gateway shares its public IPv4 address (aka. flexible IP) with the Instances attached to the private network, so that they can access the Internet.
Moreover, the public gateway supports static NAT (aka. port forwarding), so that ingress traffic from the public Internet can reach Instances on the private network. This works by mapping pre-defined ports of the public IP address of the gateway to specific ports and IP addresses on the private network.