One probe, a different verdict for every customer.
A 99.99% contract and a 99% contract, judged from the same underlying metric. Per-customer pages, SLO overrides, and subscribers, from the Pro tier rather than a $1500 a month enterprise line.
Traditional status pages assume one company, one page, one truth. Real SaaS does not work that way. Contracts are tiered, impact zones differ, and audiences do not overlap. Customer-scoped pages let one probe tell each customer the truth that applies to them.
One backend, many surfaces.
Everything that varies per customer lives on the page, not in a duplicated service. The probe stays singular.
- One definition, many pages
- A single service feeds every customer-facing page. There is no second source of truth to keep aligned.
- Per-customer SLO targets
- Acme is on 99.99%, Standard tier is on 99.9%. The same metric is judged against each contract independently.
- Per-customer subscribers
- Acme's contacts hear about incidents that affect Acme. Nobody is paged for a service they do not depend on.
- Per-customer access
- Public, SSO-gated, or JWT-scoped. Each page is visible to exactly the audience it is meant for.
- Unlimited scoped pages
- One Observer organisation spawns as many customer-scoped pages as you have customers. No per-page upsell.
Evaluate once, render per customer.
The novelty is in the last step: the metric is computed a single time, then read against each customer's own threshold.
- 01
Define a service
Bind the metrics that describe it. This is the underlying truth every customer page will read from.
- 02
Add a customer
Create an entity for one of your B2B customers. It carries their contract, their contacts, their access rules.
- 03
Bind them to a page
Attach the customer to a status page with their SLO override and their subscriber list. Set who can see it.
- 04
Observer renders per customer
The metric is evaluated once. Each page shows the verdict for that customer's threshold, computed from the same number.
Where one truth is not enough.
The shapes this takes once a status page can tell different audiences different things.
Tiered SLA commitments. Enterprise sees its 99.99% page, Standard sees 99.9%, both fed by one backend.
A multi-tenant platform. where different customers depend on different services, each scoped to what they actually use.
White-labeled pages. per customer or per region, on their own domain, with their own audience.
Internal pages scoped to teams. the same mechanism, pointed inward at the groups that depend on a platform.