Justin Duke published this on 9 January 2025. Buttondown is his newsletter product. The page title is a stack update, and a line at the top says it might be a little outdated.
The alerting change is one bullet. Better Stack, which they already used for logging, replaced PagerDuty and Statuspage. He does not say when the DNS or the status hostname moved, how many components were on the page, or what happened to email and SMS subscribers.
The same note records three other replacements. Plain took over from Help Scout, and he says they pay more for Plain and will write that move up later. Linear replaced GitHub Issues. Trotto replaced Golinks. Those are separate products. The Linear half is its own post. This one stays on Statuspage and PagerDuty.
The Statuspage → Better Stack playbook is the page, the components, the incident history, and the subscriber list. Justin’s bullet is the vendor choice. It is not that checklist.
What you can take from one sentence
They were already paying Better Stack for logs. Adding status and paging to a tool in the account is the whole rationale he wrote down. A second vendor for PagerDuty and a third for Statuspage is what went away. He does not compare features, uptime, or the monthly bill.
If your status page has a custom domain, a subscriber export, and a backlog of incidents, this post does not show you those steps. Copying the bullet would drop that history on the floor.
The stale-page warning matters. A January 2025 note can be wrong about what Buttondown runs now. I am treating it as evidence of the change he was willing to publish that day, not as a live architecture diagram.
What I would copy
Prefer a status tool you already operate, when the alternative is a page nobody on the on-call rotation opens. That is the shape of his sentence. It is a good reason only after you list the subscribers and the public URL.
Write the other moves in their own notes. Plain, Linear, and Trotto landed in the same changelog. A reader who treats the page as one migration will mix support, issues, and status.
Keep Statuspage up until a test incident on Better Stack reaches the same people. Justin does not describe that test. The Statuspage → Better Stack playbook is where that check lives. Use his post as the dated decision, and do not invent an export he never published.