Skip to content
Odinex Cloud
DELog inSign up

Networking

Private networks, NAT gateways and Elastic IPs

A private network connects your servers in a location over an internal network that is not reachable from the internet. Add a NAT gateway and servers without public addresses can still reach the internet for updates and APIs. Give such a server an Elastic IP when it needs a stable public IPv4 address for inbound traffic.

Get started Read the docs

At a glance

Address ranges
RFC 1918, /16 to /28
NAT gateways
One per network, €2.00/month
Elastic IPv4
€0.50/month
Scope
Servers in the same location
Setup in servers
DHCP on our Linux images

Key features

  • Your own address range

    Choose an IPv4 range inside 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16, from /16 to /28.

  • Configured automatically

    Servers from our Linux images pick up their private address by DHCP, also when attached later.

  • NAT gateway

    Outbound internet for servers without public addresses, through one public IPv4 address.

  • Elastic IPs

    A stable public IPv4 address mapped to a private-only server, movable to another server.

  • Private load balancing

    Attach a load balancer to the network and send traffic to servers that have no public address.

  • Fewer public addresses

    Keep databases and internal services off the internet entirely, and pay for fewer IPv4 addresses.

What it is used for

  • Database behind the app

    Run the database on the private network only; the application servers reach it on its private address.

  • A VPC-style layout

    Web servers without public addresses behind a load balancer, with outbound traffic through a NAT gateway.

  • Internal services

    Queues, caches and monitoring that talk to each other privately and never face the internet.

Try it

odx CLI
odx network create --name backend --ip-range 10.0.0.0/16 --location fra1
odx nat-gateway create --network backend --name backend-egress
odx server create --name app-1 --type s2 --image ubuntu-24.04 --location fra1 \
  --without-ipv4 --without-ipv6 --network backend

Documentation

Works well with

Private networks and NAT: questions and answers

Clear answers about location, infrastructure and billing.

Is a private network the same as a VPC?
It covers the same need: an isolated network for your servers with your own address range. Together with NAT gateways and Elastic IPs you can build a VPC-style layout with private-only servers.
Can servers without a public IP reach the internet?
Yes, if their network has a NAT gateway. Their outbound traffic leaves from the gateway public IPv4 address.
How do I make a private-only server reachable?
Assign an Elastic IP, or put a load balancer attached to the network in front of it.
Can I change the address range later?
No. The range is set when the network is created, so plan it with room to grow.

Build it in Frankfurt today

Create an account, top up from €5 and pay by the hour, never more than the monthly price.

Deploy your first server See all plans