Skip to main content
By the end of this guide, a hosted environment answers on a hostname you own, over HTTPS, with a certificate the platform obtains and renews. You publish two DNS records once; everything after that is a command. A domain belongs to your organization and a binding points it at one environment’s workload or site, so you can move a verified domain between environments without touching DNS. Custom domains explains the model, the record shapes and each state.

Before you begin

  • A Forge project with a workload or static site deployed to a hosted environment, here prod serving a workload named api. Deploy a Go API with managed Postgres gets you there.
  • Access to the DNS settings of the hostname you are adding.
  • Forge v1.6.1 or later (reliant forge --version inside the project). Signed in to Reliant, forge cloud domain needs no separate login.
1

Claim the hostname

--env names the environment whose control plane to talk to; the domain itself is not tied to it:
terminal
Output (from a run with guides-sandbox.example.com)
A subdomain gets a CNAME; an apex gets an A record instead. Claiming does not reserve the name: the first organization to verify it takes it.
2

Bind it to a workload

A claimed domain serves nothing until it is bound. --target is a workload or frontend name in that environment:
terminal
Output
For www, add it as a second domain and bind it with --redirect-to app.example.com instead of --target.
3

Publish the DNS records

At your DNS provider, create both records exactly as domain add printed them, the long TXT token included. domain show prints them again at any time:
terminal
Output (trimmed)
Leave both records in place for good: the TXT token is re-checked on every pass. Do not publish an AAAA record.
4

Verify and wait for HTTPS

The platform re-checks on its own. domain verify checks now and prints what is still missing. This guide’s run used a reserved example.com name with no DNS, so its check failed:
terminal
Output (trimmed)
Once both records resolve, the state moves through ownership checking and certificate issuance to live, usually within minutes of DNS propagating. reliant forge cloud domain ls --env prod shows the state of every domain in the organization. Then curl -I https://app.example.com should answer from your workload. domain verify exits 0 even when the check fails, so read the state: line rather than the exit code.
5

Remove a domain you no longer need

unbind stops serving and keeps the verification; rm releases the hostname entirely:
terminal
Output
Deleting an environment releases its bindings and keeps the domains.

What this does not do

  • Domains are not declared in KCL, and a deploy never creates one. A hosted spec that carries a domains field is refused at render.
  • It does not change your DNS. Reliant cannot speed up your provider’s propagation.
  • There is no AAAA record and no IPv6 serving today.

Troubleshooting

The CNAME (or the apex A record) is missing, misspelled or not propagated yet. Compare what your provider shows with domain show character for character, then run domain verify again.
Some providers append your domain to a record name, producing _reliant-challenge.app.example.com.example.com. Check the saved name. Fix the record and run domain verify; do not remove and re-add the domain, which can run into certificate rate limits.

Next steps

Manage production secrets

Give the same environment its own secret values, set from stdin.

Custom domains

Record shapes, every state, conflicts and certificates.

Secrets

The hosted secret store each environment has.

Security model

How Reliant scopes credentials and keeps secrets write-only.