Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

cState review

Free#30 of 31 in Status Page Software

A self-hosted static status-page system for teams that manage updates in Markdown.

6.3/10Editor score
Visit cState
cState6.3 Visit cState

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

For teams that want control over how service status is published, cState generates static status pages from Hugo and Markdown. Developers and engineering teams can write incident updates as content, track severity and resolution, and publish planned maintenance announcements as informational posts. Its open-source, self-hosted approach is suited to organizations comfortable managing their own publishing workflow rather than relying on a hosted status-page service.

Deployment can fit several static-hosting setups: cState lists Netlify, Cloudflare Pages, GitHub Pages, GitLab Pages, Vercel, Docker, and self-managed infrastructure. The system also provides RSS and Atom feeds, a read-only JSON API, configurable service components and categories, and custom HTML and layout extensions. A CLI can create incidents, maintenance posts, experiments, and postmortems. Optional monitoring is available through the separate cState Monitor Bot. This mix suits developer-managed pages and integrations, though it places the publishing and deployment workflow with the team.

The listed plan is Free / open source, with static pages, self-hosting, Markdown-based incident content, and a read-only API. There are no paid tiers described here, so the main tradeoff is operational ownership rather than a choice of service levels. cState is a fit for teams that value source-based publishing and flexible hosting; teams needing verified subscriber notifications or private status pages should consider alternatives that explicitly provide those capabilities. The homepage's AI-agent-oriented workflows may be relevant to some buyers, but the core status-page system centers on static publishing.

cState pros and cons

  • Where it wins
    • Publish incidents and maintenance posts from Markdown.
    • Deploy to Netlify, Cloudflare Pages, GitHub Pages, and more.
    • Includes components, feeds, a read-only JSON API, and a CLI.
  • Where it doesn't
    • Static publishing requires teams to manage deployment.
    • Subscriber notifications are not verified.
    • Private status-page functionality is not verified.

cState fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update