Status Page Generator

Status Page Generator gives small software teams a hosted, white-label status page that can be live minutes after checkout. Create a branded page, add HTTPS checks or heartbeat components, point a custom domain at Lyrinox Market, and share a public service-health page with customers.

Each page also includes integration endpoints for your own products: POST webhooks update component health, while GET status APIs let apps, dashboards, installers, and support tooling read the current state of upstream services.

• Hosted by Lyrinox Market
• White-label branding by default
• Custom domain support
• HTTPS checks
• Webhook heartbeat intake
• Tokenized JSON read APIs

Technical Details

Audience

SaaS founders, support teams, independent developers, and small operations teams.

Use case

Publish a branded status page, monitor public health endpoints, receive product heartbeats, and let customer-facing apps read dependency status.

Compatibility

Status pages are hosted by Lyrinox Market. Customer systems integrate through HTTPS checks, webhook POSTs, and tokenized JSON GET endpoints.

Supported systems

Hosted Lyrinox Market status pages, custom domains, HTTPS health endpoints, webhook-capable products, support portals, installers, and dashboards.

Supported formats

Any stack that can send HTTPS POST requests or read JSON over HTTPS.

Dependencies

Requires an active Status Page Generator subscription. Custom domains require DNS pointing at the Lyrinox Market host.

Support scope

Lyrinox supports hosted page rendering, marketplace-backed subscription entitlement, webhook intake, read APIs, and first-party status page controls.

Security and data handling

Management routes require a signed-in Lyrinox account with an active subscription. Webhook and read API endpoints use per-page unguessable tokens.

Required permissions

No credentials are required for monitored public HTTPS endpoints. Webhook sender products only need the component webhook URL.

External services or calls

Lyrinox Market performs HTTPS checks against configured component URLs and receives webhook requests sent by customer products.

Copy-ready Examples

POST /api/status-pages/hooks/{webhook_secret}/api {"status":"operational","message":"Heartbeat received"}

GET /api/status-pages/{read_token}