Skip to content

Status pages thatread the metrics,not the operator.

Observer evaluates the same metrics your engineers look at, then publishes the verdict. One backend. One source of truth. A 99.99% contract and a 99.5% contract from the same probe.

api.checkoutapi.authapi.5xxapi.rpswebhook.dispatch
pg.replica-lagpg.connectionspg.write-latencypg.deadlocksredis.evictionsclickhouse.merge-lag
tls.expiry.apptls.expiry.apidns.apidns.zone-ttlcdn.purgecdn.hit-ratiolb.4xx-rateingress.tls-handshake
app.eu-west-1app.us-east-2report.ratereport.droppedslo.checkoutslo.api.30dscheduler.lageval.cycle
payment.apiemail.deliverygit.apiinference.apiloadbalancer.apisso.tokens

Status pages, re-engineered.

A next-generation status page: every signal your engineers watch, powering your status page, with zero maintenance. The same metric that triggers your on-call also flips your public page.

Open-source, privacy-first

The Observer agent runs inside your network, outbound-only, and evaluates every metric locally. Only { metric_id, value, status, timestamp } ever crosses to the cloud — queries, credentials, and raw telemetry never leave. Apache-2.0; audit every line.

Engineering signals

Prometheus, OpenTelemetry, CloudWatch, read-only queries on Postgres, MySQL, MongoDB and Redis, log aggregations from Loki and Elasticsearch — plus HTTP, TCP, DNS, TLS, ICMP, gRPC and WebSocket probes and built-in host metrics. One evaluator behind all of them.

Zero-touch updates

Define what 'working' means as a threshold on a real signal. When the metric crosses it, the public page flips within seconds — and recovers the same way. Nobody types anything.

Customer-scoped verdicts

The same 247 ms reading is healthy for a customer on a 99.9% contract and unhealthy for one on 99.99%. Per-customer SLOs, pages, and incident visibility from a single metric — from the Pro tier, not enterprise pricing.

Human-approved automation

Incidents auto-draft the moment a threshold is crossed and email your on-call a one-click publish. Nothing reaches customers without approval, and drafts nobody acts on expire after 24 hours.

Contract-grade reporting

Per-customer monthly and quarterly attainment — 99.97% against a 99.90% commitment — generated as PDFs and emailed automatically, with maintenance exclusions applied per the contract.

On-call ready

Slack, Telegram, Discord, Teams, PagerDuty, Grafana IRM, Splunk On-Call, signed webhooks, RSS. Incident updates correlate to one alert in your on-call tool — create, update, resolve — not three separate pages. Included on every plan.

GitOps native

Export and apply pages, services, metrics and SLOs as observer/v1 YAML. PR-reviewed, reproducible, reversible — no clickops between you and production.

Enterprise controls

Password, IP allowlist, JWT, or customer-scoped access per page. Maintenance windows that don't burn SLO budget. Custom domains with automatic TLS, so customers see status.yourcompany.com.

The same incident, on two status pages.

The checkout API begins returning 5xx at 10:14. One page reads what the operator typed, the other reads what the metric measured.

Traditional, operator-driven
00:00
Observer, metric-driven
00:00
All services operational
servicesall within threshold
Checkout API5 metrics
0.08%
Webhooks3 metrics
0.10%
incident logno incidents
No thresholds crossed. 47 metrics polled, all green.
10:1010:1510:2010:2510:3010:3510:4010:4510:5010:5511:00

Three places every status page leaks.

Operator memory, page-shaped services, one threshold for every customer. Each is the moment your status page stops telling the truth. Here is how each gets fixed.

Memory1 / 3
metric: checkout.p99
type: prometheus
query: |
histogram_quantile(0.99,
sum by (le)(rate(http_req[5m])))
thresholds:
degraded: > 250ms
unhealthy: > 500ms
slo: 99.95%
customers: [mercury, helios]

Eight pillars holding the page up.

No single feature does this. It's a stack of decisions about who the page is for, where it runs, and how it talks to the tools you already use. Open any card.

Pricing

Three tiers. Pick the one whose quotas you'll actually hit. Switch up or down at any time.

Free

Single status page, single agent. Get your first metric to public in 10 minutes.

$0/month

Billed monthly, cancel any time, taxes may apply.

Start free
What's included

1 status pages

1 agents

10 metric definitions

SLOs

custom domains

7d metric history

Customer-scoped pages

Outbound webhooks

Auto-incident creation

Custom CSS

Priority support

Starter

For a single product launching to its first paying customers. All integrations included.

$19/month

Billed monthly, cancel any time, taxes may apply.

Start Starter
What's included

1 status pages

3 agents

50 metric definitions

3 SLOs

1 custom domains

30d metric history

Customer-scoped pages

Outbound webhooks

Auto-incident creation

Custom CSS

Priority support

ProMost popular

For SaaS that already has customers. Customer-scoped pages, more SLOs, more domains.

$79/month

Billed monthly, cancel any time, taxes may apply.

Start Pro
What's included

3 status pages

10 agents

500 metric definitions

Unlimited SLOs

5 custom domains

90d metric history

Customer-scoped pages

Outbound webhooks

Auto-incident creation

Custom CSS

Priority support

EnterpriseContract

Multi-product orgs, unlimited everything, priority support. Talk to us about a contract.

Contact us
What's included

Unlimited status pages

Unlimited agents

Unlimited metric definitions

Unlimited SLOs

Unlimited custom domains

Custom metric history

Customer-scoped pages

Outbound webhooks

Auto-incident creation

Custom CSS

Priority support

View the full comparison table and every feature included in each plan on the pricing page.

Frequently asked questions

We get a lot of questions. Here are the answers to the most common ones.

Categories

Still have questions?

If you can't find what you're looking for, we're here to help.

Get in touch