A status page on your own domain. Your brand, not ours.
Give every client a status page with your logo, your colors and your domain. Nine layouts, custom CSS and no foreign name on the page, so every outage builds trust in you.
Made and Hosted in the
European Union
GDPR-Compliant Hosting
in Germany
GEO-Redundant Replica
across the EU
Nine layouts. One fits every client.
A web shop with three services needs a different page than a platform with thirty. You pick one of nine layouts, set colors, header and width, and see every change at once in the preview next to it. No template look that gives away which tool is behind it.
- Nine layouts from Statusboard with uptime bars to Compact for many services, so every page fits the size of the client.
- Colors, header, font and width to your liking, so the page looks like the rest of your brand.
- Live preview in the editor, so you see what your client sees before you save.
Layouts in the editor and as API value: Classic (`classic`), Cards (`cards`), Minimal (`minimal`), Sleek (`sleek`), Board (`board`), Split (`split`), Timeline (`timeline`), Compact (`compact`) and Statusboard (`statusboard`, default, uptime bars per service across the history window). All show the same data in a different structure and density.
`colorScheme` is `light`, `dark` or `auto`, `accentColor` a hex value, `headerStyle` `simple`, `centered` or `hero`, `fontFamily` `system` or `mono`, plus `cardRadius` and `pageWidth`. `customTitle` up to 120, `customSubtitle` up to 200 characters. `PATCH /api/status-pages/<id>/design` merges: you send only the fields that change.
Your logo on top. No foreign name below.
When something breaks, the status page is the first thing your client sees of you. Your logo sits on it in light and dark mode, your favicon in the browser tab and your product name in the copyright line. Switch off the "Powered by" line and the page does not name Uptimeify anywhere.
- Logo in light and dark that follows the page's color scheme, so your branding looks right in every mode.
- Favicon and product name in the tab and the footer, so the page is recognizably yours even among open tabs.
- Custom CSS up to 20 KB for details no setting covers, so demanding corporate designs fit too.
The logo appears at the top of every layout. With a light and a dark variant, the page uses the one matching its color scheme, and `auto` counts as light. The alt text is your product name, otherwise the page name. Without a favicon the page shows no icon. `showPoweredBy: false` removes the attribution entirely.
`customCss` up to 20 KB applies to the public page only, not to the editor preview or the embed widget. The footer with legal links and the subscribe dialog stay untouched. Rules that load resources, meaning `url()`, `@import` and `@font-face`, are rejected on save. With OpenTofu you manage organization branding through `uptimeify_organization_branding`.
status.deinkunde.com instead of someone else's subdomain.
A status page on a foreign address looks like a bought-in tool. On your own domain it looks like part of your infrastructure. You add a TXT record for verification, point a CNAME, and the certificate is issued automatically.
- Custom domain in three steps: verify, activate, point, so your client finds the page at an address they know.
- HTTPS without uploading certificates, so no browser ever warns in front of your status page.
- On the root domain too, with ALIAS, ANAME or CNAME flattening, so clients who want no subdomain are covered as well.
Flow: add the hostname, set the TXT record `_verify-status.<hostname>` with the token shown, verify, activate, point the CNAME to the target shown. States: Pending, Verified, Active. With Active, the certificate is issued through on-demand HTTPS. Both records stay in place, and the TXT record is re-checked weekly. A hostname belongs to exactly one status page.
A CNAME is not allowed on a root domain. Use CNAME flattening, ALIAS or ANAME to the same target, for example at Cloudflare, Bunny DNS, Amazon Route 53 or DNSimple, or a subdomain with a redirect. Fixed A or AAAA records to our IPs deliberately do not work long term, because the addresses behind the CNAME target change during failover. If verification fails, the diagnostics show the queried record, the expected value, the TXT values found, and NXDOMAIN or timeout.
Check first. Then publish.
You create a new status page on a single screen: name, address, client, visibility. It starts empty and shows only the components you add. Until you publish it, only signed-in members of your organization can see it, with a clear preview banner.
- Lean setup, so the first page is up in minutes and components follow at your own pace.
- Nothing goes public unasked: new pages show only what you add, so a freshly created monitor never appears on a client page by itself.
- Preview with a banner: unpublished pages are unreachable for everyone else, so you can align with the client before the address goes live.
A page is reachable at `/status/<slug>` and permanently at `/status/<id>`, and with an active custom domain directly on the hostname. `isPublished: false` hides the page without deleting it: signed-in members of your organization see it with a "Preview, not public" banner, everyone else gets `404`. Publishing, unpublishing and address changes take effect within 30 seconds.
New pages start with `includeCustomerMonitors = false`. When it is on, all of the client's monitors follow the components, except those in `hiddenMonitors` (up to 500). Existing pages keep their stored value.
We don't just monitor. We help you sell.
Every Uptimeify subscription includes access to our Success Kit, a collection of battle-tested resources to turn your monitoring into a profit center.
Service Level Agreement templates to define professional boundaries with your clients.
Find the sweet spot for your care plans. Calculate margins based on check frequency and support hours.
Powerpoint Templates that explain 24/7 monitoring to non-technical clients. Close more retainers.
Use automated reports to proactively communicate value, so clients never ask what they're paying for.
Ready to turn monitoring into a profit center?
Claim your Success Kit and start scaling today.
Frequently Asked Questions
Add the hostname in the page settings, create the TXT record shown at your DNS provider and click verify. Then activate the domain and point the CNAME to the target shown. Uptimeify issues the HTTPS certificate automatically, no upload needed.
Yes, with CNAME flattening, an ALIAS or an ANAME record, as offered by Cloudflare, Bunny DNS, Amazon Route 53 or DNSimple. Alternatively, use a subdomain such as status.deinkunde.com and redirect the root domain to it. Fixed A records do not work long term, because the addresses behind them can change during failover.
No. Logo, favicon, product name, colors and domain are yours, and the page never names Uptimeify. The optional "Powered by" line shows your own product name, and you can switch it off. The status page stays part of your service instead of advertising a tool.
Yes. Layout, colors, title and custom CSS are set per status page. The logo comes from your organization's branding, so every page runs under your brand. The web shop gets a lean page and the SaaS platform one with thirty components, both from one dashboard.
Saved changes appear on the next reload, and the status page HTML is not cached. Publishing, unpublishing and address changes take effect within 30 seconds. Badge, widget and feeds may be cached for up to 60 seconds.
For the technical stakeholder
Ready to put your brand on the status page?
Create your first page, pick a layout, add logo and domain and check it all in the preview. When something breaks, your client sees your brand, not a tool's.