Kovadocs

Dedicated IP Addresses

Lease a dedicated public IP for your deployment instead of using shared ingress.

Overview

By default, deployments are accessible through a shared ingress subdomain (*.deployments.kovanetwork.com). For workloads that need a static, dedicated IP address, you can lease one and attach it to your deployment. The IP is exclusively yours for as long as the lease is active.

Use Cases

Dedicated IPs are useful when you need:

  • Mail servers - Email deliverability requires consistent sender IPs and proper reverse DNS
  • Game servers - Players connect directly to an IP and port
  • VPN endpoints - Clients need a stable IP to connect to
  • Services requiring static IPs - Third-party API allowlists, firewall rules, DNS A records

Requesting an IP

1

Open Your Deployment

Navigate to the deployment detail page from the Deployments list.

2

Go to the IPs Tab

Click the IPs tab to view assigned addresses and request new ones.

3

Request a Dedicated IP

Click Request IP. The network will assign an available public IP from the provider's pool.

4

Wait for Assignment

IP assignment typically completes within a few seconds. The assigned address will appear in the IPs tab.

DNS Configuration

Once you have a dedicated IP, point your domain to it:

Type: A
Name: myapp.example.com
Value: 198.51.100.42
TTL: 300

DNS propagation can take up to 48 hours depending on TTL settings, though most resolvers pick up changes within minutes.

Costs

Dedicated IPs are billed separately from your compute resources:

ResourceBilling
Shared ingressIncluded with deployment
Dedicated IPAdditional per-block charge

The exact cost depends on provider pricing. You can see the IP charge in the billing breakdown on the deployment detail page.

Releasing an IP

When you no longer need a dedicated IP:

  1. Go to the IPs tab on your deployment
  2. Click Release next to the IP you want to remove
  3. Confirm the release

Once released, your deployment falls back to shared ingress. The IP returns to the provider's pool and may be reassigned to another user.

Dedicated IPs persist across deployment updates (e.g. changing your SDL or adding resources). However, they do not carry over to new deployments. If you close a deployment and create a new one, you'll need to request a new IP.

API Reference

Request a dedicated IP via the API:

curl -X POST \
  -H "Authorization: Bearer TOKEN" \
  https://app.kovanetwork.com/api/v1/deployments/:id/ip

Release an IP:

curl -X DELETE \
  -H "Authorization: Bearer TOKEN" \
  https://app.kovanetwork.com/api/v1/deployments/:id/ip/:ipId