I made a status page and incident timeline you actually own
A status page and incident timeline that you actually own. Incidents are just markdown files with frontmatter, so your whole incident history lives in git instead of a vendor's database, and you can diff it, review it in a PR, and move it anywhere. It serves a clean public page plus an RSS feed, runs as a single self-hosted binary, and has no per-seat pricing because it is open source. I kept it text-forward on purpose: a status page does not need a hero video or an animated globe, it needs to load instantly during an outage when your main site is already down. Scheduled maintenance windows and a tiny subscriber API are next.
Switched the data model to a folder of markdown files with frontmatter. Now incident history lives in git, which teams seem to love.
Sign in to leave a comment.
Just tried it on my machine, worked first run. Rare and appreciated.
Last-writer-wins per field, so conflicts are tiny in practice. Notes to self on this soon.
I've been building an open-source component library with a brutalist bent
I got small LLMs running nicely on a Raspberry Pi
I made a minimalist forum that is just markdown and links
I made self-hosted feature flags without the enterprise pricing