A status page that keeps itself up to date.

Public status pages with uptime per monitor, incidents with updates and email subscribers. On your own domain, in ten languages, fed by the same monitors and incidents as your board.

From outage to update.

  1. Monitors measure: Uptime and cron monitors check your sites and your scheduled jobs.
  2. An incident opens: By hand, from an error, or automatically from a severity you choose.
  3. The page tells the story: Every public update shows on the page and goes to the subscribers.

What the status page shows.

Frequently asked questions

Which tools does the status page replace?

A status page such as Statuspage or Instatus, and the monitors from Cronitor or UptimeRobot that feed it.

Do I have to post incidents on the page by hand?

You do not have to. An incidents board can post incidents from a chosen severity on the page by itself, and closes the notice once the incident is resolved.

Can the status page live on our own domain?

Yes. You connect a domain of your own to the page.

Which plan includes the status page?

The status page is part of Premium. That is one fixed price per workspace, however many members you have.

Error tracking · Changelog · Sentry alternative

devbord · Pricing: one flat price per team · News · API documentation · Support: help and contact · Privacy: what we can and cannot see · Error tracking for dev teams, Sentry-compatible · Time tracking and invoicing for dev teams · Changelog and release notes from done cards · A Trello alternative for dev teams · A Sentry alternative that keeps your SDKs · A Linear alternative with error and time tracking · A Jira alternative for small dev teams · An Asana alternative for software teams · A ClickUp alternative with error tracking and invoicing · A Toggl alternative with a board and invoicing · A Harvest alternative with a kanban board · A Statuspage alternative with monitoring built in