Skip to main content

Internal Routing

Hostim.dev supports internal networking between apps and services within the same project. This allows your containers to talk to each other directly, without exposing anything to the public internet.

Why internal routing matters​

  • Security: Traffic stays inside the project boundary
  • Simplicity: No need to set up external URLs or ports
  • Performance: Low-latency connections within the data center

How it works​

Each app and service gets a unique internal hostname. You can use this hostname to connect from one container to another.

For example, if you have:

  • An app named web
  • Another app called api

Your web app can connect to api using the internal hostname: appapi-service

The internal hostname is subject to change. Work in progress.

This works automatically – no manual network setup is required.

Supported connections​

Internal routing can be used between:

  • Apps and databases (e.g. MySQL, PostgreSQL or Redis -- the hostname is provided in the database details)
  • One app and another app (e.g. frontend → backend)

Best practices​

  • Use internal hostnames when possible
  • Don't hardcode IP addresses
  • Keep services inside the same project to use internal routing