# IPv4

**Page:** foundation/networking/ipv4

[Download Raw Markdown](./foundation/networking/ipv4.md)

---

# IPv4


**Coming Soon** - Dedicated IPv4 address assignment for containers is currently in development.


---

## 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

- **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

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

### 1. Network Configuration (Exit IP Routing)

**Change the exit IP address** for outbound traffic from containers:

- **[Network Configuration →](./network/)** - Route traffic through SOCKS5/HTTP proxies or VPN providers
- Container appears to originate from proxy/VPN IP
- Works for outbound connections only

### 2. Hoody Proxy (Inbound Service Access)

**Access container services** via URLs (HTTP/HTTPS):

- **[Hoody Proxy →](/foundation/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

**Direct SSH/SFTP access** to containers:

- **[SSH →](./ssh/)** - SSH Proxy routes by public key
- No dedicated IP needed
- Works for terminal and file transfer access

---

## 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

**Get notified when IPv4 support launches:**

- Join the [Hoody Community](https://discord.social.hoody.com) for announcements
- Follow [@hoodyrun](https://x.social.hoody.com) on Twitter

---

## Current Networking Capabilities

**Available now:**

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

---

## What's Next

**Explore current networking features:**

- **[Network Configuration →](./network/)** - Exit IP routing through proxies/VPNs
- **[Firewall →](./firewall/)** - Host-level packet filtering
- **[SSH →](./ssh/)** - SSH and SFTP client access

**Alternative access patterns:**
- **[Hoody Proxy →](/foundation/proxy/)** - HTTPS service URLs
- **[Container Management →](/foundation/containers/create-edit-delete/)** - Creating and managing containers

---

> **IPv4 assignment is coming soon.**  
> **Use Network Configuration to control exit IPs today.**  
> **Use Hoody Proxy for inbound HTTPS service access.**

**Subscribe to updates to know when IPv4 launches.**