Private Networks

  • Private LAN
    Layer 2 ethernet network
  • High bandwidth
    Up to 4 Gbps between instances
  • Multi-Private Networks
    Up to 8 Private Networks per instance
  • Scalability
    255 instances per private network
  • Scaleway's ecosystem
    Compatible with instances and Load Balancers
  • QinQ
    Carry your own VLANs over your private networks
Isolate your resources
Enhanced security
Control your Network
Available Regions
  • fr-par-1
  • fr-par-2
  • nl-ams-1
  • pl-waw-1
  • Production ready
  • IPv4 & IPv6 Support
  • Management via console and API
Free of charge
Create your own Private Networks

Compatible with

  • Dev Instances
  • GP Instances
  • GPU Instances
  • Enterprise Instances
  • Load Balancers

Take control of your network with Private Networks

With Private Networks, configure your own Layer-2 network with IPv4 or IPv6 adresses. Enhance security of your Cloud Oriented architecture by isolating them from the Internet.

All the possibilities of a layer 2 network

Isolate your resources with Private Networks

Private Networks are a LAN-like layer 2 ethernet network. A new network interface with a unique MAC address is configured on each instance in a private network. You can use this interface to communicate in a secure and isolated network, using private IP addresses of your choice.

Hotplug Instances to your Private Networks

With Private Networks, you can easily create or delete instances, then add or remove them from your private network, without needing to restart your instances. You can hot-plug up to 255 instances per Private Networks without downtime.

Your IP addresses in an internal LAN

Each instance of a private network gets a new network interface with a MAC address on which you can configure any private IP addresses you want.

Simple configuration via API

In addition to our simple and intuitive console, all the features of Private Networks can be configured through the Scaleway API for simple and seamless integration into your automation processes.

Discover our top Use Cases for Private Networks

Best for distributed Web Apps

The Private Networks feature can help you to build a distributed web application on General Purpose and Development Virtual Instances using a private network to communicate securely between them.

Isolate logs, backups and Databases

The Private Networks feature can help you to isolate some ressources from the Internet. You can for example host a MongoDB on a GP instance, and make it only accessible from your frontend instances.

Allow your custom security enhancement

Private Networks offer you an extra-step in making you less vulnerable to all kind of attacks, such as DDoS attacks on specifics parts of your infrastructure.

Deploy your Private Networks

You have a project? Contact us:

Contact us

Sharpen your knowledge on Private Networks with our blog articles

Discover our compute resources available with Private Networks

Frequently Asked Questions

What is Private Networks?

Private Networks is a managed cloud service allowing you to create layer 2 ethernet-switched domains. These domains can also be called a virtual LAN (VLAN). They are virtual but completely private local networks that securely connect your instances together without necessarily exposing them publicly.

Can I plug multiple Private Networks on the Same Instances?

Yes, you can configure multiple private networks on the same instance. A virtual network interface is created for each private network to which the instance is attached. You can bring up each of them as indicated in our product documentation. You can configure:

  • Up to 8 private networks per instance
  • Up to 255 private networks per organization
  • Up to 255 instances per private network

Do I have to restart Instances after adding Private Networks?

No, Instances are hot plugged to Private Networks. This means private network interfaces will appear on your instances without needing to reboot.

Does Private Networks support IPv6?

Yes, you can configure IPv6 within Private Networks. To use it, the netmask should always be /64 and we recommend using a fc00::/7 unique local address (ULA) range. ULA IPv6 address generators are widely available for generating a personalized range.

Do Instances in a Private Network require a public IPv4 address?

No, they do not require a public IPv4 address.

Do non-IP protocols work over Private Networks?

Technically, any ethernet payload should work over Private Networks. However, only IPv4 and IPv6 are officially supported. If you have real use cases for other protocols, let us know.

Deploy your Private Networks

You have a project? Contact us:

Contact us