Example/Demo Pages
Use these live examples when you want to see different StatiBeat page shapes before designing your own.
The examples deliberately vary by sector, depth, visibility, and operating style. Some are broad public pages with a few clear branches. Others are deeper operational models with custom views, Beats, and Terraform-managed hierarchy.
Most sector examples use their canonical page host, such as https://trial-game-arcforge.statibeat.com/. The shared route also works as https://status.statibeat.com/status/<page-slug>.
Product demos
| Demo | What it shows | Use it when |
|---|---|---|
| Main StatiBeat demo | A general interactive product demo for the admin and public-page workflow. | You want a broad tour before choosing a setup pattern. |
| Getting started video | A short walkthrough of first setup, hierarchy creation, incident publishing, layout comparison, and resolution. | You want the fastest explanation of the basic workflow. |
Sector demo pages
| Demo page | Sector | What to look for |
|---|---|---|
| ArcForge Online Status | Game platform | A deep game-themed hierarchy for player access, gameplay, commerce, creator tools, platform slices, regions, and leaf services. It is the best example for complex hierarchy depth, player-readable grouping, Beat Groups, and multiple customer views. |
| LedgerPay Status | Fintech and payments | A payments model with merchant-facing card and transfer availability, primary and backup processor routes, ACH returns, settlement files, and synthetic checks for authorization and reconciliation paths. |
| Northstar Marketplace Status | Commerce marketplace | A buyer/seller page that separates discovery, listings, checkout, fraud screening, payments, media processing, and search. It is useful for teams that need to explain third-party dependencies without exposing internal implementation detail. |
| CareHub Internal Status | Healthcare operations | A private, password-gated healthcare example for patient access and clinician workflows. It shows how an internal or partner-only page can model sensitive operational areas without making the page public. |
| RouteGrid Network Status | Logistics and delivery | A geography-first logistics page with country, hub, dispatch, routing, and customer tracking layers. It is useful when customers think in regions, depots, or operational zones rather than product modules. |
| Northstar Streaming Status | Streaming media | A playback and creator-platform example with viewer-facing playback, Smart TV and mobile slices, creator publishing, encoding queues, manifests, and license APIs. |
| InferenceCloud Status | AI platform | An AI infrastructure example for chat APIs, batch inference, embeddings, retrieval, model serving, quota checks, and vector index health. It is useful for API-first companies with developer-facing reliability expectations. |
CareHub is intentionally private. If you need to review that page during a customer walkthrough, use the demo viewer password provided by your StatiBeat contact.
What each example is meant to inspire
Choose a hierarchy shape
The sector pages show several useful hierarchy patterns:
- product-first: ArcForge, Northstar Marketplace, Northstar Streaming, and InferenceCloud
- rail or workflow-first: LedgerPay
- geography-first: RouteGrid
- audience and access-first: CareHub
Start with the language your customers already use. Then add deeper technical layers only where they make incidents easier to understand.
Compare public and private page styles
Most examples are public because they are designed for customer-facing communication.
CareHub is private because some operational status pages are meant for employees, partners, or regulated audiences. That makes it a good reference for viewer password or viewer SSO rollouts.
Explore custom views and Beats
The examples include focused views and synthetic monitors so you can see how one page can support multiple audiences:
- customer or player status
- operations and tournament views
- buyer and seller views
- clinician and patient-experience views
- developer API and runtime operations views
That pattern is useful when one underlying service hierarchy needs different windows for different stakeholders.