Status pages for the teams everyone depends on.
Platform teams, SRE leadership, and IT at non-engineering companies. SSO-gated, network-respected, as many pages per organisation as you need, on the same flat pricing.
The hardest systems to be on call for are the ones every other team relies on, and they almost never get a status page. Observer treats an internal page as a configuration mode, not a separate product. The same probe that backs your public page can back a private one.
Internal where it counts.
Everything the public page does, plus the controls that make a page safe to point inward.
- SSO-gated pages
- Sign-in through your own identity provider. An internal page is visible to employees, and only employees.
- Per-team scopes
- Finance sees finance systems. Engineering sees the dependency graph. Each team gets the view that concerns it.
- Subscriber routing
- Incidents reach internal distribution lists and Slack channels, not just a public subscribe box.
- Many pages, one bill
- Public plus internal plus per-team, set up the same way, billed the same way. No enterprise line item for internal use.
- Network boundary respected
- The agent stays in your environment. Internal metrics are evaluated where they live and never leave as raw data.
Three teams, the same gap.
Different systems, different audiences, the same missing piece: a page that answers is this down before anyone has to ask.
Platform and infrastructure teams
Auth, ingestion, the warehouse, the deployment pipeline. One page everyone points at, and far fewer Slack DMs asking whether something is down.
SRE leadership
Cross-service incidents need cross-team visibility. A unified internal page shows dependencies, ownership, and live verdicts, while scoped views surface only what each team owns.
IT teams outside engineering
Payroll, finance systems, HR portals. When one breaks, the help desk floods. Observer reads the real metric, posts the incident, and lets employees check before they file a ticket.
The same setup, two settings apart.
If you have built a customer page, you already know how. An internal page differs in exactly two places.
- 01
Set the access mode
Switch a page from public to SSO required or private. That single setting is the difference between external and internal.
- 02
Route the subscribers
Point notifications at internal distribution lists or Slack instead of a public subscribe form.
- 03
Nothing else changes
Same agent, same metrics, same deployment. If you already run a public page, internal pages are purely additive.
Observer does not replace on-call routing. Rotations, escalation policies, and paging stay with PagerDuty or Opsgenie. This is status pages and incident communication. Those tools sit alongside it, not underneath it.