External Networking
By default, every container deployed on Bahriya is reachable from the internet via its hostname. External networking controls whether this is the case.
Default behaviour
When external networking is enabled (the default), Bahriya exposes your container to the internet via HTTPS using the container's configured hostnames.
Your container is reachable at:
- Its default regional hostname (
{handle}.{region}.x.on.bahriya.app)
- Its vanity hostname (if configured)
- Its custom domain (if configured)
Disabling external networking
When external networking is disabled, your container is not exposed to the internet.
The container is still reachable from within the same project by other containers using its handle as the hostname.
Use this for:
- Background workers that don't serve HTTP traffic.
- Internal services that should only be called by other containers in the same project, not by external clients.
- Databases or cache services running alongside your application.
Changing external networking
You can toggle external networking on an existing container. Enabling it creates DNS records and exposes the container; disabling it removes them. The change triggers a redeployment.
Note that disabling external networking does not stop the container — it continues running, just without an internet-facing endpoint.
