unkey.app hostnames, so you can reach it as soon as it’s ready, with no DNS setup. Some hostnames always point at that one deployment. Others move to newer deployments. You can’t create, rename, or delete them. To use your own name, add a custom domain.
How hostnames are named
Each hostname starts with a prefix made from your project and , and ends with your workspace slug:
For a pull request from a fork, the fork owner’s name is added, so its deployments don’t clash with yours:
payments-fork-contributor-....
The five hostnames
For a deployment in workspaceacme, project payments, app default, production, built from commit 1a2b3c4d5e6f on branch feature/new_checkout with deployment ID d_3f9kq2x7, the deployment gets these hostnames:
The commit hostname uses the first seven characters of the SHA. Commit and branch hostnames only exist when the deployment has a commit and branch, which GitHub deployments always do. A preview deployment gets
payments-preview-acme.unkey.app as its environment hostname, and no live hostname.
Use the two pinned hostnames in bug reports and pull request comments, because they always show that exact build. Use the three moving hostnames in configuration. See Production and preview for how promote and rollback move them.
CLI deployments get a longer commit hostname
You can rununkey deploy several times on the same commit, so for CLI deployments we add the last four characters of the deployment ID to the commit hostname. For deployment d_3f9kq2x7 it becomes payments-git-1a2b3c4-q2x7-acme.unkey.app. Redeploying the same deployment keeps the same hostnames.
How branch names appear in hostnames
Branch names and deployment IDs are lowercased, every character that isn’t a letter or digit becomes a hyphen, repeated hyphens become one, and the result is cut at 80 characters. Sofeature/new_checkout becomes feature-new-checkout, and d_3f9kq2x7 becomes d-3f9kq2x7. Two branches that differ only in punctuation or case share one branch hostname.