Where custom domains fit

Custom domains are a TEAM-plan feature — the tier built for studios and client work, alongside multiple client projects under one account and managed databases. On STARTER, your app runs on its Forge URL, which is fine for side projects and demos. ENTERPRISE, with dedicated infrastructure, also supports custom domains for institutions.

Why it matters for client work

If you are an agency shipping a client portal or a booking form, the URL is part of the deliverable. A client portal living on your-forge-url reads as borrowed infrastructure; the same app on portal.clientsite.com reads as finished work. That is the gap the TEAM plan is built to close — one account, several client projects, each on its own domain.

What setup involves

Pointing a domain at your Forge app is standard DNS work: you add a record at your domain registrar that points your hostname at the address Forge gives you for the project, then wait for DNS to propagate — usually minutes to a few hours. The exact record values come with your project settings once your project is live. Forge verifies the connection and your app answers on the custom hostname.

Two things to know before you start: the domain is yours — nothing about it is locked to Forge if you later move — and DNS changes are fully reversible, so pointing and un-pointing is the same step in reverse.

After it is live

Once the domain resolves, your app serves on both the Forge URL and the custom domain during any transition. For what happens when a project changes owners — including the domain — see Forge Support and Handover, and Who Should Use Forge (and Who Shouldn't) for whether TEAM is the right tier.