Connect a domain and configure networking

After deployment, each application gets a default Deplomo URL. For production, you can connect a custom domain and configure HTTP, TCP or private networking.

HTTP

For websites and APIs, select HTTP exposure. The process must listen on 0.0.0.0 and the service’s internal port; PORT is the standard Deplomo convention. The default service URL is available over HTTPS and is the best initial test for distinguishing application problems from DNS issues.

Private

A private service has no internet endpoint and suits workers, internal backends and datastores. Use bindings or reference variables for internal addresses to avoid hardcoding hostnames in source code.

TCP

For non-HTTP protocols, select TCP exposure. Clients must connect to the displayed external hostname and port; this port differs from the container’s internal port. Enable protocol authentication and encryption in the software itself.

Custom domains

Add the domain to the service

In Domains, enter the domain without a scheme or path.

Create the recommended DNS record

Add the CNAME/TXT or other record shown in the dashboard to the domain’s authoritative DNS. If the zone is in Deplomo DNS, some of this is handled automatically.

Verify the domain

After DNS propagates, verify the domain. TLS certificates for verified hostnames are managed automatically.

Test the domain connection

Test HTTP and HTTPS, redirects, cookie domains, callback URLs and, where applicable, www and root-domain behavior.

Making a service public does not secure the application. Review administrative endpoints, CORS, rate limits, session cookies, default credentials and protections against common web attacks in your application.

Traffic metrics

For HTTP, the dashboard shows historical request counts, 5xx errors, average response time and bytes sent, based on access logs. TCP services report connections and traffic at the proxy layer; some runtimes do not provide request-level details for TCP.