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:
- Click Create Network
- Optionally enter a CIDR
- 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
/24is 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, the network appears in the list.
| Column | Description |
|---|---|
| Name | Human-readable network name assigned by the platform |
| CIDR | Private address range used by the network |
| Status | Active when the network is ready to use |
| Network ID | Technical identifier used by the API and MCP |
| Actions | Operations available for the network |
Wait for Active before selecting the network during an instance launch. You can copy the Network ID directly from the list.
Default networks cannot be deleted. For another network, open Actions → Delete Network and confirm only after verifying that no resources still depend on it.
3. Attach a network to an instance
When creating an instance:
- Select a private network
- Launch the instance
The selector is under Advanced options → Select Network. The first available network is selected automatically, so check the value instead of assuming it is the network you intended.
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
Troubleshooting
Invalid CIDR
Ensure the CIDR is within the allowed range.
Examples:
10.1.5.0/24
10.1.5.0Instances 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