Public Gateway

A single & secure entrance to your infrastructure.

Define a single access point

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

Automate network configuration

Let the Public Gateway automate network configuration for you and help you configure your private network

Reliable gateway uptime

We handle the setup, administration & updates. Failing devices are automatically replaced with minimum impact to your traffic.

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

Technical details

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

  • DHCPEnable automatic IP address assignment for resources in your private network (dynamic and static).

  • DNSEnable local name resolution within your private network.

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

  • EgressEgress included

Popular use cases

Your website/application needs to filter entering and exiting connections. Add a Public Gateway to ensure security and to not expose unnecessary resources.

Restrict access to your backends with security rules and let only the web server be in contact with the external network. Combine the added value of a Public Gateway with a Private Network.

Monitoring your network for both internal or external connections allows you to better control the performance of your application/website, and in turn improve customer satisfaction.

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 provide services to automate the allocation of private IP addresses (DHCP) and 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. Instances in a Private Network for which autoconfiguration (DHCP) is enabled will automatically benefit from the services provided by the public gateway. Autoconfiguration is automatically enabled in recent Instances. If your instance is too old, you may have to update it or enable autoconfiguration by hand.

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.