Skip to content
Hoody Documentation
Hoody.com
Download Page (.md)

IPv4

Section titled “IPv4”

What’s Coming

Section titled “What’s Coming”

Dedicated IPv4 addresses will allow containers to have their own public IP addresses, independent of the host server’s IP.

Planned Features

Section titled “Planned Features”
  • Static IPv4 Assignment - Each container gets a dedicated public IP
  • IP Persistence - IP address remains the same across container restarts
  • Direct Routing - Services accessible directly via IP (no proxy routing)
  • Multiple IPs per Container - Support for multiple IPv4 addresses per container
  • IP Pooling - Rent blocks of IPs for your projects

Current Alternatives

Section titled “Current Alternatives”

While dedicated IPv4 is in development, you can configure container networking using:

1. Network Configuration (Exit IP Routing)

Section titled “1. Network Configuration (Exit IP Routing)”

Change the exit IP address for outbound traffic from containers:

  • Network Configuration → - Route traffic through SOCKS5/HTTP/HTTPS proxies (many VPN providers expose SOCKS5 endpoints)
  • Container appears to originate from proxy/VPN IP
  • Works for outbound connections only

2. Hoody Proxy (Inbound Service Access)

Section titled “2. Hoody Proxy (Inbound Service Access)”

Access container services via URLs (HTTP/HTTPS):

  • Hoody Proxy → - Makes services accessible via unique URLs
  • HTTPS with automatic SSL certificates
  • No IP address needed for service access
  • Works for inbound connections (accessing container services)

3. SSH Access

Section titled “3. SSH Access”

Direct SSH/SFTP access to containers:

  • SSH → - SSH Proxy routes by public key
  • No dedicated IP needed
  • Works for terminal and file transfer access

Use Cases (When Available)

Section titled “Use Cases (When Available)”

Dedicated IPv4 addresses will enable:

Legacy Application Support:

  • Applications that require static IPs
  • IP-based licensing systems
  • IP whitelisting requirements

Direct Service Hosting:

  • No reverse proxy in front
  • Direct IP:port access
  • Lower latency (no proxy layer)

Multi-IP Scenarios:

  • Different IPs for different services
  • IP-based traffic segregation
  • Compliance requirements

Email/SMTP Hosting:

  • Dedicated sending IP for reputation
  • Reverse DNS configuration
  • IP warmup for deliverability

Stay Updated

Section titled “Stay Updated”

Get notified when IPv4 support launches:

Current Networking Capabilities

Section titled “Current Networking Capabilities”

Available now:

  1. Network Configuration - Control outbound traffic routing (exit IP)
  2. Firewall - Packet-level ingress/egress filtering
  3. SSH - Secure Shell and SFTP access
  4. Hoody Proxy - HTTPS URLs for service access

What’s Next

Section titled “What’s Next”

Explore current networking features:

Alternative access patterns:

Dedicated IPv4 assignment is not available yet. Until it ships, use Network Configuration to control which IP your container’s outbound traffic exits from, and Hoody Proxy for inbound HTTPS access to your services.