Skip to content

SolutionsPlatform teams

A status page for the teams everyone depends on.

Platform, infrastructure, IT and SRE teams get a page their colleagues check before they ask. Each one stays inside: behind Google or Microsoft sign-in, a password, your office network or your app's sign-in.

platform.example.com
Skip to status
Platform
Active incidents
1 active incident.
Nov 2122:38 UTC

Latest updateInvestigating22:38 UTC ()

Deploys are waiting up to 15 minutes for a runner. Running deploys are not affected.

  1. Identified22:56

    Two runners lost their cache volume. They are being replaced; queued deploys start as they come back.

View incident

At a glance

Uptime, 30 days

99.58%

Services operational

3of 4

Active incidents

1
Services
3 of 4 services operational
  • Operational
  • Degraded
  • Outage
  • No data
Deploy pipeline
2 checks
Degraded30-day uptime100%
Oct 23Today
Metrics
  • Queued deploy jobs
    Degraded30-day uptime100%
    Oct 23Today
  • Runners online
    Degraded30-day uptime100%
    Oct 23Today
Internal API gateway
2 checks
Operational30-day uptime99.5%
Oct 23Today
Metrics
  • Gateway p95 latency
    Operational30-day uptime100%
    Oct 23Today
  • Gateway 5xx rate
    Operational30-day uptime99.5%
    Oct 23Today
Message queue
1 check
Operational30-day uptime100%
Oct 23Today
Artifact registry
1 check
Operational30-day uptime100%
Oct 23Today
Incidents
Last 24 hours
Active incidents are shown under the current status.
The status page itself, drawing sample data for three internal pages. Switch pages, and scroll inside them.

Access

Inside stays inside.

One access mode per page. It is checked before anything renders, and the badge, widget, JSON and feeds follow it, so nothing leaks through an embed.

Who gets in

Visitors from your office or VPN. Nobody has to sign in.

  • Up to 20 IPv4 ranges in CIDR form.
  • Every other address is refused before anything renders.

Starter and up

Everyone else sees

platform.example.com
Status overviewStatus
Access restricted
Your network is not on this page's allowlist.

Downgrades

A private page never turns public by itself.

If a plan lapses, the page keeps refusing visitors it would have refused before. Switching it to public is always your call.

Who it's for

Fewer “is it down?” messages.

The systems everyone inside relies on rarely get a status page. Give each team one, and let colleagues subscribe from it.

Platform teams

One page instead of the thread.

Deploys, the internal gateway, queues. Engineers look before they ask, and an incident posted there emails everyone who subscribed.

IT

Fewer tickets in an outage.

Mail, VPN, payroll. Staff check the page before they file, and the all clear reaches them the same way.

SRE leadership

Every team's service levels in one view.

Pro and up

Put each team's SLOs on one page with the error budget left, judged by the same rules everywhere.

You run it

Built to pass your own review.

The team that runs everything else sets Observer up. It reads what you already have, only dials out, and lives in your repository.

Sources

It reads what you already run.

Prometheus, OpenTelemetry, CloudWatch, Loki, Elasticsearch and your databases, plus HTTP, TCP, DNS, TLS, gRPC and WebSocket checks, all from one agent inside your network.

Network

The agent only dials out.

It reads inside your network and sends one number and its verdict per metric. Credentials stay on the host, and nothing connects in.

Install

A container, a binary or the Helm chart.

Run it next to your data with Docker, as a single binary, or on Kubernetes with the Helm chart.

As code

Checks live in your repository.

Starter and up

Keep checks, thresholds and pages in observer.yaml, review them in pull requests, and apply them with the CLI or its GitHub Action. A dry run shows the diff first.

Coding agents

Or let your coding agent set it up.

Connect the MCP server from Claude Code, Cursor, Codex or another MCP client, and your agent can add the checks and the pages for you.

Verdicts

One rule for every page.

Comparisons are strict, so a value equal to a threshold never matches, and a status change has to hold through a short confirmation window before a page flips.

Private metrics

Some numbers never leave the console.

Mark a metric private and it stays off every status page, internal ones included. Your team still hears when it breaks.

Off every page

Not listed, not counted.

A private metric is left out of the page, its uptime calendar, widget and Reliability Center, and it can never change a page's headline.

Still watched

Alerts keep flowing.

Its status changes still reach your alert channels, and the console keeps it in the metrics list, marked private.

Scope

An access mode, not a separate product.

Same setup

Nothing else changes.

Same agent, same metrics, same incidents. An internal page is a page with its access mode set, and it can go public again at any time.

Pages per plan

Room for every team.

Starter runs 1 status page, Pro 3, Business 10, Enterprise as many as you need. Internal pages count like any other.

Where Observer stops

Not an on-call router, not a root-cause tool.

Rotations and escalation stay in PagerDuty or Grafana IRM, and finding the cause stays with your team and your AI SRE. Observer feeds them, and proves the impact.

Send your next SLA statement signed.