Skip to content

set up a custom domain

A custom domain points your own host (e.g. feedback.acme.com) at your spirby organization. Once verified, every public board, roadmap, and changelog is served from that host.

  • An active paid subscription. Trials cannot configure a custom domain.
  • Access to dns for the host you want to use.
  • The host cannot be a subdomain of spirby.com itself, that would conflict with the app.

In the admin dashboard, go to settings → custom domain → add domain and enter the full host. Spirby:

  1. Stores the domain with status pending.
  2. Enqueues a verification job.
  3. Returns the cname target you need to add at your dns provider.

At your dns provider, add a cname record:

<your-host> CNAME <cname-target-from-spirby>

Spirby uses Cloudflare for SaaS for ssl certificates. Once dns propagates and the verification job sees the cname pointing at the right target, the domain is added at Cloudflare and a certificate is issued automatically.

The verification job runs up to 10 attempts, 1 minute apart. Status moves through:

  • pending, waiting for dns to point at the target
  • verified, dns is correct and the Cloudflare hostname is registered
  • failed. 10 attempts elapsed without success
  • the public board, roadmap, and changelog all load on https://<your-host>
  • spirby still accepts requests on the original <subdomain>.spirby.com, there is no automatic redirect
  • email links use the custom host

You can remove the custom domain at any time from the same screen. Removing the domain locally also deletes the Cloudflare hostname (best-effort: a transient failure does not block the local clear; orphans can be cleaned up from the Cloudflare dashboard later).

If verification keeps failing, see troubleshooting.