Shared IPv4 & port mapping
Every Sidecar container gets its own public IPv6 address outright. IPv4 is scarcer, so on lower tiers your container shares one public IPv4 address with other peers and receives a dedicated, contiguous range of ports on that address. Traffic to any port in your range is forwarded straight into your container — no proxy, all protocols (TCP and UDP).
What you get
Your dashboard shows an endpoint like:
203.0.113.7:20000–20063
That means the public address 203.0.113.7 plus the 64-port
block 20000 through 20063 is yours. A packet
arriving at 203.0.113.7:20000 is DNAT'd to the same port
inside your container; the same applies to every port up to the end of
the range. The range is computed as:
port_end = port_start + port_count − 1
How to use it
- Bind your service to one of the ports in your assigned range.
- Advertise the shared IPv4 plus that port to your users.
- For services that need a well-known port (e.g. 443), use IPv6 directly, or move up to a tier with a dedicated IPv4 where the whole address — and every port — is yours.
Dedicated IPv4 vs. shared IPv4
On a dedicated IPv4 the entire address belongs to your container and the port-range section never appears — every port is already yours. Shared IPv4 trades a slice of the port space for a much lower price while still giving you raw, un-proxied L3/L4 reachability.
Need a dedicated address or a custom hostname? See pricing or set up a custom domain in your dashboard.