PRICINGBLOG
Language
Internal VPC Networking

Internal Networking No Exposing.

Services in one project connect over an internal network. No ports open to the internet, and internal traffic is not billed.

Internal VPC NetworkingDemo
redis://6379postgres://5432
api-gatewaymain ← helipodapp/api
running
api.helipod.app
2 vCPU 2GB 1GB
SSL
redisvalkey:7 · TCP
running
0.5 vCPU 512MB
SSL
postgrespostgres:16 · TCP
running
1 vCPU 1GB 10GB
SSL
InitializingInternal VPC

Why it matters

What you get

Automatic Isolation

Services within a project can access each other. Services from other projects cannot, automatic isolation.

Over Internal DNS

Services reach each other by service name on internal DNS, not through public internet addresses.

No Bandwidth Costs

Internal traffic is not charged bandwidth costs. Save money on high-traffic applications.

Internal DNS

Use service names as hostnames. No need to hardcode IP addresses.

Steps

How it works

  1. 01

    Create Services

    Create services within the same project, backend, database, cache, etc.

  2. 02

    Use Internal DNS

    Connect services using service names as hostnames (e.g., mongodb:27017).

  3. 03

    No Need to Expose

    Database and cache services don't need exposed ports to the internet. More secure and efficient.

Blog

Read also

Guides and tutorials related to this feature.

FAQ

Frequently asked questions

How do I connect between services?
Use internal DNS with the format service-name:port. For example, for MongoDB: mongodb:27017. No IP address or public URL needed.
Are there connection limits?
Traffic between services in the same project is not billed separately. You pay for the services' resources (CPU, RAM, storage).
Can I access from outside?
Internal services cannot be accessed from outside unless you set up a custom domain. This is a security feature, not a bug.

Ready to try?

Sign in with Google or GitHub, connect a repository, and pay from a Rupiah balance. No credit card needed.
WhatsApp