Launch on your domain once. Keep shipping behind it.

Declare custom hosts and whole-host redirects with the app. After DNS verification, Adios serves the TLS route and keeps the hostname attached to the promoted current release.

Deploy an app Read domain setup

adios.yaml excerpt

name: web
routable: true

custom_hosts:
  - app.example.com
  - www.example.com

redirects:
  - from: example.com
    to: www.example.com

Example outcome

Make www.example.com the canonical hostname.

Attach www.example.com to the app and redirect example.com/pricing?plan=pro to the same path and query on the www host.

Launch with a verified custom hostname

Keep the generated platform route available while connecting your domain.

Deploy without changing DNS again

The hostname follows whichever release is current.

Keep canonical redirects at the gateway

A permanent 308 preserves the incoming path and query string.

Why this matters

A domain should belong to the app, not to a fragile proxy configuration.

DNS records, certificate renewal, apex redirects, and release cutovers are often managed separately, making a routine deploy depend on infrastructure nobody wants to touch.

What changes with Adios

Domains, redirects, and TLS live beside the runtime

Attach exact hostnames to the promoted release and express whole-host redirects in the same manifest that defines the app.

How it works

Verify the hostname once, then keep releasing behind it.

Step 01
Add the custom host or redirect to the app.
Step 02
Point DNS at the Adios gateway.
Step 03
Wait for verification, then deploy or redeploy the runtime.

A real use case

Make www.example.com the canonical hostname.

Attach www.example.com to the app and redirect example.com/pricing?plan=pro to the same path and query on the www host.

Custom host support in adios.yaml

Redirect-only gateway routes

Managed TLS for verified domains

Generated platform domains for quick launches

Connected pathReady

01
Add host
Declare the domain
02
Point DNS
Use the Adios target
03
Verify
Confirm ownership and route
04
Serve
Publish through managed TLS

Start here

Ship behind a hostname your users already know.

Start with a generated route, verify your domain, and keep it attached to each promoted release.

Deploy an app

Keep building

The next pieces usually connected to this one.

View all features

Global Edge Routing

Traffic enters through Adios edge locations while generated routes and custom domains resolve to the promoted current release and a healthy regional replica.

Explore →

Adios Deployments

Keep the build, start, health, region, and resource contract in adios.yaml. Running adios up turns the current source into a version and promotes it when the deployment is healthy.

Explore →

Runtime Security

Adios places managed gateways in front of public apps, keeps credentials outside source, supports runtime controls where available, and lets internal services remain non-routable.

Explore →