Branding your status page

Branding controls at v1 are deliberately narrow. The trade-off: customers want their page to look like their company; visitors of a status page want clarity, not creativity. We ship just enough brand control to make the page recognisable without letting it become hard to read on a bad day.

What you control

• Brand colour — single hex value applied to the header border, the verdict badge accent, link underlines, and the CTA button. Page background and body text stay neutral.
• Logo — uploaded via Vercel Blob, served from the blob CDN. Max 10 MB. Allowed: image/png, image/jpeg, image/svg+xml. Anything else returns a 400 from the upload endpoint.
• Page title — the H1 at the top of the page, also used as the HTML <title> for browser tabs and link previews.

What you can't control at v1

• Dark mode — public pages are light-only at v1. Some visitors will land from incident emails opened on dark devices; we accept the contrast loss to avoid maintaining two themes.
• Custom font — page uses our default sans / mono stack. Avoids adding a third-party font load that could fail on a bad day and blank the page just when visitors most need it.
• Background and foreground colour — neutral by design. The brand colour is an accent, not the canvas.

Logo upload mechanics

POST /api/status-pages/:id/upload-logo with a multipart file field. On success, status_page.logoUrl is set to the blob URL. The old logo blob is deleted asynchronously by an Inngest function when you replace or delete the page.

Reversing the rules

If you have a strong reason for a brand control we don't ship — full theme, font upload, dark mode — open a ticket at hello@domaincare.io. We evaluate each request seriously and write down the reasoning either way.