Networking

Create private networks to connect your instances securely.

Private networks allow instances to communicate internally while remaining isolated.

With an agent (MCP)

Connect the redu MCP, then just ask your agent. Over the MCP, private networks are list-only: list_private_networks lets the agent list and inspect your existing networks. On a deploy, check_deploy_prerequisites auto-selects a network for you, so the agent does not need to pick one manually. Creating a new private network is done in the console (below) for now.

1. Create a private network

Go to:

Menu → Network → Private Networks

Then:

1. Click Create Network
2. Optionally enter a CIDR
3. Submit the form

Optional CIDR

You can define a CIDR for the network.

Examples:

10.1.5.0/24
10.1.5.0

• If no CIDR is provided, one is assigned automatically
• If /24 is omitted, it is applied automatically
• The platform normalizes CIDR values internally

For most cases, you can leave this field empty.

2. View networks

After creation, networks appear in the list.

You can see:

• Network name
• Network ID

3. Attach a network to an instance

When creating an instance:

1. Select a private network
2. Launch the instance

Instances in the same network can communicate with each other.

4. Control access with security groups

Security groups define firewall rules.

Examples:

• SSH → port 22
• HTTP → port 80
• HTTPS → port 443

See Security Groups Guide

Troubleshooting

Invalid CIDR

Ensure the CIDR is within the allowed range.

Examples:

10.1.5.0/24
10.1.5.0

Instances cannot communicate

Check that:

• Both instances are in the same network
• Security groups allow the required traffic

Network not available

If a network does not appear during instance creation:

• Refresh the page
• Ensure the network was created successfully

Related

• Compute
• Security Groups
• Networking Overview