Hep.gg Documentation

Status

Hosted public status pages with a Statuspage-style owner workspace: one-click component status, an incident composer, scheduled maintenance, monitors, subscribers, and a reporting API. Served at a free status.hep.gg address or your own domain.

Read via MCP

Status is a hosted status-page product (think Statuspage.io) that Hep.gg serves for you. You run a page from one workspace in the dashboard at dash.hep.gg/status: add the services you monitor as components, group them, flip their status with one click, post incidents and scheduled maintenance from a single composer, let visitors subscribe to updates, and let monitors flip components for you. Once published, the page is served as a polished, server-rendered page at its free yourname.status.hep.gg address or on your own domain, with per-component 90-day uptime, a JSON feed, an embeddable badge, and Atom and RSS feeds.

The workspace

One screen, built around what an operator actually does:

  • Status: what visitors see right now, the components board with a one-click status toggle on every row, your open incidents with a one-tap Post update, and any scheduled maintenance with Start now and Complete now.
  • Incidents: open incidents, maintenance, the full history with search, and your templates.
  • Subscribers: who follows your page by email, webhook or Discord, and the feed URLs.
  • Monitors: every URL check, its last result and latency, with Check now.
  • Settings (the gear): identity and branding with a live preview, your address and custom domain, notifications, API keys, and the danger zone.

The Open incident button in the top bar is always one tap away, and the whole thing works one-handed on a phone. Press Cmd/Ctrl+K for the command palette.

Getting live in a minute

Create a page, add your first component, and press Publish. Your page is live at <slug>.status.hep.gg immediately; a custom domain can be added at any time and becomes the canonical address. A short checklist in the workspace walks you through those three steps the first time.

Authentication

  • Visitor-facing surfaces are unauthenticated. The rendered page, status.json, badge.svg, and the feeds are public. Access is gated by the page being published, in good standing, and not expired.
  • The reporting API uses a per-page Status API key. Create one under Settings, then send it as Authorization: Bearer hyd_status_... to read status, open incidents, post updates, and set component statuses for that page only. See Reporting API.
  • Running the page is dashboard-only, authenticated by your hep.gg session.

Plans and limits

  • Free: 1 page, up to 5 leaf components, a small "Powered by Hep.gg" footer, URL monitors at 3-minute intervals or slower, up to 100 subscribers and 500 notification emails a day per page.
  • Prime: 2 pages, unlimited components, the footer can be removed, 1-minute monitors, custom domains, up to 2,000 subscribers and 5,000 emails a day per page.
  • Extra pages: both tiers can stack additional 30-day page slots with Hep Tokens from the dashboard.

Groups do not count toward the free component cap, only the leaf components you report on.

What's next

  • Components and statuses: groups, the five statuses, one-click changes, visibility, uptime, and monitors.
  • Incidents and maintenance: the composer, update progression, templates, scheduled maintenance, postmortems, and subscriber notifications.
  • Custom domains: your free address and your own domain.
  • Public endpoints: the rendered page, status.json, badge.svg, feeds, and subscriptions.
  • Reporting API: drive your page from an external monitor with a per-page key.