Networking
VeloxaHost uses OVN (Open Virtual Network) for software-defined networking — giving you isolated, programmable private networks with full L2/L3 control.
Private Networks
Every project gets a private network per region. Instances within the same private network communicate over RFC-1918 addresses without touching the public internet. Traffic between instances on the same private network is fast, free, and does not count against bandwidth limits.
Default network
When you create your first instance, a default private network (default) is created automatically. Its CIDR is 10.0.0.0/24 — you can add up to 254 instances.
Create a custom network
# Console: Project → Networking → Create Network
# Or via API:
POST /v1/networks
{
"name": "backend-net",
"region": "vh-us-south-1",
"cidr": "10.10.0.0/24",
"gateway": "10.10.0.1"
}
Attach an Instance to a Network
An instance can be attached to multiple networks simultaneously — useful for separating frontend and backend traffic.
# Attach a running instance to an additional network
POST /v1/instances/{instance_id}/networks
{
"network_id": "net_backend"
}
# The new interface appears as eth1 inside the instance
Public IP Addresses
By default, instances receive a public IPv4 address via NAT. For a dedicated public IP that you can reassign between instances, use Floating IPs →
Bandwidth
| Traffic type | Billing |
|---|---|
| Private network (between instances) | Free, unlimited |
| Inbound public traffic | Free |
| Outbound public traffic | 5 TB/month included, then $0.01/GB |