Routes

A route connects a URL to a target - such as a Space, a Container Deployment or a redirect. This is how you make your applications accessible under your own domains.

Creating a Route

1. Open Routes → Create Route
2. Enter the URL (subdomain, domain, path)
3. Select the target
4. Click Save

SSL certificates are created automatically.

URL Structure

A route URL consists of three parts:

https://[subdomain].[domain]/[path]

• Subdomain - optional, e.g. www or api
• Domain - a domain from your account
• Path - optional, e.g. /blog or /app

Examples:

• example.com → main domain
• www.example.com → with subdomain
• example.com/blog → with path
• api.example.com/v1 → subdomain and path

Target Types

Space

Routes requests to a Space. The Space must exist in your account.

Container

Routes requests to a Container Deployment. You select the deployment and the container with the desired port.

Redirect

Redirects visitors to another URL. Choose between:

• Permanent (301) - for permanent redirects, adopted by search engines
• Temporary (302) - for temporary redirects

Multiple Routes per Target

You can point any number of routes to the same target. Typical use cases:

• example.com and www.example.com to the same Space
• Different domains to the same application
• Different paths to different containers

Preview Routes

For Container Deployments you can create preview routes directly from the deployment view. These generate an automatic URL to quickly make a port accessible - handy for testing.

Requirements

The domain used must be present in your account. You can either register domains through us or add external domains. More on this under Domains.