Most status pages are marketing. They show seven straight green months and one carefully phrased "degraded performance" stripe. We don't have seven months of history yet, and we'd rather show the truth from day one than backfill a green wall later. status.dekimu.com is being built that way.
The page lives apart from every product surface, on its own hosting, with its own domain. That separation is the whole point — a status page hosted on the infrastructure it reports on tells you nothing during the incident you actually need it for.
Per-surface health across the ecosystem — id, InvoiceUp, miniterms, Hub, HelpMeNegotiate, Politeno, dekimu.site. Are dashboards rendering, can people sign in, can users do the thing the app exists to do. The incident timeline is written by us, not auto-generated. If something is broken we say so in plain English and post a follow-up note when it's fixed.
The day you wish you had a status page is the day every customer is already on Twitter.
When the checks pass forty-eight hours straight without a false positive. We'd rather ship it a week late and right than a week early and wrong. The announce post goes up the day status.dekimu.com is real.