# Subdomains and custom domains

> Publishing an organisation's content at its own address rather than under blueprintr.io.

An organisation can serve its published content from its own address.

## Subdomain

Claim a label and the organisation's Atrium and folia are served from
`<label>.blueprintr.io`. This needs no DNS work.

The label is claimed once and becomes part of every URL underneath it.

## Custom domain

Point your own domain at Blueprintr instead. Add the domain in the
organisation's domains console and create the DNS records it shows you.
Verification is automatic once the records resolve, and certificates are issued
for you.

> [!IMPORTANT]
> A custom domain must be verified before it serves anything. Until then the
> content stays on the subdomain, and requests to the unverified domain are not
> answered.

## What moves

| Surface | Served from the custom domain |
| --- | --- |
| Atrium | Yes |
| Foliums | Yes |
| Published blueprints | Yes, for organisation-owned content |
| Personal blueprints | No, those stay under your handle |
| The dashboard and editor | No |

## Reader authentication

If you use
[reader authentication](/foliums/blueprintr-user-guide/foliums/reader-authentication),
the sign-in route must be reachable on the domain your folia are served from.
That is edge configuration rather than a setting; confirm it with whoever
operates the deployment before relying on it.