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.
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 | The most complex example: a five-level game hierarchy for player access, gameplay, commerce, creator tools, platforms, regions, modes, and leaf services. Use it to show deep grouping, Beat Groups, and several customer views. |
| LedgerPay Status | Fintech and payments | A narrow workflow model from product to payment rail, processor, and dependency. It shows merchant-facing card and transfer availability without turning the page into a huge service inventory. |
| Northstar Marketplace Status | Commerce marketplace | A wide, shallow two-level marketplace page with buyer, seller, and platform-operations branches. See the copyable Terraform example to build the same core structure. |
| CareHub Internal Status | Healthcare operations | A small private, password-gated two-level healthcare example for patient access and clinician workflows. It shows how an internal or partner-only page can stay intentionally simple. |
| RouteGrid Network Status | Logistics and delivery | A deep, narrow geography-first model that drills from country to hub, workflow, system, and operational signal. It is useful when customers think in regions, depots, or operational zones rather than product modules. |
| Northstar Streaming Status | Streaming media | A medium-depth playback and creator-platform page with broad device, web, creator, and live-ops capabilities. It sits between simple scanability and deeper service modeling. |
| InferenceCloud Status | AI platform | A technical five-level API/runtime/dependency/signal hierarchy for chat, batch, embeddings, quota, vector writes, and usage metering. It is useful for API-first companies with developer-facing reliability expectations. |
CareHub is intentionally private. Use the demo viewer password CareHubDemo!2026 during customer walkthroughs.
What each example is meant to inspire
Choose a hierarchy shape
The sector pages show several useful hierarchy patterns:
- product-first: ArcForge, Northstar Streaming, and InferenceCloud
- wide and shallow: Northstar Marketplace
- 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.