cState vs StatusBeacon

cState turns Markdown content into static status pages and operational records, including incident updates, maintenance, experiment reports, evaluation logs, release notes, and decision records. Teams can manage incidents and maintenance as Markdown, with an audit trail and version control for updates. Static output needs no database and can be hosted on Netlify, Vercel, GitHub Pages, Cloudflare, Docker, or a user's own server. Status data can be embedded in docs, footers, dashboards, and product surfaces through JSON, RSS, Atom, and SVG outputs; the read-only API provides JSON status data. The product page lists support for 19+ languages and options to customize colors, logos, and layouts. Optional CLI and monitorbot tools add operator workflows and monitoring automation, while the core product is static. cState Core and the Free / open source plan are listed at free. cState Kit is a paid offering with automation tools, templates, setup guidance, commercial support, and white-label options; no price is listed. The maker identifies open-source projects, small SaaS teams, internal engineering teams, and agencies or consultants as audiences.

StatusBeacon has no write-up on Specifiction yet; its figures are above.