Docs / custom-domains

Custom domains

Connect a domain you already own to a published project. HTTPS is issued automatically, and your poleved.app address keeps working alongside it.

Before you start

  • The domain has to be yours — you need access to its DNS settings at your registrar. Buying a domain is not part of the platform.
  • Publish the project first. A custom domain points at whatever your live deployment is serving; on an unpublished project the address resolves to nothing. See publish & deploy.
  • Only the project owner can add, verify or remove a domain. Editors can see the list.
  • A subdomain such as app.tokoku.com is the smoothest choice — see the note on bare domains below.

Adding a domain

  1. Open the project, then Settings → Domains.
  2. Type the hostname under Add a domain — the domain only, no https:// and no path.
  3. Click Add.

The field checks what you type against the same rules the server uses: no wildcards, no IP addresses, no underscores, and the extension is required (tokoku.com, not tokoku).

A hostname can only be claimed once across the whole platform. If you get That domain is already claimed for a name that is yours, an earlier claim is still holding it — unverified claims are released automatically after 72 hours.

The domain then appears in the list with a Waiting for DNS badge and the record you need to create.

Creating the DNS record

Under the domain you will see Create this DNS record at your registrar. Copy the values with the copy button beside each one rather than retyping them:

FieldWhat to enter
TypeCNAME
Nameyour hostname, e.g. app.tokoku.com
Valuecopy it from the panel

Sometimes a second TXT record is listed next to it. That one proves you control the domain before the certificate is issued — create both. The values can change between checks, so always work from what the panel shows right now.

Add the record in your registrar's DNS editor and save it.

Some registrars cannot point a bare domain (tokoku.com with nothing in front) using a CNAME. If yours refuses, use a subdomain like www.tokoku.com instead, or move the domain to a DNS provider that allows it.

Verifying

DNS changes take anywhere from a few minutes to a few hours to spread. That part happens at your registrar and is outside the platform's control.

Pending domains are re-checked automatically about every ten minutes, so you can close the tab and come back. If you would rather not wait, click Verify on the row to check straight away.

The badge moves Waiting for DNS → Verifying → Live. Once it reads Live, the hostname turns into a link, HTTPS is already in place, and the record block disappears — there is nothing left to do.

A live domain can later read Broken, with a short reason beside it. That means the address stopped serving, usually because the DNS record was changed or removed. Restore the record and it recovers on the next check.

Removing a domain

Click the trash button on the row, then Remove to confirm. The address stops serving immediately and the hostname is released, so it can be claimed again — by you or by anyone else.

Removing a domain never touches your project or its poleved.app URL.

Limits & notes

  • Unverified claims are deleted after 72 hours, which releases the hostname. Add it again once the DNS is ready.
  • Wildcard domains (*.tokoku.com) are not supported. Add each hostname you want.
  • Your plan sets how many custom domains you get: none on Spark, 1 on Maker, 3 on Studio, 10 on Foundry. Claims still waiting on DNS count toward it.
  • No more than 20 domains per project, whatever your plan.
  • Both addresses stay live — the custom domain and https://<slug>.poleved.app. Renaming the slug does not disturb a connected domain.
  • This page deliberately does not print the record values. They are generated for your domain and can change, so the panel is the only source worth copying from.
  • Limits may change during alpha.

Related