Getting Started with Status Pages

Overview

This guide introduces AppStatus Status Pages and covers:

• Public and private status pages with custom domains
• 7 editor tabs: Settings, Structure, Updates, Maintenance, Subscribers, Translations, Advanced
• Monitor-to-component mapping with custom display names
• Password protection with Argon2id hashing
• Email subscriber management with verification
• Design themes: modern/classic with light/dark/system modes
• Custom CSS/JavaScript injection for full control
• Multi-language translations support

What are AppStatus Status Pages?

Status Pages provide transparent, real-time communication about service availability and incident progress. They map your internal monitors to public-facing components with custom display names, uptime history, and incident timelines — giving stakeholders visibility without exposing internal infrastructure.

Each status page is configured through a 7-tab editor covering identity, component mapping, incident updates, scheduled maintenance, subscriber management, translations, and advanced settings. Pages support custom domains, password protection, search engine control, and full design customization through themes, custom CSS, and JavaScript injection.

Key capabilities:

• Subdomain hosting: {slug}.yourdomain.com with automatic wildcard SSL
• Custom domain support with CNAME configuration
• Password protection using Argon2id (64KB memory, 4 iterations, 4 threads)
• Auth cookie: HTTP-only, 30-day expiry, constant-time comparison
• Email subscribers with verification tokens and unsubscribe
• Announcement-triggered subscriber emails
• Monitor mapping with custom display names, ordering, and visibility toggles
• Per-monitor uptime history toggle and section grouping
• Status page groups for organizing multiple pages
• Design: modern_look/classic, light/dark/system theme, custom primary color
• Custom CSS and JavaScript injection
• Multi-language translations via JSONB
• Auto-refresh: public page updates every 10 seconds
• Incident display with min_incident_length filter

Status Page Workflows

Each workflow maps to real AppStatus features and API endpoints used in the main app.

Troubleshooting

Operational Guidance

• Avoid manual status overrides unless explicitly required.
• Use pre-approved update templates during live incidents.
• Review subscriber growth and delivery reliability monthly.

Step-by-Step Setup

A status page is how your customers find out about an outage without opening a support ticket. You pick a slug (e.g. acme-status.appstatus.io), map your monitors to public components (e.g. "API", "Web dashboard"), brand it with your logo and colours, and optionally point a custom domain. Incident updates posted from the Incidents page show up on the public page automatically.

1. 1

   Open Status pages from the sidebar

   The list shows every status page in the workspace, public and private. The status column tells you whether the page is currently published.

   WhereSidebar → Status pages
2. 2

   Click "+ Create status page"

   The editor opens in a draft (private) state. You can fully build and preview the page before flipping it to public — visitors see nothing until you publish.

   WhereStatus pages → + Create status page
3. 3

   Pick a unique slug

   The slug becomes the subdomain (e.g. acme-status → acme-status.appstatus.io). The form checks availability live as you type and shows a green tick when the slug is free.

   WhereEditor → Identity → Slug

   Tip

   Choose carefully — changing the slug later breaks any existing bookmarks and the SEO ranking of the page.

4. 4

   Add branding

   Upload your logo and favicon, set a homepage URL and a support contact, write a short description. These show in the page header and footer and give customers the context they expect.

   WhereEditor → Branding → Logo, Favicon, Homepage URL, Support contact, Description
5. 5

   Map monitors to public components

   Public visitors see "components" with friendly names ("API", "Web dashboard", "Mobile app"), not your internal monitor names. Pick which monitors to expose, give each one a display name, and drag to reorder. Each component shows green when its monitor is UP.

   WhereEditor → Structure → Components → Add monitor
6. 6

   Choose visibility settings

   Decide who can see this page: public (anyone with the URL), public + password-protected (gated portal for customers), or private (workspace members only). Toggle "Show uptime history" and "Show incident history" based on how transparent you want to be.

   WhereEditor → Visibility → Public / Password-protected / Private
7. 7

   (Optional) Add a custom domain

   For status.yourcompany.com instead of yourcompany.appstatus.io, paste your domain into the Custom domain field. Then add a CNAME record in your DNS pointing to status.appstatus.io. TLS provisions automatically within a few minutes.

   WhereEditor → Branding → Custom domain

   Tip

   Save the page first — the editor shows you the exact CNAME target after you save.

8. 8

   Preview before publishing

   The "Preview" button (top-right) opens the page in a new tab using the slug subdomain. Anonymous visitors still cannot reach it because the page is private — this preview uses a signed link visible only to you.

   WhereEditor → Preview (top-right)
9. 9

   Publish

   Flip the "Public" toggle to On and click Save. The page becomes reachable at https://<slug>.appstatus.io (or your custom domain). Customers can now visit it and subscribe to incident updates.

   WhereEditor → Visibility → Public: On → Save

Configuration Options

Every option you can set, what each choice means, and what to pick. Use this as a reference while you fill in the form.

Feature Reference

Every feature, where to find it in the app, and what it does. Use this when you know what you want to do but not where it lives.

Next Steps

Continue building your monitoring stack: