Skip to main content
This feature is in Early Access and under active development. Behavior, supported fields, and limits may change before General Availability (GA). This guide provides forward-looking context for evaluation and feedback.Visit your dashboard to sign up for Early Access, or to send your feedback via the “Let us know” link.
Dedicated IPs let you configure static IP addresses that are exclusively assigned to your account for receiving traffic to your domains and agent connections. By default, ngrok uses a shared, multi-tenant pool of dynamic IP addresses that may change frequently and without notice. Dedicated IPs provide:
  • Static addresses - IP addresses that don’t change, making it easier to configure firewall rules and allowlists
  • Account exclusivity - IP addresses used only by your account, providing additional isolation
  • Custom port support - When used with domains, create endpoints on any inbound port (not restricted to ports 80 and 443)
  • Protocol support - Available for any ngrok-supported protocol, including HTTP/S, TCP, and TLS

Use cases

Dedicated IPs are valuable for:
  • Firewall allowlisting - Your customers can allowlist specific IPs in their firewalls to permit traffic from your services
  • Compliance requirements - Meet security policies that require traffic from known, static IP addresses
  • Network monitoring - Simplify logs and traffic analysis with consistent source IPs
  • Custom connect URLs - Secure agent connections with account-specific IPs (see Agent Dedicated IPs)

Dedicated IPs for domains

How it works

When you configure a domain with dedicated IPs, all matching endpoints for that domain receive traffic on your dedicated IP addresses instead of ngrok’s shared multi-tenant IPs. Dedicated IPs and Region Resolution (region pinning) share the same resolves_to field on the domain resource:
  • Region pinning: resolves_to: [{ "value": "<region-shortcode>" }]
  • Dedicated IPs: resolves_to: [{ "value": "<ip-address>" }]
You can combine both region pinning and dedicated IPs in the same configuration.

Configuration

Configure dedicated IPs through the Domains API using the resolves_to field.
Dedicated IPs are provisioned by ngrok after you sign up for Early Access. Contact ngrok Sales to obtain your dedicated IP addresses before configuring your domains.

Create a domain with dedicated IPs

The format for dedicated IPs in the resolves_to field is <ip-address>:<port>. The port is optional but can be specified if you want to receive traffic on a specific port.
curl --request POST \
  --url https://api.ngrok.com/reserved_domains \
  --header "Authorization: Bearer <token>" \
  --header "Content-Type: application/json" \
  --header "ngrok-version: 2" \
  --data '{
    "domain": "api.example.com",
    "description": "Production API with dedicated IPs",
    "certificate_management_policy": {
      "authority": "letsencrypt",
      "private_key_type": "ecdsa"
    },
    "resolves_to": [
      { "value": "192.0.2.1:1234" }
    ]
  }'

Combine dedicated IPs with region pinning

{
  "resolves_to": [
    { "value": "us-cal-1" },
    { "value": "192.0.2.1:1234" }
  ]
}

Update an existing domain

curl --request PATCH \
  --url https://api.ngrok.com/reserved_domains/{domain_id} \
  --header "Authorization: Bearer <token>" \
  --header "Content-Type: application/json" \
  --header "ngrok-version: 2" \
  --data '{
    "resolves_to": [
      { "value": "192.0.2.1:1234" }
    ]
  }'

Custom ports

When using dedicated IPs, you can create endpoints on any port, not just 80 and 443:
# Standard ports (available without dedicated IPs)
ngrok http 8080 --url https://api.example.com

# Custom ports (requires dedicated IPs)
ngrok http 8080 --url https://api.example.com:8443
ngrok tcp 22 --url tcp://api.example.com:2222

Agent Dedicated IPs

Dedicated IPs are also available for Agent Connect URLs, providing account-unique IP addresses for your agents to connect to ngrok’s service. This enhances security by:
  • Allowing you to allowlist only your dedicated connect IPs in your network
  • Preventing rogue agents from calling home to unexpected IPs
  • Providing white-labeling with a custom connect URL domain and dedicated IPs
See Agent Connect URL documentation for more information.

Pricing

Dedicated IPs are available as an add-on feature for Pay-as-you-go plan customers.
FeatureAvailabilityPricing
Dedicated Domain IPsEarly AccessContact Sales
Dedicated Agent Connect IPsAvailable$900/month per region (contact Sales)
See the Pricing page for details.

API reference

FAQs

How do I get dedicated IPs?

Dedicated IPs are in Early Access. Sign up for access through your ngrok dashboard.

Can I use dedicated IPs with TCP endpoints?

Yes, dedicated IPs work with all ngrok-supported protocols, including HTTP/S, TCP, and TLS.

What’s the difference between dedicated IPs and region pinning?

  • Region pinning restricts which ngrok Points of Presence handle your traffic for compliance and data residency requirements
  • Dedicated IPs provide static IP addresses exclusively for your account
You can use both features together.

Do dedicated IPs support IPv6?

Currently, dedicated IPs for domains are IPv4 only. IPv6 support may be added in the future.

How many dedicated IPs do I get?

The number of dedicated IPs available depends on your configuration and requirements. Contact ngrok Sales to discuss your needs.