---
title: Namazu Cloud Subdomains
description: "A subdomain is a hostname under `cloud.namazustudios.com` that an organization reserves and attaches to an instance. It is how the outside world reaches your hosted Elements deployment. Subdomains live in an organization's pool: you reserve them in advance and attach…"
url: "https://namazustudios.com/docs/namazu-cloud/namazu-cloud-subdomains/"
updated: "2026-09-23"
category: Namazu Cloud
---

# Namazu Cloud Subdomains

A subdomain is a hostname under `cloud.namazustudios.com` that an organization reserves and attaches to an instance. It is how the outside world reaches your hosted Elements deployment. Subdomains live in an organization's pool: you reserve them in advance and attach one when you create an instance. The [name](https://namazustudios.com/glossary/name/) you pick is the address your players or users connect to, so choose it like you would choose a hostname for production.

---

## Statuses

Every subdomain carries a status, and that status is [authoritative](https://namazustudios.com/glossary/authoritative/):

| Status | Meaning |
| --- | --- |
| `RESERVED` | Reserved by the organization but not attached to any instance. Available to use when you create a new instance. |
| `DEPLOYED` | Attached to a live, running instance and publicly reachable at that hostname. |
| `DISABLED` | Administratively disabled by Namazu Cloud. Cannot be used for new instances. |

---

## Reserving a Subdomain

From the Subdomains section, reserve a [name](https://namazustudios.com/glossary/name/) for your organization (for example `myapp.cloud.namazustudios.com`). The portal checks availability as you type, so a [name](https://namazustudios.com/glossary/name/) already taken by another organization is flagged before you submit. When you create the subdomain it becomes `RESERVED` in your organization's pool, ready for the next [instance](namazu-cloud-instances) you create.

You can add a description to a subdomain to track its purpose, move it to a different organization you own, and remove it from the pool when it is no longer needed.

Note

Releasing a subdomain is guarded while any instance still references it. To reclaim the hostname for a fresh instance, first destroy the instance that uses it.

---

## Subdomains and Instances

A subdomain is attached to an instance at creation time and is fixed for the life of the instance. From then on the instance page shows your live hostname and the subdomain reads `DEPLOYED`. Only `DEPLOYED` subdomains are publicly served.

Destroying an instance does not release its subdomain. The subdomain returns to your organization's pool as `RESERVED` and is immediately available for another instance, so a hostname your users already know can move to a fresh deployment without changing anything on their side.

---

## Related Pages

- [Namazu Cloud Overview](namazu-cloud-overview)
- [Namazu Cloud Instances](namazu-cloud-instances). Attaching a reserved subdomain when you create an instance
- [Namazu Cloud Organizations](namazu-cloud-organizations). Subdomains belong to an organization's pool