# Preview URLs and the 63-character hostname limit

Why every preview link is one DNS label, how project, computer, port and team share 63 characters, and how we trim names without collisions.

20 Nov 20265 min readhomemade team

Every service you run on a homemade computer can get its own link. Start a dev server on port 3000, mark it as a URL in the project config, and anyone you choose can open it in a browser with HTTPS. It looks simple from the outside. Inside, it runs into one of the oldest limits on the internet: a single part of a hostname can be at most 63 characters long.

This post explains how our preview links are built, why the whole thing has to fit in one 63-character piece, and how we shorten names without two computers ever ending up with the same link.

## What a preview link looks like

A link has four parts, joined with dashes, under the domain where computers' links live:

```
https://{project}-{computer}-{port}-{team}.onhomemade.com
```

For a project `shop`, a computer `misty-fern-142`, port 5173 and a team `acme`, that is:

```
https://shop-misty-fern-142-5173-acme.onhomemade.com
```

Each part tells you something. You can read a link in a chat message and know which project, which branch's computer and which service it points to, without opening it. A computer also has a page without a port, `shop-misty-fern-142-acme`, that lists its services. Only signed-in members of the team can open that one.

## Why one label, not nested subdomains

A cleaner-looking scheme would nest the parts:

```
https://5173.misty-fern-142.shop.acme.onhomemade.com
```

Each piece between dots is called a label. We could make as many labels as we like. The problem is the certificate.

Every link needs HTTPS, and HTTPS needs a certificate that covers the hostname. A wildcard certificate for `*.onhomemade.com` covers any name with exactly one label in front of the domain. It does not cover two or more. `shop.onhomemade.com` matches, `misty-fern-142.shop.onhomemade.com` does not.

Nested names would mean issuing a certificate for every team, project and computer, as they are created, with all the waiting, rate limits and failure cases that brings. With one label, one wildcard certificate covers every computer that will ever exist. A new computer's links work the moment it boots.

So everything goes into one label. And one label is capped at 63 characters by the DNS standard (RFC 1035). There is no way around that.

## The budget

The port takes up to 5 digits (65535) and the separators take 3 dashes. That leaves 55 characters for the project, computer and team names together.

We reserve the full 5 digits for the port even when a service uses port 80. That way every port of one computer uses exactly the same three name parts, and the computer can work out its own links. Inside every computer, the `HOMEMADE_URL` variables match its real links.

Names can be longer than that on their own. A team name can be up to 50 characters, a project too, and a computer's name up to 32. Most of the time they fit: `shop`, `misty-fern-142` and `acme` use 22 of the 55. When they don't fit, something has to give.

## How names get shortened

The rule is: use the full names whenever they fit, and only shorten what is needed, in a fixed order.

1. First the computer's name, from its 32-character cap down toward 20.
2. Then the project's name, down toward 15.
3. Then the team's name, down toward 15.

None of them is ever cut below those floors. The floors add up to 15 + 20 + 15 = 50, plus 5 for the port and 3 dashes makes 58, so the result always fits in 63.

Here is a real example with the same algorithm, for a project `customer-dashboard-redesign`, a computer `misty-fern-142` and a team `acme-international`:

```
customer-dashboard-dy8g-misty-fern-142-5173-acme-international
```

The names add up to 59 characters, 4 over budget. The computer name is already short, so the project name is trimmed, and the team name stays whole. The link is 62 characters.

## Shortening without collisions

Cutting names is dangerous. Two projects called `customer-dashboard-redesign` and `customer-dashboard-rewrite` would both become `customer-dashboard` if we just chopped off the end. Their links would point to the same place.

So a shortened part never ends with a plain cut. It ends with a dash and four characters taken from a hash of the full, original name. In the example above, `-dy8g` comes from hashing `customer-dashboard-redesign`. A different full name gives different characters, so two names that share a beginning still get different links.

The hash is short on purpose. It isn't a security feature. It only needs to keep apart names that are already unique within their team, and four characters of a well-spread hash do that.

## Links never change

We changed this scheme on 19 November 2026. Before that, each part had a fixed cap (project 15, computer 20, team 15), even when the other parts were short and there was room to spare. That cut names that didn't need cutting.

Links that were already handed out had to keep working. A link pasted into a pull request or a ticket last week shouldn't break because we improved the format. So every computer named before the change is marked, and keeps its old fixed caps forever. Only new computers get the shared budget.

## Dev servers just work

A long, unusual hostname can upset dev servers. Tools like Vite, Next.js, Django and Rails check the `Host` header to protect against DNS rebinding, and refuse names they don't know.

So the preview passes your app each request as if it came to `http://localhost:{port}`. Host checks accept it without any setup, and a redirect to `localhost` is sent back to the preview link. If your app needs to see the real address, for example to build absolute URLs in emails, set `publicHost: true` on the service.

## Who can open a link

Every service has a sharing level, set in the project config or per port on the computer's page:

| Level        | Who can open the link                      |
| ------------ | ------------------------------------------ |
| Public       | Anyone who has the link (the default)      |
| Organization | Members of the team that owns the computer |
| Owner only   | The person who created the computer        |

People who aren't allowed in are asked to sign in. And if the computer is asleep, the link can wake it. See [sleep and wake, explained](/blog/sleep-and-wake-explained).

## Your own domain

If you'd rather serve previews on your own domain, the Custom domains add-on on Pro ($20 a month) lets you connect up to 5 domains per project, each with its own certificate. See [pricing](/pricing).

The full reference for links is in the [previews docs](https://docs.homemade.dev/previews). If you're comparing how other platforms handle preview URLs, our [comparison pages](/compare) list each one's approach.

## Try homemade

Every project gets its own cloud computers, with Claude Code and Codex signed in. The Hobby plan is free.

[Start free](/login?signup=1)[See pricing](/pricing)

## Related posts

- [Sleep and wake, explained What happens when a cloud computer goes to sleep: memory snapshots, deep sleep, waking from a preview link, and what you pay while it sleeps.](/blog/sleep-and-wake-explained)
- [Running Claude Code and Codex in a cloud computer How to run Claude Code and Codex in a cloud computer: sign in once, start agents in parallel on their own branches, and review from any device.](/blog/claude-code-and-codex-in-a-cloud-computer)
- [Cloud dev environments for AI agents What an AI coding agent needs from a cloud dev environment: isolation, persistence, credentials, previews and cost. A checklist, with the trade-offs.](/blog/cloud-dev-environments-for-ai-agents)
- [All posts Every post](/blog)

Make yourself at home.

## Product

- [Pricing](/pricing)
- [Integrations](/integrations)
- [CLI](/cli)
- [MCP](/mcp)
- [API](/api)

## Use cases

- [Claude Code in the cloud](/claude-code-in-the-cloud)
- [Codex in the cloud](/codex-in-the-cloud)
- [AI agent sandbox](/ai-agent-sandbox)
- [Cloud dev environment](/cloud-dev-environment)
- [Preview environments](/preview-environments)

## Compare

- [All comparisons](/compare)

## Resources

- [Docs](https://docs.homemade.dev)
- [Blog](/blog)
- [llms.txt](https://docs.homemade.dev/llms.txt)

## Company

- [Contact](mailto:hello@homemade.dev)
- [GitHub](https://github.com/usehomemade/homemade)

## Legal

- [Impressum](/impressum)
- [Terms](/terms)
- [Privacy](/privacy)

© 2026 homemade.dev

---

Canonical: https://www.homemade.dev/blog/preview-urls-63-character-hostname
More pages: https://www.homemade.dev/llms.txt
