Status pages

DevFlow can host a public or private status page off the back of your monitors and SLOs. Most teams use this instead of running their own.

creating a page

devflow status create acme-status   --domain status.acme.io   --visibility public

The --domain flag accepts a custom subdomain (CNAME to status.devflow.io). DNS verification happens automatically; certificate is managed.

components

A status page has components (services your customers care about). Each component pulls its current state from one or more monitors / SLOs:

components:
  - name: API
    state_from:
      type: slo
      slo: payments-availability-99.9
  - name: Webhooks
    state_from:
      type: monitor
      monitor: webhook-relay
  - name: Dashboard
    state_from:
      type: composite
      operator: any-degraded
      sources: [monitor:dashboard-prod, monitor:dashboard-eu]

subscribers

Customers can subscribe to email, RSS, SMS, or Slack updates. Subscriber list is exportable; we don't sell or share it.

historical incidents

Every incident-management incident affecting a status-page component is auto-published with the postmortem stub. You can edit the public-facing message before publish; nothing goes live without an explicit "Publish" click.

eat-our-own-dogfood

DevFlow's own status page (status.devflow.io) is built on this exact product. See uptime-and-our-own-status for what we hold ourselves to.

private pages

Internal-only status pages live behind your SSO — same product, different visibility flag. Useful for engineering-team dashboards.