Brainpod
All updates
New featureNetworking

Local DNS for apps and databases

Connect apps and databases inside your Pod with private hostnames and resource variables, without creating a public route.

The Brainpod team2 min read

One Pod. Private hostnames. No public route between services.

Your apps can now find each other through local DNS. Apps with internal ports and managed databases get a private hostname inside their Brainpod Pod, so you can connect a frontend to an API or a worker to a database without exposing that connection to the internet.

Private names, scoped to your Pod

An app named api gets the hostname api.default.pod.internal. The default part is the resource namespace, not your Pod's name.

These names resolve only inside the Pod that owns the resource. You can use the same resource names in separate Pods: each Pod's workloads resolve their own resources, not another Pod's. Existing network isolation still applies. Public DNS lookups continue to work as usual.

Connect your apps

To make an app reachable by other apps in the same Pod:

  1. Open the app's settings and go to Advanced → Internal ports.
  2. Add the TCP port your app listens on, such as 8080. When selecting an image with no ports configured, Brainpod prefills the ports detected from the image; you can edit them before saving.
  3. In the calling app's environment variables, reference the target's host variable rather than hardcoding its hostname.
  4. Deploy the changes.

For example, a frontend connecting to an app named api on port 8080 can use:

.env
API_URL=http://${api.host}:8080

Brainpod resolves this to http://api.default.pod.internal:8080. Connections are load-balanced across the API's ready instances.

Internal ports do not publish your app to the internet. Add a Route separately when you want public access. Apps without internal ports do not export an internal hostname.

Databases use local DNS too

Postgres, MariaDB, Valkey and MSSQL use the same private naming scheme. A database named db exports ${db.host} as db.default.pod.internal, and its ${db.uri} connection string uses that hostname too. Prefer the URI variable when your app needs a full connection string; existing TLS requirements are unchanged.

You can find and copy the hostname under Internal DNS in app and database details, or select the host variable from the environment-variable suggestions.

Your first deploy is one prompt away.

Hand it to your agent. It installs the skill, creates your account and comes back with a live URL. No credit card to get started.

Book a call