Domains and Networking

Domains and Networking#

NexHost separates public services from internal workspace services. The type you choose at creation determines which access model applies.

Public access#

Static Sites, Frontend Apps, and Web Services receive a public hostname after a successful release. You can add a custom domain through the dashboard once the service is ready. Public runtime services listen on the injected PORT; NexHost handles the external HTTP routing.

Private access#

Private Services and Postgres are intended for use inside the workspace network. Use the connection details displayed in the dashboard from other workspace services. Do not use a Private Service where users or third-party clients need a public URL.

Health paths#

Frontend Apps and Web Services can use an HTTP health path. The path must start with / and return a successful response before the configured timeout. Use a page such as / for a frontend or a small unauthenticated endpoint such as /health for an API.

Choosing between public types#

• Use Frontend App for a server-rendered UI.
• Use Web Service for an API or general backend.
• Use Static Site for pre-built files with no server process.