Status

Hosted, public status pages - a component tree and incident timeline served on your own hep.gg slot or custom domain, with 90-day uptime, a status JSON feed, and an embeddable badge.

Status#

Status is a hosted status-page product (think Statuspage.io or BetterStack) that Hep.gg serves for you. You build a page entirely in the dashboard at hep.gg/dashboard/status: add the services you monitor as components, group them into categories, post incidents on a timeline, customize the look, and mount the page on a domain. Once published it is served as a polished, dark, server-rendered page on its mounted host, complete with per-component 90-day uptime, a machine-readable JSON feed, and an embeddable SVG badge.

Status is built primarily in the dashboard, but it also offers an optional per-page reporting API: you can create a Status API key and let an external monitor open incidents, post updates, and set component statuses programmatically. Building pages, editing the component tree, mounting domains, and buying slots stay dashboard-only. What is documented here is everything a developer can call: the public, unauthenticated surfaces a published page exposes (the rendered page, status.json, and badge.svg) plus the key-authed reporting API.

Authentication#

Status has two surfaces with different auth:

• Visitor-facing surfaces are unauthenticated. The rendered page, status.json, and badge.svg are all public. Access is gated by the page row, not a token.
• The reporting API uses a per-page Status API key. Create one in the dashboard for a given page, then send it as Authorization: Bearer hyd_status_... to open incidents, post updates, and set component statuses for that page only. See Reporting API.
• Building and editing pages is dashboard-only. Creating pages, editing the component tree, mounting domains, theming, and buying slots all happen in the dashboard authenticated by your hep.gg session cookie.

Visibility and availability#

A page is served publicly only when all of these are true on its row:

• is_public = 1 (you have published it from the dashboard).
• suspended = 0 (the account and page are in good standing).
• expires_at is null, or still in the future.

If any of these fails, the rendered page, status.json, and badge.svg return 404.

Plans and limits#

• Free: 1 page, up to 5 leaf components, with a small "Powered by Hep.gg" footer link.
• Premium: 2 pages, unlimited components, and the option to remove the footer link.
• Extra pages: both tiers can stack additional 30-day page slots (480 Hep Tokens each) from the dashboard.

Categories do not count toward the free 5-component cap - only the leaf components you actually report status on.

What's next#

• Components and statuses - the component tree, the five statuses, rollup, and uptime.
• Incidents and maintenance - the incident timeline, states, impact, templates, and scheduled maintenance.
• Custom domains - mounting your page on a hep.gg slot or your own domain.
• Public endpoints - the rendered page, status.json, and badge.svg.
• Reporting API - drive incidents and component statuses from an external monitor with a per-page key.