Incidents, without the panic channel.

An incident gets a severity, someone who leads it and a timeline. If they don’t pick up, devbord escalates to the next person on call. Afterwards, the postmortem is already half written.

From alarm to postmortem.

1. Something breaks: Open an incident by hand, from an issue in error tracking, or let a rule do it.
2. Whoever is on call picks it up: They get a notification and acknowledge. If it stays quiet, it moves to the next person after the minutes you choose.
3. Resolved, and written down: The postmortem starts as a first draft from the timeline. What still needs doing becomes a card.

Who’s on call. And when you are.

A rota by the day, week or fortnight, with the upcoming shifts in a row. If someone has to step away, a colleague covers that stretch, with the reason noted, and the rota carries on afterwards. Your shifts show up in your calendar too.

What incidents and on-call include.

• Severity and status. Critical, major or minor. Investigating, identified, monitoring, resolved: every step with its time.
• Escalation. Whoever doesn’t answer is relieved by the next person in the rota after 5 to 60 minutes. You choose from which severity.
• Rotas. Shifts of a day, a week or two weeks, with covers for whoever needs an evening off.
• Handover. Whoever hands over the pager also hands over the incidents still waiting for an answer.
• On the status page. A public update lands on your status page and with its subscribers. From a severity you choose, that happens by itself.
• Postmortems. A postmortem in Markdown, drafted from the timeline and saved as a doc.
• MTTA and MTTR. How fast incidents are acknowledged and resolved, right on the board.
• In your calendar and on your phone. Your shifts as a calendar feed, and incidents as time-sensitive notifications in the iPhone app.

Frequently asked questions

Does this replace PagerDuty or Opsgenie?

For a small team, usually yes: rotas, escalation, notifications on your phone and a timeline per incident. What’s missing: phone calls and SMS.

Can an error become an incident by itself?

Yes. Open an incident from an issue in error tracking, or let an automation rule do it, for example on an error spike.

How does an incident reach the status page?

By hand from the incident, or by itself from a severity you choose. Resolving closes the notice on the page.

Which plan includes incident management?

Incident management is part of Premium. That is one fixed price per workspace, however many members you have.

Status pages · Error tracking · Releases and test runs

devbord · Pricing: one flat price per team · News · API documentation · Support: help and contact · Privacy: what we can and cannot see · Terms of service · Privacy policy · Error tracking for dev teams, Sentry-compatible · Time tracking and invoicing for dev teams · Status pages with uptime monitoring and incidents · Changelog and release notes from done cards · Release management, test runs and DORA metrics for dev teams · Meeting agendas, async stand-ups and retros for dev teams · A feedback portal with voting and a public roadmap · Automation, a REST API, webhooks and an MCP server for dev teams · Sprint planning with burndown, a roadmap and OKRs · 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